Exam Bundle

Reliability: The Reliability pillar concerns recovery from disruptions, meeting demand and resilient design. This does not address the need for A business wants to reduce environmental impact through efficient resource utilization. The appropriate Sustainability applies because The Sustainability pillar is about minimizing environmental impacts of cloud workloads.

Security: The Security pillar focuses on protecting systems and information using identity, detection and data safeguards. This does not address the need for A business wants to reduce environmental impact through efficient resource utilization. The appropriate Sustainability applies because The Sustainability pillar is about minimizing environmental impacts of cloud workloads.

Performance efficiency: The Performance Efficiency pillar emphasizes efficient resource selection and adapting as demand and technology evolve. This does not address the need for A business wants to reduce environmental impact through efficient resource utilization. The appropriate Sustainability applies because The Sustainability pillar is about minimizing environmental impacts of cloud workloads.

Reliability: The Reliability pillar concerns recovery from disruptions, meeting demand and resilient design. That does not meet the requirement: A company asks architects to consider carbon impact and avoid unused resource capacity.

Performance efficiency: The Performance Efficiency pillar emphasizes efficient resource selection and adapting as demand and technology evolve. That does not meet the requirement: A company asks architects to consider carbon impact and avoid unused resource capacity.

Security: The Security pillar focuses on protecting systems and information using identity, detection and data safeguards. That does not meet the requirement: A company asks architects to consider carbon impact and avoid unused resource capacity.

Security: The Security pillar focuses on protecting systems and information using identity, detection and data safeguards. This does not address the need for A company asks architects to consider carbon impact and avoid unused resource capacity. The appropriate Sustainability applies because The Sustainability pillar is about minimizing environmental impacts of cloud workloads.

Reliability: The Reliability pillar concerns recovery from disruptions, meeting demand and resilient design. This does not address the need for A company asks architects to consider carbon impact and avoid unused resource capacity. The appropriate Sustainability applies because The Sustainability pillar is about minimizing environmental impacts of cloud workloads.

Performance efficiency: The Performance Efficiency pillar emphasizes efficient resource selection and adapting as demand and technology evolve. This does not address the need for A company asks architects to consider carbon impact and avoid unused resource capacity. The appropriate Sustainability applies because The Sustainability pillar is about minimizing environmental impacts of cloud workloads.

Assume perfect infrastructure offers no meaningful recovery plan for component or Availability Zone failures. That does not meet the requirement: Consider this AWS requirement: A development team plans for individual components to fail rather than assuming permanent uptime.

Keep all components together creates tighter coupling and a common failure domain. That does not meet the requirement: Consider this AWS requirement: A development team plans for individual components to fail rather than assuming permanent uptime.

Scale up only: Increases the capacity of an existing node but does not introduce independent replicas. That does not meet the requirement: Consider this AWS requirement: A development team plans for individual components to fail rather than assuming permanent uptime.

Assume perfect infrastructure offers no meaningful recovery plan for component or Availability Zone failures. This does not address the need for A development team plans for individual components to fail rather than assuming permanent uptime. The appropriate Design for failure applies because Fault-aware architecture uses redundancy, isolation and recovery because component failures can occur.

Keep all components together creates tighter coupling and a common failure domain. This does not address the need for A development team plans for individual components to fail rather than assuming permanent uptime. The appropriate Design for failure applies because Fault-aware architecture uses redundancy, isolation and recovery because component failures can occur.

Scale up only: Increases the capacity of an existing node but does not introduce independent replicas. This does not address the need for A development team plans for individual components to fail rather than assuming permanent uptime. The appropriate Design for failure applies because Fault-aware architecture uses redundancy, isolation and recovery because component failures can occur.

Keep all components together creates tighter coupling and a common failure domain. That does not meet the requirement: An API platform needs to isolate faults and continue processing when one dependency fails.

Scale up only: Increases the capacity of an existing node but does not introduce independent replicas. That does not meet the requirement: An API platform needs to isolate faults and continue processing when one dependency fails.

Assume perfect infrastructure offers no meaningful recovery plan for component or Availability Zone failures. That does not meet the requirement: An API platform needs to isolate faults and continue processing when one dependency fails.

Keep all components together creates tighter coupling and a common failure domain. This does not address the need for An API platform needs to isolate faults and continue processing when one dependency fails. The appropriate Design for failure applies because Fault-aware architecture uses redundancy, isolation and recovery because component failures can occur.

Assume perfect infrastructure offers no meaningful recovery plan for component or Availability Zone failures. This does not address the need for An API platform needs to isolate faults and continue processing when one dependency fails. The appropriate Design for failure applies because Fault-aware architecture uses redundancy, isolation and recovery because component failures can occur.

Scale up only: Increases the capacity of an existing node but does not introduce independent replicas. This does not address the need for An API platform needs to isolate faults and continue processing when one dependency fails. The appropriate Design for failure applies because Fault-aware architecture uses redundancy, isolation and recovery because component failures can occur.

Shared monolith places components in one coupled application rather than isolating independent services. That does not meet the requirement: A technical reviewer evaluates this need: Two business services must evolve independently and tolerate temporary failures of one another.

Direct hard dependency requires a producer and consumer to be available together instead of decoupling work asynchronously. That does not meet the requirement: A technical reviewer evaluates this need: Two business services must evolve independently and tolerate temporary failures of one another.

Single process architecture: Makes one process a potential single point of failure. That does not meet the requirement: A technical reviewer evaluates this need: Two business services must evolve independently and tolerate temporary failures of one another.

Direct hard dependency requires a producer and consumer to be available together instead of decoupling work asynchronously. This does not address the need for Two business services must evolve independently and tolerate temporary failures of one another. The appropriate Loose coupling applies because Loose coupling reduces dependencies between components, allowing them to change or fail more independently.

Single process architecture: Makes one process a potential single point of failure. This does not address the need for Two business services must evolve independently and tolerate temporary failures of one another. The appropriate Loose coupling applies because Loose coupling reduces dependencies between components, allowing them to change or fail more independently.

Shared monolith places components in one coupled application rather than isolating independent services. This does not address the need for Two business services must evolve independently and tolerate temporary failures of one another. The appropriate Loose coupling applies because Loose coupling reduces dependencies between components, allowing them to change or fail more independently.

Direct hard dependency requires a producer and consumer to be available together instead of decoupling work asynchronously. That does not meet the requirement: An online store wants the catalog and order processing services to communicate without tight synchronous dependency.

Shared monolith places components in one coupled application rather than isolating independent services. That does not meet the requirement: An online store wants the catalog and order processing services to communicate without tight synchronous dependency.

Single process architecture: Makes one process a potential single point of failure. That does not meet the requirement: An online store wants the catalog and order processing services to communicate without tight synchronous dependency.

Single process architecture: Makes one process a potential single point of failure. This does not address the need for An online store wants the catalog and order processing services to communicate without tight synchronous dependency. The appropriate Loose coupling applies because Loose coupling reduces dependencies between components, allowing them to change or fail more independently.

Shared monolith places components in one coupled application rather than isolating independent services. This does not address the need for An online store wants the catalog and order processing services to communicate without tight synchronous dependency. The appropriate Loose coupling applies because Loose coupling reduces dependencies between components, allowing them to change or fail more independently.

Direct hard dependency requires a producer and consumer to be available together instead of decoupling work asynchronously. This does not address the need for An online store wants the catalog and order processing services to communicate without tight synchronous dependency. The appropriate Loose coupling applies because Loose coupling reduces dependencies between components, allowing them to change or fail more independently.