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 Avoid single points of failure provides the function to remove a single component whose outage would take down the whole system.

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 Avoid single points of failure provides the function to remove a single component whose outage would take down the whole system.

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 Avoid single points of failure provides the function to remove a single component whose outage would take down the whole system.

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 Return on investment (ROI) provides the function to evaluate expected financial benefit relative to an investment.

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 Return on investment (ROI) provides the function to evaluate expected financial benefit relative to an investment.

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 Return on investment (ROI) provides the function to evaluate expected financial benefit relative to an investment.

It is not limited to choosing the least expensive instance; that caveat is associated more closely with Operational excellence pillar for the need to improve how teams operate, monitor and continually refine workloads than with Operations as code for the requirement to apply controlled repeatable procedures to infrastructure and operations.

Collecting metrics alone is not improvement unless teams act on findings; that caveat is associated more closely with Frequent improvement loops for the need to use incidents and measurements to continually refine cloud operations than with Operations as code for the requirement to apply controlled repeatable procedures to infrastructure and operations.

Redundancy without access protection is not the same security objective; that caveat is associated more closely with Security pillar for the need to protect information, systems and assets using risk-aware controls than with Operations as code for the requirement to apply controlled repeatable procedures to infrastructure and operations.

Moving ongoing table changes is a separate database replication concern; that caveat is associated more closely with AWS Schema Conversion Tool (AWS SCT) for the need to convert database schema and code for a heterogeneous database migration than with Replatform for the requirement to make limited optimizations during migration without fully redesigning the application.

It does not intentionally rebuild the application's architecture around managed services; that caveat is associated more closely with Rehost (lift and shift) for the need to move an application to cloud infrastructure with minimal redesign than with Replatform for the requirement to make limited optimizations during migration without fully redesigning the application.

A tracking dashboard does not replace server or database transfer mechanisms; that caveat is associated more closely with AWS Migration Hub for the need to track migration progress across applications and migration tools than with Replatform for the requirement to make limited optimizations during migration without fully redesigning the application.

Elasticity is intended to increase and decrease capacity in response to changing demand because elasticity matches provisioned resources to workload demand, allowing capacity to contract after a spike; in this design the new outcome is to avoid administering an underlying platform for a common workload, which calls for Managed-service operational relief rather than Elasticity or the earlier On-demand resource availability.

Scalability is intended to support larger workloads by adding capacity as requirements grow because scalability is the ability of a system to handle growth by increasing resources or distributing work; in this design the new outcome is to avoid administering an underlying platform for a common workload, which calls for Managed-service operational relief rather than Scalability or the earlier On-demand resource availability.

On-demand resource availability primarily supports the earlier need to obtain computing resources when a new workload is ready to launch because cloud resources can be provisioned without owning and installing new data-center hardware first, but the new task is to avoid administering an underlying platform for a common workload; that is why Managed-service operational relief is preferable here.

Moving ongoing table changes is a separate database replication concern; that caveat is associated more closely with AWS Schema Conversion Tool (AWS SCT) for the need to convert database schema and code for a heterogeneous database migration than with AWS Prescriptive Guidance for the requirement to find practical AWS migration patterns and implementation guidance.

It is not primarily a workforce reskilling framework; that caveat is associated more closely with AWS CAF Security perspective for the need to embed protection, risk practices and security capabilities into migration than with AWS Prescriptive Guidance for the requirement to find practical AWS migration patterns and implementation guidance.

A tracking dashboard does not replace server or database transfer mechanisms; that caveat is associated more closely with AWS Migration Hub for the need to track migration progress across applications and migration tools than with AWS Prescriptive Guidance for the requirement to find practical AWS migration patterns and implementation guidance.

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

That description belongs to Geographic flexibility because AWS provides multiple Regions that can be selected for workloads and data; it is used to choose a physical deployment geography to address customers or regulatory constraints, not to explain how Self-service provisioning provides the function to create an environment without waiting for physical equipment installation.

That description belongs to Experimentation at low initial commitment because usage-based provisioning enables limited experiments that can be shut down if unsuccessful; it is used to test a prototype without large upfront infrastructure investment, not to explain how Self-service provisioning provides the function to create an environment without waiting for physical equipment installation.

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

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 Right-sized architecture.

Right-sized architecture primarily supports the earlier need to match provisioned resources to measured workload requirements because right sizing avoids both excess capacity and insufficient capacity for expected service levels, but the new task is to understand resource demand and quotas before workload demand exceeds limits; that is why Capacity awareness is preferable here.

Capital expenditure (CapEx) addresses a different objective, 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; the checklist instead requires the distinct outcomes to avoid running nonproduction compute unnecessarily; attribute cloud spending to teams and projects.

Spot capacity economics addresses a different objective, to save on flexible interruptible EC2 computing, because Spot Instances exploit spare EC2 capacity at discounted rates with interruption risk; the checklist instead requires the distinct outcomes to avoid running nonproduction compute unnecessarily; attribute cloud spending to teams and projects.

Cost allocation ownership addresses a different objective, to make cloud expenditure traceable to a responsible department, because accounts, tags and reports can help identify which teams or products generate spend; the checklist instead requires the distinct outcomes to avoid running nonproduction compute unnecessarily; attribute cloud spending to teams and projects.

Performance efficiency pillar addresses a different objective, 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; the checklist instead requires the distinct outcomes to remove a single component whose outage would take down the whole system; understand resource demand and quotas before workload demand exceeds limits; match provisioned resources to measured workload requirements.

Design for failure addresses a different objective, to plan for individual components or zones becoming unavailable, because resilient cloud designs anticipate disruption and use isolation and recovery behavior; the checklist instead requires the distinct outcomes to remove a single component whose outage would take down the whole system; understand resource demand and quotas before workload demand exceeds limits; match provisioned resources to measured workload requirements.

Infrastructure observability addresses a different objective, to make system behavior visible through meaningful operational metrics and logs, because useful telemetry helps teams detect performance changes and failures early; the checklist instead requires the distinct outcomes to remove a single component whose outage would take down the whole system; understand resource demand and quotas before workload demand exceeds limits; match provisioned resources to measured workload requirements.

Refactor or re-architect is intended 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; in this design the new outcome is to move an application to cloud infrastructure with minimal redesign, which calls for Rehost (lift and shift) rather than Refactor or re-architect or the earlier AWS Application Migration Service.

AWS Application Migration Service primarily supports the earlier 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, but the new task is to move an application to cloud infrastructure with minimal redesign; that is why Rehost (lift and shift) 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 move an application to cloud infrastructure with minimal redesign, which calls for Rehost (lift and shift) rather than AWS Database Migration Service (AWS DMS) or the earlier AWS Application Migration Service.