Spot capacity economics primarily supports the earlier need to save on flexible interruptible EC2 computing because Spot Instances exploit spare EC2 capacity at discounted rates with interruption risk, but the new task is to obtain eligible compute discounts in exchange for a spending commitment; that is why Savings Plans commitment is preferable here.

Resource tagging for accountability is intended to attribute cloud spending to teams and projects because consistent resource tags support reporting and ownership when activated for cost allocation; in this design the new outcome is to obtain eligible compute discounts in exchange for a spending commitment, which calls for Savings Plans commitment rather than Resource tagging for accountability or the earlier Spot capacity economics.

Automation of shutdown schedules is intended to avoid running nonproduction compute unnecessarily because scheduled automation can stop or remove eligible idle resources when they are not required; in this design the new outcome is to obtain eligible compute discounts in exchange for a spending commitment, which calls for Savings Plans commitment rather than Automation of shutdown schedules or the earlier Spot capacity economics.

That description belongs to On-demand resource availability because cloud resources can be provisioned without owning and installing new data-center hardware first; it is used to obtain computing resources when a new workload is ready to launch, not to explain how Managed-service operational relief provides the function to avoid administering an underlying platform for a common workload.

That description belongs to Scalability because scalability is the ability of a system to handle growth by increasing resources or distributing work; it is used to support larger workloads by adding capacity as requirements grow, not to explain how Managed-service operational relief provides the function to avoid administering an underlying platform for a common workload.

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 Managed-service operational relief provides the function to avoid administering an underlying platform for a common workload.

AWS CAF Governance perspective addresses the separate need to manage transformation risks, priorities and portfolio decisions because the Governance perspective addresses decision-making, program oversight and value management; it is not as direct as AWS CAF Business perspective for the actual requirement to connect cloud adoption to business outcomes and investment decisions.

Migration dependency mapping addresses the separate need to identify which applications and infrastructure components rely on one another because dependency discovery helps group and sequence migrations to avoid broken integrations; it is not as direct as AWS CAF Business perspective for the actual requirement to connect cloud adoption to business outcomes and investment decisions.

AWS Application Migration Service addresses the separate need to replicate source servers for a largely lift-and-shift migration because application Migration Service supports server migration with continuous replication and automated conversion to run on AWS; it is not as direct as AWS CAF Business perspective for the actual requirement to connect cloud adoption to business outcomes and investment decisions.

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 CAF Business perspective for the actual requirement to connect cloud adoption to business outcomes and investment decisions.

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 Total cost of ownership (TCO) provides the function to compare the full cost of different infrastructure approaches.

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 Total cost of ownership (TCO) provides the function to compare the full cost of different infrastructure approaches.

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 Total cost of ownership (TCO) provides the function to compare the full cost of different infrastructure approaches.

Durability is intended to reduce the likelihood of losing stored information over time because durability measures protection against permanent data loss and typically uses resilient storage design; in this design the new outcome is to release a customer-facing capability with less infrastructure lead time, which calls for Faster time to market rather than Durability 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 release a customer-facing capability with less infrastructure lead time; that is why Faster time to market is preferable here.

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 release a customer-facing capability with less infrastructure lead time, which calls for Faster time to market rather than Fault tolerance or the earlier Resource pooling.

That description belongs to Experiment-driven performance choices because measurement of actual application behavior supports appropriate performance trade-offs; it is used to benchmark workload alternatives before standardizing a configuration, not to explain how Capacity awareness provides the function to understand resource demand and quotas before workload demand exceeds limits.

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 Capacity awareness provides the function to understand resource demand and quotas before workload demand exceeds limits.

That description belongs to Vertical scaling because vertical scaling changes the size or power of one instance or server; it is used to increase the capacity of an existing compute resource, not to explain how Capacity awareness provides the function to understand resource demand and quotas before workload demand exceeds limits.

AWS Application Migration Service addresses the separate need to replicate source servers for a largely lift-and-shift migration because application Migration Service supports server migration with continuous replication and automated conversion to run on AWS; it is not as direct as Repurchase for the actual requirement to replace an existing application with a different software product or SaaS solution.

AWS Prescriptive Guidance addresses the separate need to find practical AWS migration patterns and implementation guidance because prescriptive Guidance provides proven strategies and technical patterns for cloud adoption; it is not as direct as Repurchase for the actual requirement to replace an existing application with a different software product or SaaS solution.

Refactor or re-architect addresses the separate need 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; it is not as direct as Repurchase for the actual requirement to replace an existing application with a different software product or SaaS solution.

Retire addresses the separate need to remove an application that no longer delivers sufficient business value because retirement eliminates unneeded systems from the future estate; it is not as direct as Repurchase for the actual requirement to replace an existing application with a different software product or SaaS solution.

Avoided data-center costs is intended to reduce expenses for facility space, power, cooling and physical maintenance because migrating suitable workloads can shift responsibility for physical facility operation to AWS; in this design the new outcome is to understand resource expenses before changing deployment decisions, which calls for Cost visibility rather than Avoided data-center costs or the earlier Demand forecasting.

Demand forecasting primarily supports the earlier need to estimate future usage to avoid unplanned commitment or capacity decisions because forecasts help teams plan spend and procurement based on usage trends, but the new task is to understand resource expenses before changing deployment decisions; that is why Cost visibility 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 understand resource expenses before changing deployment decisions, which calls for Cost visibility rather than Capital expenditure (CapEx) or the earlier Demand forecasting.

Elastic test environments addresses a different objective, to scale test capacity up for an evaluation then stop consuming it, because temporary cloud test resources can be provisioned and removed with demand; the checklist instead requires the distinct outcomes to serve customers in distant geographies with regional deployments; test a prototype without large upfront infrastructure investment.

Durability addresses a different objective, to reduce the likelihood of losing stored information over time, because durability measures protection against permanent data loss and typically uses resilient storage design; the checklist instead requires the distinct outcomes to serve customers in distant geographies with regional deployments; test a prototype without large upfront infrastructure investment.

Geographic flexibility addresses a different objective, 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; the checklist instead requires the distinct outcomes to serve customers in distant geographies with regional deployments; test a prototype without large upfront infrastructure investment.

AWS CAF Operations perspective primarily supports the earlier need to prepare support, monitoring and service operations for migrated workloads because the Operations perspective develops capabilities for operating workloads effectively, but the new task is to establish technical foundations for hosting and building cloud workloads; that is why AWS CAF Platform perspective is preferable here.

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 establish technical foundations for hosting and building cloud workloads, which calls for AWS CAF Platform perspective rather than AWS Cloud Adoption Framework (AWS CAF) or the earlier AWS CAF Operations perspective.

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 establish technical foundations for hosting and building cloud workloads, which calls for AWS CAF Platform perspective rather than AWS CAF Business perspective or the earlier AWS CAF Operations perspective.

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 spread work across additional independent resources; that is why Horizontal scaling 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 spread work across additional independent resources, which calls for Horizontal scaling rather than Right-sized architecture or the earlier Security pillar.

Performance efficiency pillar is intended 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; in this design the new outcome is to spread work across additional independent resources, which calls for Horizontal scaling rather than Performance efficiency pillar or the earlier Security pillar.