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.

Security pillar addresses the separate 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; it is not as direct as Frequent improvement loops for the actual requirement to use incidents and measurements to continually refine cloud operations.

Horizontal scaling addresses the separate need to spread work across additional independent resources because horizontal scaling increases the number of workers or instances serving a workload; it is not as direct as Frequent improvement loops for the actual requirement to use incidents and measurements to continually refine cloud operations.

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

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

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

Automation of shutdown schedules addresses the separate need to avoid running nonproduction compute unnecessarily because scheduled automation can stop or remove eligible idle resources when they are not required; it is not as direct as Bring Your Own License (BYOL) for the actual requirement to reuse eligible existing software licenses under applicable provider terms.

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 Bring Your Own License (BYOL) for the actual requirement to reuse eligible existing software licenses under applicable provider terms.

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 Bring Your Own License (BYOL) for the actual requirement to reuse eligible existing software licenses under applicable provider terms.

Faster time to market is intended to release a customer-facing capability with less infrastructure lead time because on-demand delivery of infrastructure helps shorten build and launch cycles; in this design the new outcome is to benefit from provider-managed shared infrastructure without operating a dedicated facility, which calls for Resource pooling rather than Faster time to market or the earlier Reduced undifferentiated heavy lifting.

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 benefit from provider-managed shared infrastructure without operating a dedicated facility, which calls for Resource pooling rather than Self-service provisioning or the earlier Reduced undifferentiated heavy lifting.

Reduced undifferentiated heavy lifting primarily supports the earlier need to spend less staff effort maintaining generic infrastructure components because managed AWS services take over selected operational tasks such as platform maintenance, but the new task is to benefit from provider-managed shared infrastructure without operating a dedicated facility; that is why Resource pooling is preferable here.

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 Replatform for the actual requirement to make limited optimizations during migration without fully redesigning the application.

Rehost (lift and shift) addresses the separate need to move an application to cloud infrastructure with minimal redesign because rehosting relocates a workload while largely preserving its existing architecture; it is not as direct as Replatform for the actual requirement to make limited optimizations during migration without fully redesigning the application.

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 Replatform for the actual requirement to make limited optimizations during migration without fully redesigning the application.

That description belongs to AWS Migration Hub because migration Hub helps provide visibility across a portfolio's migration activity; it is used to track migration progress across applications and migration tools, not to explain how AWS Schema Conversion Tool (AWS SCT) provides the function to convert database schema and code for a heterogeneous database migration.

That description belongs to AWS Prescriptive Guidance because prescriptive Guidance provides proven strategies and technical patterns for cloud adoption; it is used to find practical AWS migration patterns and implementation guidance, not to explain how AWS Schema Conversion Tool (AWS SCT) provides the function to convert database schema and code for a heterogeneous database migration.

That description belongs to AWS Database Migration Service (AWS DMS) because AWS DMS supports migration and ongoing replication for suitable database engines; it is used to move or replicate database data to a supported target, not to explain how AWS Schema Conversion Tool (AWS SCT) provides the function to convert database schema and code for a heterogeneous database migration.

That description belongs to Performance efficiency pillar because performance efficiency includes choosing suitable technologies and maintaining efficient resource use as demand changes; it is used to select and adapt resources to meet performance needs efficiently, not to explain how Security pillar provides the function to protect information, systems and assets using risk-aware controls.

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

That description belongs to Reliability pillar because reliability covers recovery, capacity planning and resilience to infrastructure or service disruption; it is used to help a workload recover from failures and continue functioning correctly, not to explain how Security pillar provides the function to protect information, systems and assets using risk-aware controls.

Elasticity primarily supports the earlier need 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, but the new task is to obtain computing resources when a new workload is ready to launch; that is why On-demand resource availability is preferable here.

Agility is intended to experiment and deploy new ideas without a long hardware procurement cycle because cloud agility shortens the time between a business idea and an available environment through on-demand provisioning; in this design the new outcome is to obtain computing resources when a new workload is ready to launch, which calls for On-demand resource availability rather than Agility or the earlier Elasticity.

Managed-service operational relief is intended to avoid administering an underlying platform for a common workload because managed services move specific tasks such as database engine patching to AWS; in this design the new outcome is to obtain computing resources when a new workload is ready to launch, which calls for On-demand resource availability rather than Managed-service operational relief or the earlier Elasticity.

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 License-included pricing provides the function to pay for software license rights as part of an eligible cloud service charge.

That description belongs to Savings Plans commitment because savings Plans provide discounts for qualifying usage during a commitment term; it is used to obtain eligible compute discounts in exchange for a spending commitment, not to explain how License-included pricing provides the function to pay for software license rights as part of an eligible cloud service charge.

That description belongs to Bring Your Own License (BYOL) because bYOL can let a customer apply eligible licenses to suitable cloud deployments; it is used to reuse eligible existing software licenses under applicable provider terms, not to explain how License-included pricing provides the function to pay for software license rights as part of an eligible cloud service charge.

Experimentation at low initial commitment is intended to test a prototype without large upfront infrastructure investment because usage-based provisioning enables limited experiments that can be shut down if unsuccessful; 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 Experimentation at low initial commitment or the earlier Durability.

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 Durability.

Durability primarily supports the earlier need to reduce the likelihood of losing stored information over time because durability measures protection against permanent data loss and typically uses resilient storage design, 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.

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 match provisioned resources to measured workload requirements, which calls for Right-sized architecture rather than Horizontal scaling or the earlier Resource-efficient software.

Resource-efficient software primarily supports the earlier need to avoid unnecessary processing and storage when delivering the same output because reducing wasted computation contributes to performance and sustainability objectives, but the new task is to match provisioned resources to measured workload requirements; that is why Right-sized architecture is preferable here.

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 match provisioned resources to measured workload requirements, which calls for Right-sized architecture rather than Experiment-driven performance choices or the earlier Resource-efficient software.