DynamoDB global tables addresses the separate need to provide multi-Region active-active replication for a DynamoDB application because global tables replicate supported data across selected Regions for regional workloads; it is not as direct as Amazon DynamoDB for the actual requirement to store key-value or document data with managed NoSQL scaling.

Amazon DocumentDB addresses the separate need to run JSON document workloads using MongoDB-compatible APIs because documentDB offers managed document database capabilities for suitable MongoDB workloads; it is not as direct as Amazon DynamoDB for the actual requirement to store key-value or document data with managed NoSQL scaling.

Amazon ElastiCache addresses the separate need to cache frequently accessed application data in memory because elastiCache offers managed in-memory caching engines to reduce repetitive backend reads; it is not as direct as Amazon DynamoDB for the actual requirement to store key-value or document data with managed NoSQL scaling.

Amazon AppStream 2.0 addresses the separate need to stream hosted desktop applications to end users because appStream 2.0 streams supported applications through a browser or client; it is not as direct as AWS X-Ray for the actual requirement to trace distributed requests through supported application components.

AWS CloudTrail addresses the separate need to audit supported AWS account activity and API operations because cloudTrail records AWS actions for governance and incident review; it is not as direct as AWS X-Ray for the actual requirement to trace distributed requests through supported application components.

AWS Systems Manager addresses the separate need to perform operational automation and inventory for fleets because systems Manager supplies run command automation patching and fleet management; it is not as direct as AWS X-Ray for the actual requirement to trace distributed requests through supported application components.

That description belongs to AWS service APIs because AWS APIs expose actions and resource operations through defined programmatic interfaces; it is used to interact programmatically with AWS using supported service requests, not to explain how AWS SDKs provides the function to integrate AWS service requests directly into application source code.

That description belongs to AWS Elastic Beanstalk because elastic Beanstalk orchestrates supporting AWS resources for supported web application platforms; it is used to deploy application code with managed environment provisioning, not to explain how AWS SDKs provides the function to integrate AWS service requests directly into application source code.

That description belongs to AWS CodePipeline because codePipeline coordinates supported actions across a delivery workflow; it is used to orchestrate source-to-deployment stages automatically, not to explain how AWS SDKs provides the function to integrate AWS service requests directly into application source code.

Amazon EMR addresses the separate need to run supported big-data frameworks such as Apache Spark because eMR provides managed cluster and serverless options for big-data processing; it is not as direct as AWS Glue for the actual requirement to discover prepare and integrate data across supported sources.

Amazon Bedrock addresses the separate need to build generative AI applications using foundation models through managed APIs because bedrock provides access to foundation models and tooling for generative AI solutions; it is not as direct as AWS Glue for the actual requirement to discover prepare and integrate data across supported sources.

Data lake on Amazon S3 addresses the separate need to collect diverse raw and processed datasets in object storage because S3 can serve as a central durable layer for data lake architectures; it is not as direct as AWS Glue for the actual requirement to discover prepare and integrate data across supported sources.

That description belongs to AWS Database Migration Service because AWS DMS can perform initial loading and change data capture for supported databases; it is used to move ongoing database data between supported source and destination engines, not to explain how AWS Schema Conversion Tool provides the function to translate supported database schemas and code for heterogeneous migrations.

That description belongs to RDS Multi-AZ configuration because RDS Multi-AZ options support failover when the primary or supporting infrastructure fails; it is used to improve database availability using a standby in another Availability Zone, not to explain how AWS Schema Conversion Tool provides the function to translate supported database schemas and code for heterogeneous migrations.

That description belongs to Amazon RDS because RDS automates selected relational database operations including backup and patching; it is used to operate a managed relational database engine, not to explain how AWS Schema Conversion Tool provides the function to translate supported database schemas and code for heterogeneous migrations.

Repeatable deployment pipeline is intended to apply the same deployment process across development and production because automated workflows reduce configuration drift between environments by executing controlled steps; in this design the new outcome is to orchestrate source-to-deployment stages automatically, which calls for AWS CodePipeline rather than Repeatable deployment pipeline or the earlier Manual console provisioning.

Manual console provisioning primarily supports the earlier need to perform a one-off configuration with interactive review because the console suits an infrequent human-guided operation when repetition is not the priority, but the new task is to orchestrate source-to-deployment stages automatically; that is why AWS CodePipeline is preferable here.

AWS SDKs is intended to integrate AWS service requests directly into application source code because sDKs provide language libraries and request handling for application integrations with AWS APIs; in this design the new outcome is to orchestrate source-to-deployment stages automatically, which calls for AWS CodePipeline rather than AWS SDKs or the earlier Manual console provisioning.

Memory optimized EC2 instance addresses a different objective, to support applications with large in-memory working sets, because memory-optimized families provide higher RAM-to-vCPU ratios for memory-bound applications; the checklist instead requires the distinct outcomes to run applications needing high local storage IOPS or throughput; obtain eligible EC2 billing discounts for committed usage attributes; operate virtual servers with explicit OS and instance management.

Horizontal EC2 scaling addresses a different objective, to add parallel instance capacity for a distributed application, because horizontal scaling adds multiple instances that can share workload when architecture supports it; the checklist instead requires the distinct outcomes to run applications needing high local storage IOPS or throughput; obtain eligible EC2 billing discounts for committed usage attributes; operate virtual servers with explicit OS and instance management.

Amazon Lightsail addresses a different objective, to launch simple virtual servers with bundled management and predictable plans, because lightsail packages compute networking and storage for straightforward applications; the checklist instead requires the distinct outcomes to run applications needing high local storage IOPS or throughput; obtain eligible EC2 billing discounts for committed usage attributes; operate virtual servers with explicit OS and instance management.

AWS Global Accelerator addresses the separate need to route user traffic toward healthy regional endpoints through AWS global network paths because global Accelerator uses static anycast IP addresses and endpoint health information to improve availability and performance; it is not as direct as Availability Zone for the actual requirement to separate redundant application components across isolated facilities within one Region.

Application availability versus data durability addresses the separate need to separate immediate service accessibility from long-term data survival because availability concerns whether a service is usable; durability concerns retaining stored data; it is not as direct as Availability Zone for the actual requirement to separate redundant application components across isolated facilities within one Region.

AWS Region addresses the separate need to select a geographic area in which to place a workload because an AWS Region is a distinct geographic location containing multiple Availability Zones; it is not as direct as Availability Zone for the actual requirement to separate redundant application components across isolated facilities within one Region.

Data residency by Region addresses the separate need to keep stored customer data in a selected geography because region placement and configured replication determine where supported AWS workload data resides; it is not as direct as Availability Zone for the actual requirement to separate redundant application components across isolated facilities within one Region.

AWS IoT Device Management addresses a different objective, to organize and manage fleets of supported connected devices, because ioT device management capabilities help register organize and monitor connected devices; the checklist instead requires the distinct outcomes to perform operational automation and inventory for fleets; route events from producers to targets using event patterns.

AWS Developer Tools addresses a different objective, to recognize the separation of build release deploy and tracing functions, because AWS developer services specialize in different steps of software delivery; the checklist instead requires the distinct outcomes to perform operational automation and inventory for fleets; route events from producers to targets using event patterns.

AWS Service Catalog addresses a different objective, to offer provisionable approved products to internal teams, because service Catalog enables controlled self-service of predefined infrastructure products; the checklist instead requires the distinct outcomes to perform operational automation and inventory for fleets; route events from producers to targets using event patterns.

That description belongs to EBS volume encryption because encrypted EBS volumes use integrated key management for data at rest; it is used to protect block storage with supported at-rest encryption, not to explain how AWS Backup provides the function to centrally manage backup plans across supported AWS resources.

That description belongs to S3 server-side encryption because S3 encrypts stored object data at rest and supports key-management choices; it is used to encrypt S3 object data at rest using supported key arrangements, not to explain how AWS Backup provides the function to centrally manage backup plans across supported AWS resources.

That description belongs to AWS DataSync because dataSync moves files or objects between on-premises and AWS storage systems with verification; it is used to accelerate and automate transfers between supported storage locations, not to explain how AWS Backup provides the function to centrally manage backup plans across supported AWS resources.

VPC endpoint primarily supports the earlier need to connect supported VPC workloads privately to selected AWS services because VPC endpoints provide service connectivity without requiring a public internet path, but the new task is to resolve application domain names and apply supported DNS routing policies; that is why Amazon Route 53 is preferable here.

Security group is intended to enforce stateful inbound and outbound rules on supported resources because security groups act as virtual firewalls associated with network interfaces; in this design the new outcome is to resolve application domain names and apply supported DNS routing policies, which calls for Amazon Route 53 rather than Security group or the earlier VPC endpoint.

Internet gateway is intended to enable internet routing for resources in a VPC with suitable configuration because an internet gateway connects a VPC to the internet for eligible public addressing paths; in this design the new outcome is to resolve application domain names and apply supported DNS routing policies, which calls for Amazon Route 53 rather than Internet gateway or the earlier VPC endpoint.