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.

Retain primarily supports the earlier need to leave a selected workload in its current environment for the time being because retention is appropriate when migration is not yet justified or allowed, but the new task is to plan service availability and rollback while changing environments; that is why Business continuity during migration is preferable here.

AWS CAF Operations perspective is intended to prepare support, monitoring and service operations for migrated workloads because the Operations perspective develops capabilities for operating workloads effectively; in this design the new outcome is to plan service availability and rollback while changing environments, which calls for Business continuity during migration rather than AWS CAF Operations perspective or the earlier Retain.

AWS Cloud Adoption Framework (AWS CAF) is intended to structure the organizational changes needed for cloud adoption because AWS CAF organizes transformation capabilities into Business, People, Governance, Platform, Security and Operations perspectives; in this design the new outcome is to plan service availability and rollback while changing environments, which calls for Business continuity during migration rather than AWS Cloud Adoption Framework (AWS CAF) or the earlier Retain.

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 minimize environmental impact associated with running workloads, which calls for Sustainability pillar rather than Operational excellence pillar or the earlier Security pillar.

Reliability pillar is intended to help a workload recover from failures and continue functioning correctly because reliability covers recovery, capacity planning and resilience to infrastructure or service disruption; in this design the new outcome is to minimize environmental impact associated with running workloads, which calls for Sustainability pillar rather than Reliability pillar or the earlier Security pillar.

Security pillar primarily supports the earlier need to protect information, systems and assets using risk-aware controls because the security pillar addresses identities, detection, infrastructure and data protection, and incident response, but the new task is to minimize environmental impact associated with running workloads; that is why Sustainability pillar is preferable here.

That description belongs to Cost optimization pillar because cost optimization focuses on understanding spend and delivering value at the right cost; it is used to avoid unnecessary expenditure while achieving business outcomes, not to explain how Resource-efficient software provides the function to avoid unnecessary processing and storage when delivering the same output.

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 Resource-efficient software provides the function to avoid unnecessary processing and storage when delivering the same output.

That description belongs to Multi-AZ redundancy because deploying suitable redundant resources in multiple AZs isolates many facility-level failures; it is used to avoid tying service availability to one Availability Zone, not to explain how Resource-efficient software provides the function to avoid unnecessary processing and storage when delivering the same output.

AWS CAF Business perspective addresses the separate need to connect cloud adoption to business outcomes and investment decisions because the Business perspective aligns cloud initiatives with strategy, value and commercial priorities; it is not as direct as AWS CAF Governance perspective for the actual requirement to manage transformation risks, priorities and portfolio decisions.

AWS CAF Platform perspective addresses the separate need to establish technical foundations for hosting and building cloud workloads because the Platform perspective addresses cloud engineering, architecture and platform capabilities; it is not as direct as AWS CAF Governance perspective for the actual requirement to manage transformation risks, priorities and portfolio decisions.

Migration Evaluator addresses the separate need to develop a data-informed financial business case for migration because migration Evaluator supports assessing on-premises resource usage and potential AWS economics; it is not as direct as AWS CAF Governance perspective for the actual requirement 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 tying service availability to one Availability Zone, which calls for Multi-AZ redundancy rather than Resource-efficient software or the earlier Trade-off evaluation.

Cost optimization pillar is intended to avoid unnecessary expenditure while achieving business outcomes because cost optimization focuses on understanding spend and delivering value at the right cost; in this design the new outcome is to avoid tying service availability to one Availability Zone, which calls for Multi-AZ redundancy rather than Cost optimization pillar or the earlier Trade-off evaluation.

Trade-off evaluation primarily supports the earlier need to consider competing architectural priorities instead of optimizing one metric blindly because the Well-Architected Framework helps review reliability, security, cost and other quality attributes together, but the new task is to avoid tying service availability to one Availability Zone; that is why Multi-AZ redundancy is preferable here.

AWS CAF Business perspective is intended to connect cloud adoption to business outcomes and investment decisions because the Business perspective aligns cloud initiatives with strategy, value and commercial priorities; in this design the new outcome is to develop a data-informed financial business case for migration, which calls for Migration Evaluator rather than AWS CAF Business perspective or the earlier AWS Database Migration Service (AWS DMS).

AWS Schema Conversion Tool (AWS SCT) is intended to convert database schema and code for a heterogeneous database migration because AWS SCT helps transform schema objects and certain database code between supported engines; in this design the new outcome is to develop a data-informed financial business case for migration, which calls for Migration Evaluator rather than AWS Schema Conversion Tool (AWS SCT) or the earlier AWS Database Migration Service (AWS DMS).

AWS Database Migration Service (AWS DMS) primarily supports the earlier need to move or replicate database data to a supported target because AWS DMS supports migration and ongoing replication for suitable database engines, but the new task is to develop a data-informed financial business case for migration; that is why Migration Evaluator is preferable here.

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 Operations perspective provides the function to prepare support, monitoring and service operations for migrated workloads.

That description belongs to Business continuity during migration because migration preparation includes cutover planning, recovery objectives and dependency awareness; it is used to plan service availability and rollback while changing environments, not to explain how AWS CAF Operations perspective provides the function to prepare support, monitoring and service operations for migrated workloads.

That description belongs to AWS CAF Platform perspective because the Platform perspective addresses cloud engineering, architecture and platform capabilities; it is used to establish technical foundations for hosting and building cloud workloads, not to explain how AWS CAF Operations perspective provides the function to prepare support, monitoring and service operations for migrated workloads.

Right-sized architecture is intended to match provisioned resources to measured workload requirements because right sizing avoids both excess capacity and insufficient capacity for expected service levels; in this design the new outcome is to select and adapt resources to meet performance needs efficiently, which calls for Performance efficiency pillar rather than Right-sized architecture 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 select and adapt resources to meet performance needs efficiently; that is why Performance efficiency pillar is preferable here.

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 select and adapt resources to meet performance needs efficiently, which calls for Performance efficiency pillar rather than Horizontal scaling or the earlier Multi-AZ redundancy.

Multi-AZ redundancy is intended to avoid tying service availability to one Availability Zone because deploying suitable redundant resources in multiple AZs isolates many facility-level failures; in this design the new outcome is to avoid unnecessary processing and storage when delivering the same output, which calls for Resource-efficient software rather than Multi-AZ redundancy or the earlier Continuous performance tuning.

Cost optimization pillar is intended to avoid unnecessary expenditure while achieving business outcomes because cost optimization focuses on understanding spend and delivering value at the right cost; in this design the new outcome is to avoid unnecessary processing and storage when delivering the same output, which calls for Resource-efficient software rather than Cost optimization pillar or the earlier Continuous performance tuning.

Continuous performance tuning primarily supports the earlier need to revisit resource choices as application demand evolves because performance-efficient architectures update technology choices and capacity based on evidence, but the new task is to avoid unnecessary processing and storage when delivering the same output; that is why Resource-efficient software is preferable here.

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 tying service availability to one Availability Zone, which calls for Multi-AZ redundancy rather than Resource-efficient software or the earlier Avoid single points of failure.

Cost optimization pillar is intended to avoid unnecessary expenditure while achieving business outcomes because cost optimization focuses on understanding spend and delivering value at the right cost; in this design the new outcome is to avoid tying service availability to one Availability Zone, which calls for Multi-AZ redundancy rather than Cost optimization pillar or the earlier Avoid single points of failure.

Avoid single points of failure primarily supports the earlier need to remove a single component whose outage would take down the whole system because redundancy across failure boundaries helps keep a service available when one part fails, but the new task is to avoid tying service availability to one Availability Zone; that is why Multi-AZ redundancy is preferable here.