That description belongs to Resource-efficient software because reducing wasted computation contributes to performance and sustainability objectives; it is used to avoid unnecessary processing and storage when delivering the same output, not to explain how Multi-AZ redundancy provides the function to avoid tying service availability to one Availability Zone.

That description belongs to Trade-off evaluation because the Well-Architected Framework helps review reliability, security, cost and other quality attributes together; it is used to consider competing architectural priorities instead of optimizing one metric blindly, not to explain how Multi-AZ redundancy provides the function to avoid tying service availability to one Availability Zone.

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 Multi-AZ redundancy provides the function to avoid tying service availability to one Availability Zone.

Avoided data-center costs primarily supports the earlier need to reduce expenses for facility space, power, cooling and physical maintenance because migrating suitable workloads can shift responsibility for physical facility operation to AWS, but the new task is to reduce storage expense by matching access frequency to storage class; that is why Storage tier selection is preferable here.

Capital expenditure (CapEx) is intended to recognize upfront infrastructure purchase as a fixed investment because capEx involves purchasing owned assets such as servers and data-center equipment before the benefits are consumed; in this design the new outcome is to reduce storage expense by matching access frequency to storage class, which calls for Storage tier selection rather than Capital expenditure (CapEx) or the earlier Avoided data-center costs.

Variable cloud costs is intended to align consumption-based expense with actual usage because usage-based pricing lets spending change with resource consumption instead of requiring fixed purchased capacity; in this design the new outcome is to reduce storage expense by matching access frequency to storage class, which calls for Storage tier selection rather than Variable cloud costs or the earlier Avoided data-center costs.

Self-service provisioning is intended to create an environment without waiting for physical equipment installation because authorized teams can provision cloud resources through APIs or a console when they are needed; in this design the new outcome is to test a prototype without large upfront infrastructure investment, which calls for Experimentation at low initial commitment rather than Self-service provisioning or the earlier Resource pooling.

Fault tolerance is intended to continue operating despite an individual infrastructure component failing because fault-tolerant systems absorb failures using redundancy, isolation and suitable application behavior; in this design the new outcome is to test a prototype without large upfront infrastructure investment, which calls for Experimentation at low initial commitment rather than Fault tolerance or the earlier Resource pooling.

Resource pooling primarily supports the earlier need to benefit from provider-managed shared infrastructure without operating a dedicated facility because cloud providers abstract and share large infrastructure fleets while logically isolating customers, but the new task is to test a prototype without large upfront infrastructure investment; that is why Experimentation at low initial commitment is preferable here.

AWS CAF People perspective primarily supports the earlier need to prepare the workforce and organizational culture for cloud transformation because the People perspective addresses skills, roles, workforce transformation and change management, but the new task is to prepare support, monitoring and service operations for migrated workloads; that is why AWS CAF Operations perspective is preferable here.

Business continuity during migration is intended to plan service availability and rollback while changing environments because migration preparation includes cutover planning, recovery objectives and dependency awareness; in this design the new outcome is to prepare support, monitoring and service operations for migrated workloads, which calls for AWS CAF Operations perspective rather than Business continuity during migration or the earlier AWS CAF People perspective.

AWS CAF Platform perspective is intended to establish technical foundations for hosting and building cloud workloads because the Platform perspective addresses cloud engineering, architecture and platform capabilities; in this design the new outcome is to prepare support, monitoring and service operations for migrated workloads, which calls for AWS CAF Operations perspective rather than AWS CAF Platform perspective or the earlier AWS CAF People perspective.

Multi-AZ redundancy addresses the separate need to avoid tying service availability to one Availability Zone because deploying suitable redundant resources in multiple AZs isolates many facility-level failures; it is not as direct as Loose coupling for the actual requirement to allow application components to fail or scale with less direct dependency on each other.

Operations as code addresses the separate need to apply controlled repeatable procedures to infrastructure and operations because machine-readable definitions allow review, versioning and consistent execution of operations; it is not as direct as Loose coupling for the actual requirement to allow application components to fail or scale with less direct dependency on each other.

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 Loose coupling for the actual requirement to allow application components to fail or scale with less direct dependency on each other.

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 understand resource demand and quotas before workload demand exceeds limits; that is why Capacity awareness is preferable here.

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 understand resource demand and quotas before workload demand exceeds limits, which calls for Capacity awareness rather than Right-sized architecture or the earlier Continuous performance tuning.

Vertical scaling is intended to increase the capacity of an existing compute resource because vertical scaling changes the size or power of one instance or server; in this design the new outcome is to understand resource demand and quotas before workload demand exceeds limits, which calls for Capacity awareness rather than Vertical scaling or the earlier Continuous performance tuning.

Managed-service operational relief addresses the separate need to avoid administering an underlying platform for a common workload because managed services move specific tasks such as database engine patching to AWS; it is not as direct as Durability for the actual requirement to reduce the likelihood of losing stored information over time.

Self-service provisioning addresses the separate need to create an environment without waiting for physical equipment installation because authorized teams can provision cloud resources through APIs or a console when they are needed; it is not as direct as Durability for the actual requirement to reduce the likelihood of losing stored information over time.

Global reach addresses the separate need to serve customers in distant geographies with regional deployments because AWS Regions allow workloads to run closer to users in multiple geographic markets; it is not as direct as Durability for the actual requirement to reduce the likelihood of losing stored information over time.

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 Prescriptive Guidance.

AWS Prescriptive Guidance primarily supports the earlier need to find practical AWS migration patterns and implementation guidance because prescriptive Guidance provides proven strategies and technical patterns for cloud adoption, but the new task is to develop a data-informed financial business case for migration; that is why Migration Evaluator is preferable here.

AWS Database Migration Service (AWS DMS) is intended to move or replicate database data to a supported target because AWS DMS supports migration and ongoing replication for suitable database 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 Database Migration Service (AWS DMS) or the earlier AWS Prescriptive Guidance.

That description belongs to Economies of scale because large cloud providers can spread infrastructure costs across broad demand and procurement volumes; it is used to benefit from infrastructure purchasing and operations at provider scale, not to explain how Capital expenditure (CapEx) provides the function to recognize upfront infrastructure purchase as a fixed investment.

That description belongs to Total cost of ownership (TCO) because a TCO analysis considers hardware, software, operations, labor, facilities and cloud usage; it is used to compare the full cost of different infrastructure approaches, not to explain how Capital expenditure (CapEx) provides the function to recognize upfront infrastructure purchase as a fixed investment.

That description belongs to Return on investment (ROI) because rOI compares gains with associated investment costs for a business decision; it is used to evaluate expected financial benefit relative to an investment, not to explain how Capital expenditure (CapEx) provides the function to recognize upfront infrastructure purchase as a fixed investment.

Refactor or re-architect addresses a different objective, to modify an application to exploit cloud-native capabilities more substantially, because refactoring changes design or code to gain capabilities such as managed services or elastic components; the checklist instead requires the distinct outcomes to make limited optimizations during migration without fully redesigning the application; manage transformation risks, priorities and portfolio decisions.

AWS CAF Platform perspective addresses a different objective, to establish technical foundations for hosting and building cloud workloads, because the Platform perspective addresses cloud engineering, architecture and platform capabilities; the checklist instead requires the distinct outcomes to make limited optimizations during migration without fully redesigning the application; manage transformation risks, priorities and portfolio decisions.

AWS Application Discovery Service addresses a different objective, to collect information about on-premises servers and dependencies for migration planning, because discovery services help inventory workloads and understand application dependencies; the checklist instead requires the distinct outcomes to make limited optimizations during migration without fully redesigning the application; manage transformation risks, priorities and portfolio decisions.

Total cost of ownership (TCO) is intended to compare the full cost of different infrastructure approaches because a TCO analysis considers hardware, software, operations, labor, facilities and cloud usage; in this design the new outcome is to benefit from infrastructure purchasing and operations at provider scale, which calls for Economies of scale rather than Total cost of ownership (TCO) or the earlier Bring Your Own License (BYOL).

Bring Your Own License (BYOL) primarily supports the earlier need to reuse eligible existing software licenses under applicable provider terms because bYOL can let a customer apply eligible licenses to suitable cloud deployments, but the new task is to benefit from infrastructure purchasing and operations at provider scale; that is why Economies of scale is preferable here.

Capital expenditure (CapEx) is intended to recognize upfront infrastructure purchase as a fixed investment because capEx involves purchasing owned assets such as servers and data-center equipment before the benefits are consumed; in this design the new outcome is to benefit from infrastructure purchasing and operations at provider scale, which calls for Economies of scale rather than Capital expenditure (CapEx) or the earlier Bring Your Own License (BYOL).