Performance efficiency pillar primarily supports the earlier need to select and adapt resources to meet performance needs efficiently because performance efficiency includes choosing suitable technologies and maintaining efficient resource use as demand changes, but the new task is to match provisioned resources to measured workload requirements; that is why Right-sized architecture is preferable here.

Experiment-driven performance choices is intended to benchmark workload alternatives before standardizing a configuration because measurement of actual application behavior supports appropriate performance trade-offs; in this design the new outcome is to match provisioned resources to measured workload requirements, which calls for Right-sized architecture rather than Experiment-driven performance choices or the earlier Performance efficiency pillar.

Horizontal scaling is intended to spread work across additional independent resources because horizontal scaling increases the number of workers or instances serving a workload; in this design the new outcome is to match provisioned resources to measured workload requirements, which calls for Right-sized architecture rather than Horizontal scaling or the earlier Performance efficiency pillar.

That description belongs to AWS CAF Business perspective because the Business perspective aligns cloud initiatives with strategy, value and commercial priorities; it is used to connect cloud adoption to business outcomes and investment decisions, not to explain how Retain provides the function to leave a selected workload in its current environment for the time being.

That description belongs to AWS Cloud Adoption Framework (AWS CAF) because AWS CAF organizes transformation capabilities into Business, People, Governance, Platform, Security and Operations perspectives; it is used to structure the organizational changes needed for cloud adoption, not to explain how Retain provides the function to leave a selected workload in its current environment for the time being.

That description belongs to AWS CAF People perspective because the People perspective addresses skills, roles, workforce transformation and change management; it is used to prepare the workforce and organizational culture for cloud transformation, not to explain how Retain provides the function to leave a selected workload in its current environment for the time being.

That description belongs to Avoid single points of failure because redundancy across failure boundaries helps keep a service available when one part fails; it is used to remove a single component whose outage would take down the whole system, not to explain how Infrastructure observability provides the function to make system behavior visible through meaningful operational metrics and logs.

That description belongs to Operational excellence pillar because operational excellence focuses on delivering business value through effective operations and continuous learning; it is used to improve how teams operate, monitor and continually refine workloads, not to explain how Infrastructure observability provides the function to make system behavior visible through meaningful operational metrics and logs.

That description belongs to Automate recovery because automated detection and recovery reduce the time needed to handle predictable failure conditions; it is used to restore normal application behavior without waiting for routine manual intervention, not to explain how Infrastructure observability provides the function to make system behavior visible through meaningful operational metrics and logs.

That description belongs to AWS Cloud Adoption Framework (AWS CAF) because AWS CAF organizes transformation capabilities into Business, People, Governance, Platform, Security and Operations perspectives; it is used to structure the organizational changes needed for cloud adoption, not to explain how AWS CAF Governance perspective provides the function to manage transformation risks, priorities and portfolio decisions.

That description belongs to AWS CAF Business perspective because the Business perspective aligns cloud initiatives with strategy, value and commercial priorities; it is used to connect cloud adoption to business outcomes and investment decisions, not to explain how AWS CAF Governance perspective provides the function to manage transformation risks, priorities and portfolio decisions.

That description belongs to AWS CAF People perspective because the People perspective addresses skills, roles, workforce transformation and change management; it is used to prepare the workforce and organizational culture for cloud transformation, not to explain how AWS CAF Governance perspective provides the function to manage transformation risks, priorities and portfolio decisions.

Resource-efficient software is intended to avoid unnecessary processing and storage when delivering the same output because reducing wasted computation contributes to performance and sustainability objectives; in this design the new outcome is to avoid unnecessary expenditure while achieving business outcomes, which calls for Cost optimization pillar rather than Resource-efficient software or the earlier Multi-AZ redundancy.

Multi-AZ redundancy primarily supports the earlier need to avoid tying service availability to one Availability Zone because deploying suitable redundant resources in multiple AZs isolates many facility-level failures, but the new task is to avoid unnecessary expenditure while achieving business outcomes; that is why Cost optimization pillar is preferable here.

Operational excellence pillar is intended to improve how teams operate, monitor and continually refine workloads because operational excellence focuses on delivering business value through effective operations and continuous learning; in this design the new outcome is to avoid unnecessary expenditure while achieving business outcomes, which calls for Cost optimization pillar rather than Operational excellence pillar or the earlier Multi-AZ redundancy.

It does not intentionally rebuild the application's architecture around managed services; that caveat is associated more closely with Rehost (lift and shift) for the need to move an application to cloud infrastructure with minimal redesign than with Repurchase for the requirement to replace an existing application with a different software product or SaaS solution.

It generally demands more engineering effort than a straightforward rehost; that caveat is associated more closely with Refactor or re-architect for the need to modify an application to exploit cloud-native capabilities more substantially than with Repurchase for the requirement to replace an existing application with a different software product or SaaS solution.

An application is not considered rehosted simply because its old server is powered down; that caveat is associated more closely with Retire for the need to remove an application that no longer delivers sufficient business value than with Repurchase for the requirement to replace an existing application with a different software product or SaaS solution.

Infrastructure observability addresses the separate need to make system behavior visible through meaningful operational metrics and logs because useful telemetry helps teams detect performance changes and failures early; it is not as direct as Reliability pillar for the actual requirement to help a workload recover from failures and continue functioning correctly.

Sustainability pillar addresses the separate need to minimize environmental impact associated with running workloads because sustainability emphasizes efficient consumption and reduction of energy and resource waste; it is not as direct as Reliability pillar for the actual requirement to help a workload recover from failures and continue functioning correctly.

Continuous performance tuning addresses the separate need to revisit resource choices as application demand evolves because performance-efficient architectures update technology choices and capacity based on evidence; it is not as direct as Reliability pillar for the actual requirement to help a workload recover from failures and continue functioning correctly.

Loose coupling primarily supports the earlier need to allow application components to fail or scale with less direct dependency on each other because queues and asynchronous communication can decouple component lifecycles, but the new task is to reduce the blast radius and rollback effort of deployments; that is why Small reversible changes is preferable here.

Operational excellence pillar is intended to improve how teams operate, monitor and continually refine workloads because operational excellence focuses on delivering business value through effective operations and continuous learning; in this design the new outcome is to reduce the blast radius and rollback effort of deployments, which calls for Small reversible changes rather than Operational excellence pillar or the earlier Loose coupling.

Security pillar is intended to protect information, systems and assets using risk-aware controls because the security pillar addresses identities, detection, infrastructure and data protection, and incident response; in this design the new outcome is to reduce the blast radius and rollback effort of deployments, which calls for Small reversible changes rather than Security pillar or the earlier Loose coupling.

Rehost (lift and shift) addresses a different objective, to move an application to cloud infrastructure with minimal redesign, because rehosting relocates a workload while largely preserving its existing architecture; the checklist instead requires the distinct outcomes to replace an existing application with a different software product or SaaS solution; manage transformation risks, priorities and portfolio decisions; replicate source servers for a largely lift-and-shift migration.

AWS Cloud Adoption Framework (AWS CAF) addresses a different objective, to structure the organizational changes needed for cloud adoption, because AWS CAF organizes transformation capabilities into Business, People, Governance, Platform, Security and Operations perspectives; the checklist instead requires the distinct outcomes to replace an existing application with a different software product or SaaS solution; manage transformation risks, priorities and portfolio decisions; replicate source servers for a largely lift-and-shift migration.

Business continuity during migration addresses a different objective, to plan service availability and rollback while changing environments, because migration preparation includes cutover planning, recovery objectives and dependency awareness; the checklist instead requires the distinct outcomes to replace an existing application with a different software product or SaaS solution; manage transformation risks, priorities and portfolio decisions; replicate source servers for a largely lift-and-shift migration.

The framework guides organizational readiness; it does not copy database records itself; that caveat is associated more closely with AWS Cloud Adoption Framework (AWS CAF) for the need to structure the organizational changes needed for cloud adoption than with Retain for the requirement to leave a selected workload in its current environment for the time being.

A purely technical deployment plan cannot replace employee readiness; that caveat is associated more closely with AWS CAF People perspective for the need to prepare the workforce and organizational culture for cloud transformation than with Retain for the requirement to leave a selected workload in its current environment for the time being.

It differs from the Platform perspective's technical infrastructure capabilities; that caveat is associated more closely with AWS CAF Business perspective for the need to connect cloud adoption to business outcomes and investment decisions than with Retain for the requirement to leave a selected workload in its current environment for the time being.

That description belongs to Infrastructure observability because useful telemetry helps teams detect performance changes and failures early; it is used to make system behavior visible through meaningful operational metrics and logs, not to explain how Automate recovery provides the function to restore normal application behavior without waiting for routine manual intervention.

That description belongs to Loose coupling because queues and asynchronous communication can decouple component lifecycles; it is used to allow application components to fail or scale with less direct dependency on each other, not to explain how Automate recovery provides the function to restore normal application behavior without waiting for routine manual intervention.

That description belongs to Continuous performance tuning because performance-efficient architectures update technology choices and capacity based on evidence; it is used to revisit resource choices as application demand evolves, not to explain how Automate recovery provides the function to restore normal application behavior without waiting for routine manual intervention.