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 Security pillar for the actual requirement to protect information, systems and assets using risk-aware controls.

Automate recovery addresses the separate need to restore normal application behavior without waiting for routine manual intervention because automated detection and recovery reduce the time needed to handle predictable failure conditions; it is not as direct as Security pillar for the actual requirement to protect information, systems and assets using risk-aware controls.

Capacity awareness addresses the separate need to understand resource demand and quotas before workload demand exceeds limits because good reliability planning accounts for capacity needs and service quotas; it is not as direct as Security pillar for the actual requirement to protect information, systems and assets using risk-aware controls.

That description belongs to Global reach because AWS Regions allow workloads to run closer to users in multiple geographic markets; it is used to serve customers in distant geographies with regional deployments, not to explain how Geographic flexibility provides the function to choose a physical deployment geography to address customers or regulatory constraints.

That description belongs to Elasticity because elasticity matches provisioned resources to workload demand, allowing capacity to contract after a spike; it is used to increase and decrease capacity in response to changing demand, not to explain how Geographic flexibility provides the function to choose a physical deployment geography to address customers or regulatory constraints.

That description belongs to Self-service provisioning because authorized teams can provision cloud resources through APIs or a console when they are needed; it is used to create an environment without waiting for physical equipment installation, not to explain how Geographic flexibility provides the function to choose a physical deployment geography to address customers or regulatory constraints.

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 prepare support, monitoring and service operations for migrated workloads; that is why AWS CAF Operations perspective is preferable here.

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 Database Migration Service (AWS DMS).

AWS CAF People perspective is intended to prepare the workforce and organizational culture for cloud transformation because the People perspective addresses skills, roles, workforce transformation and change management; 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 People perspective or the earlier AWS Database Migration Service (AWS DMS).

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 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 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 Continuous performance tuning.

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

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 Platform perspective provides the function to establish technical foundations for hosting and building cloud workloads.

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 Platform perspective provides the function to establish technical foundations for hosting and building cloud workloads.

That description belongs to Elastic test environments because temporary cloud test resources can be provisioned and removed with demand; it is used to scale test capacity up for an evaluation then stop consuming it, not to explain how Scalability provides the function to support larger workloads by adding capacity as requirements grow.

That description belongs to Agility because cloud agility shortens the time between a business idea and an available environment through on-demand provisioning; it is used to experiment and deploy new ideas without a long hardware procurement cycle, not to explain how Scalability provides the function to support larger workloads by adding capacity as requirements grow.

That description belongs to Elasticity because elasticity matches provisioned resources to workload demand, allowing capacity to contract after a spike; it is used to increase and decrease capacity in response to changing demand, not to explain how Scalability provides the function to support larger workloads by adding capacity as requirements grow.

Return on investment (ROI) is intended to evaluate expected financial benefit relative to an investment because rOI compares gains with associated investment costs for a business decision; 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 Return on investment (ROI) or the earlier Capital expenditure (CapEx).

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 Capital expenditure (CapEx).

Capital expenditure (CapEx) primarily supports the earlier 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, but the new task is to benefit from infrastructure purchasing and operations at provider scale; that is why Economies of scale is preferable here.

Faster time to market addresses the separate need to release a customer-facing capability with less infrastructure lead time because on-demand delivery of infrastructure helps shorten build and launch cycles; it is not as direct as Experimentation at low initial commitment for the actual requirement to test a prototype without large upfront infrastructure investment.

Geographic flexibility addresses the separate need to choose a physical deployment geography to address customers or regulatory constraints because AWS provides multiple Regions that can be selected for workloads and data; it is not as direct as Experimentation at low initial commitment for the actual requirement to test a prototype without large upfront infrastructure investment.

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 Experimentation at low initial commitment for the actual requirement to test a prototype without large upfront infrastructure investment.

Operating expenditure (OpEx) is intended to treat recurring service consumption as a running operational cost because opEx reflects spending as services and computing resources are consumed; in this design the new outcome is to align consumption-based expense with actual usage, which calls for Variable cloud costs rather than Operating expenditure (OpEx) or the earlier Avoided data-center costs.

Rightsizing is intended to remove overprovisioning based on workload measurements because rightsizing matches compute or storage capacity to real demand and performance needs; in this design the new outcome is to align consumption-based expense with actual usage, which calls for Variable cloud costs rather than Rightsizing or the earlier Avoided data-center costs.

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 align consumption-based expense with actual usage; that is why Variable cloud costs is preferable here.

That description belongs to Operations as code because machine-readable definitions allow review, versioning and consistent execution of operations; it is used to apply controlled repeatable procedures to infrastructure and operations, not to explain how Frequent improvement loops provides the function to use incidents and measurements to continually refine cloud operations.

That description belongs to Security pillar because the security pillar addresses identities, detection, infrastructure and data protection, and incident response; it is used to protect information, systems and assets using risk-aware controls, not to explain how Frequent improvement loops provides the function to use incidents and measurements to continually refine cloud operations.

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 Frequent improvement loops provides the function to use incidents and measurements to continually refine cloud operations.

That description belongs to AWS CAF Operations perspective because the Operations perspective develops capabilities for operating workloads effectively; it is used to prepare support, monitoring and service operations for migrated workloads, not to explain how Business continuity during migration provides the function to plan service availability and rollback while changing environments.

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 Business continuity during migration provides the function to plan service availability and rollback while changing environments.

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 Business continuity during migration provides the function to plan service availability and rollback while changing environments.