Resource pooling addresses the separate 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; it is not as direct as Self-service provisioning for the actual requirement to create an environment without waiting for physical equipment installation.

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 Self-service provisioning for the actual requirement to create an environment without waiting for physical equipment installation.

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 Self-service provisioning for the actual requirement to create an environment without waiting for physical equipment installation.

Operating expenditure (OpEx) addresses the separate need to treat recurring service consumption as a running operational cost because opEx reflects spending as services and computing resources are consumed; it is not as direct as Storage tier selection for the actual requirement to reduce storage expense by matching access frequency to storage class.

Demand forecasting addresses the separate need to estimate future usage to avoid unplanned commitment or capacity decisions because forecasts help teams plan spend and procurement based on usage trends; it is not as direct as Storage tier selection for the actual requirement to reduce storage expense by matching access frequency to storage class.

Capital expenditure (CapEx) addresses the separate need 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; it is not as direct as Storage tier selection for the actual requirement to reduce storage expense by matching access frequency to storage class.

Avoided data-center costs addresses the separate 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; it is not as direct as Storage tier selection for the actual requirement to reduce storage expense by matching access frequency to storage class.

Capacity awareness primarily supports the earlier need to understand resource demand and quotas before workload demand exceeds limits because good reliability planning accounts for capacity needs and service quotas, but the new task is to increase the capacity of an existing compute resource; that is why Vertical scaling 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 increase the capacity of an existing compute resource, which calls for Vertical scaling rather than Operational excellence pillar or the earlier Capacity awareness.

Continuous performance tuning is intended to revisit resource choices as application demand evolves because performance-efficient architectures update technology choices and capacity based on evidence; in this design the new outcome is to increase the capacity of an existing compute resource, which calls for Vertical scaling rather than Continuous performance tuning or the earlier Capacity awareness.

AWS Database Migration Service (AWS DMS) addresses the separate need to move or replicate database data to a supported target because AWS DMS supports migration and ongoing replication for suitable database engines; it is not as direct as AWS Prescriptive Guidance for the actual requirement to find practical AWS migration patterns and implementation guidance.

Repurchase addresses the separate need to replace an existing application with a different software product or SaaS solution because repurchasing selects a new commercial offering rather than migrating the same software deployment unchanged; it is not as direct as AWS Prescriptive Guidance for the actual requirement to find practical AWS migration patterns and implementation guidance.

AWS CAF Security perspective addresses the separate need to embed protection, risk practices and security capabilities into migration because the Security perspective helps establish security governance and resilient protective controls; it is not as direct as AWS Prescriptive Guidance for the actual requirement to find practical AWS migration patterns and implementation guidance.

AWS CAF People perspective addresses the separate need to prepare the workforce and organizational culture for cloud transformation because the People perspective addresses skills, roles, workforce transformation and change management; it is not as direct as AWS Prescriptive Guidance for the actual requirement to find practical AWS migration patterns and implementation guidance.

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 help a workload recover from failures and continue functioning correctly, which calls for Reliability pillar rather than Experiment-driven performance choices or the earlier Cost optimization pillar.

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 help a workload recover from failures and continue functioning correctly, which calls for Reliability pillar rather than Right-sized architecture or the earlier Cost optimization pillar.

Cost optimization pillar primarily supports the earlier need to avoid unnecessary expenditure while achieving business outcomes because cost optimization focuses on understanding spend and delivering value at the right cost, but the new task is to help a workload recover from failures and continue functioning correctly; that is why Reliability pillar is preferable here.

Fault tolerance addresses the separate need to continue operating despite an individual infrastructure component failing because fault-tolerant systems absorb failures using redundancy, isolation and suitable application behavior; it is not as direct as Reduced undifferentiated heavy lifting for the actual requirement to spend less staff effort maintaining generic infrastructure components.

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 Reduced undifferentiated heavy lifting for the actual requirement to spend less staff effort maintaining generic infrastructure components.

Resource pooling addresses the separate 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; it is not as direct as Reduced undifferentiated heavy lifting for the actual requirement to spend less staff effort maintaining generic infrastructure components.

Avoided data-center costs addresses the separate 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; it is not as direct as Rightsizing for the actual requirement to remove overprovisioning based on workload measurements.

Cost visibility addresses the separate need to understand resource expenses before changing deployment decisions because cost reporting and allocation tools can reveal spend drivers that are less apparent in a shared data center; it is not as direct as Rightsizing for the actual requirement to remove overprovisioning based on workload measurements.

Total cost of ownership (TCO) addresses the separate need to compare the full cost of different infrastructure approaches because a TCO analysis considers hardware, software, operations, labor, facilities and cloud usage; it is not as direct as Rightsizing for the actual requirement to remove overprovisioning based on workload measurements.

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 Cloud Adoption Framework (AWS CAF) for the actual requirement to structure the organizational changes needed for cloud adoption.

AWS Migration Hub addresses the separate need to track migration progress across applications and migration tools because migration Hub helps provide visibility across a portfolio's migration activity; it is not as direct as AWS Cloud Adoption Framework (AWS CAF) for the actual requirement to structure the organizational changes needed for cloud adoption.

AWS CAF Security perspective addresses the separate need to embed protection, risk practices and security capabilities into migration because the Security perspective helps establish security governance and resilient protective controls; it is not as direct as AWS Cloud Adoption Framework (AWS CAF) for the actual requirement to structure the organizational changes needed for cloud adoption.

That description belongs to Variable cloud costs because usage-based pricing lets spending change with resource consumption instead of requiring fixed purchased capacity; it is used to align consumption-based expense with actual usage, not to explain how Rightsizing provides the function to remove overprovisioning based on workload measurements.

That description belongs to Operating expenditure (OpEx) because opEx reflects spending as services and computing resources are consumed; it is used to treat recurring service consumption as a running operational cost, not to explain how Rightsizing provides the function to remove overprovisioning based on workload measurements.

That description belongs to Capital expenditure (CapEx) because capEx involves purchasing owned assets such as servers and data-center equipment before the benefits are consumed; it is used to recognize upfront infrastructure purchase as a fixed investment, not to explain how Rightsizing provides the function to remove overprovisioning based on workload measurements.

Elastic test environments addresses the separate need to scale test capacity up for an evaluation then stop consuming it because temporary cloud test resources can be provisioned and removed with demand; it is not as direct as Global reach for the actual requirement to serve customers in distant geographies with regional deployments.

Resource pooling addresses the separate 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; it is not as direct as Global reach for the actual requirement to serve customers in distant geographies with regional deployments.

Rapid global deployment addresses the separate need to make a proven application available in a newly targeted market quickly because cloud infrastructure in multiple geographic regions reduces the need to construct local facilities; it is not as direct as Global reach for the actual requirement to serve customers in distant geographies with regional deployments.

Vertical scaling addresses the separate need to increase the capacity of an existing compute resource because vertical scaling changes the size or power of one instance or server; it is not as direct as Sustainability pillar for the actual requirement to minimize environmental impact associated with running workloads.

Experiment-driven performance choices addresses the separate need to benchmark workload alternatives before standardizing a configuration because measurement of actual application behavior supports appropriate performance trade-offs; it is not as direct as Sustainability pillar for the actual requirement to minimize environmental impact associated with running workloads.

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 Sustainability pillar for the actual requirement to minimize environmental impact associated with running workloads.

Cost optimization pillar addresses the separate need to avoid unnecessary expenditure while achieving business outcomes because cost optimization focuses on understanding spend and delivering value at the right cost; it is not as direct as Sustainability pillar for the actual requirement to minimize environmental impact associated with running workloads.