That description belongs to RDS read replica because read replicas provide copies usable to serve read traffic with replication behavior; it is used to offload eligible read queries from a relational database primary, not to explain how RDS Multi-AZ configuration provides the function to improve database availability using a standby in another Availability Zone.

That description belongs to Database on Amazon EC2 because self-managing a database on EC2 leaves patching, backups and high availability largely to the customer; it is used to retain direct control of database host OS and engine installation, not to explain how RDS Multi-AZ configuration provides the function to improve database availability using a standby in another Availability Zone.

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 RDS Multi-AZ configuration provides the function to improve database availability using a standby in another Availability Zone.

AWS Management Console is intended to perform occasional AWS administration through a browser interface because the console provides graphical pages to view and configure AWS resources; in this design the new outcome is to offer approved infrastructure products through governed self-service, which calls for AWS Service Catalog rather than AWS Management Console or the earlier AWS service APIs.

AWS Cloud Development Kit (AWS CDK) is intended to define AWS infrastructure using familiar programming languages because AWS CDK constructs synthesize infrastructure definitions for deployment through CloudFormation; in this design the new outcome is to offer approved infrastructure products through governed self-service, which calls for AWS Service Catalog rather than AWS Cloud Development Kit (AWS CDK) or the earlier AWS service APIs.

AWS service APIs primarily supports the earlier need to interact programmatically with AWS using supported service requests because AWS APIs expose actions and resource operations through defined programmatic interfaces, but the new task is to offer approved infrastructure products through governed self-service; that is why AWS Service Catalog is preferable here.

Amazon FSx for Windows File Server primarily supports the earlier need to provide managed SMB file shares for Windows workloads because fSx for Windows File Server supports Windows file protocols and Active Directory integration, but the new task is to speed long-distance S3 uploads using AWS edge networking; that is why S3 Transfer Acceleration is preferable here.

Amazon S3 is intended to store durable objects and retrieve them by bucket and key because S3 is an object storage service for files and data blobs rather than mounted block devices; in this design the new outcome is to speed long-distance S3 uploads using AWS edge networking, which calls for S3 Transfer Acceleration rather than Amazon S3 or the earlier Amazon FSx for Windows File Server.

S3 Glacier Deep Archive is intended to retain long-lived archives at very low storage cost when restoration can be slow because deep Archive is designed for extremely infrequent access and long retention; in this design the new outcome is to speed long-distance S3 uploads using AWS edge networking, which calls for S3 Transfer Acceleration rather than S3 Glacier Deep Archive or the earlier Amazon FSx for Windows File Server.

RDS automated backups addresses a different objective, to enable managed point-in-time recovery for an eligible RDS database, because RDS backups and transaction logs support recovery within a configured retention period; the checklist instead requires the distinct outcomes to move data between database engines of the same general type; manage highly connected entities and their relationships as a graph.

DynamoDB global tables addresses a different objective, to provide multi-Region active-active replication for a DynamoDB application, because global tables replicate supported data across selected Regions for regional workloads; the checklist instead requires the distinct outcomes to move data between database engines of the same general type; manage highly connected entities and their relationships as a graph.

AWS Database Migration Service addresses a different objective, to move ongoing database data between supported source and destination engines, because AWS DMS can perform initial loading and change data capture for supported databases; the checklist instead requires the distinct outcomes to move data between database engines of the same general type; manage highly connected entities and their relationships as a graph.

Route 53 failover routing is intended to redirect DNS responses when monitored endpoint health changes because Route 53 health checks and failover policies can influence which healthy target a client resolves; in this design the new outcome is to direct clients to an endpoint using managed domain name resolution, which calls for Amazon Route 53 DNS rather than Route 53 failover routing or the earlier Availability Zone.

AWS Region is intended to select a geographic area in which to place a workload because an AWS Region is a distinct geographic location containing multiple Availability Zones; in this design the new outcome is to direct clients to an endpoint using managed domain name resolution, which calls for Amazon Route 53 DNS rather than AWS Region or the earlier Availability Zone.

Availability Zone primarily supports the earlier need to separate redundant application components across isolated facilities within one Region because an Availability Zone is one or more discrete data centers with independent infrastructure in a Region, but the new task is to direct clients to an endpoint using managed domain name resolution; that is why Amazon Route 53 DNS is preferable here.

That description belongs to Amazon Cognito because cognito supports application user directories and federation; it is used to provide sign-up sign-in and identity features for customer-facing applications, not to explain how Amazon Connect provides the function to run a cloud-based customer contact center.

That description belongs to Amazon SQS because sQS holds messages for consumers to process independently; it is used to decouple systems with durable asynchronous message queues, not to explain how Amazon Connect provides the function to run a cloud-based customer contact center.

That description belongs to AWS CodeBuild because codeBuild executes build environments without maintaining build servers; it is used to run continuous-integration builds and automated tests, not to explain how Amazon Connect provides the function to run a cloud-based customer contact center.

That description belongs to Amazon EC2 AMI because an Amazon Machine Image supplies a template for instance boot volumes and configuration; it is used to relaunch instances from a defined system image, not to explain how EC2 Auto Scaling provides the function to adjust the number of matching EC2 instances as demand changes.

That description belongs to Spot interruption handling because Spot capacity may be interrupted by AWS, so tasks should checkpoint or retry; it is used to design flexible EC2 workloads to withstand capacity reclamation, not to explain how EC2 Auto Scaling provides the function to adjust the number of matching EC2 instances as demand changes.

That description belongs to AWS Fargate because fargate supplies serverless compute for supported ECS and EKS workloads; it is used to run container tasks without managing EC2 container hosts, not to explain how EC2 Auto Scaling provides the function to adjust the number of matching EC2 instances as demand changes.

That description belongs to Amazon EFS because eFS supplies managed NFS file systems that can be accessed concurrently by supported clients; it is used to mount elastic shared file storage from multiple Linux workloads, not to explain how Amazon FSx for Windows File Server provides the function to provide managed SMB file shares for Windows workloads.

That description belongs to EBS versus EFS storage model because EBS offers block storage attached to instances; EFS offers a shared file system mounted over NFS; it is used to recognize block devices compared with managed network file systems, not to explain how Amazon FSx for Windows File Server provides the function to provide managed SMB file shares for Windows workloads.

That description belongs to AWS Elastic Disaster Recovery because elastic Disaster Recovery uses continuous block replication and orchestrated recovery; it is used to restore servers and workloads in AWS after an infrastructure disaster, not to explain how Amazon FSx for Windows File Server provides the function to provide managed SMB file shares for Windows workloads.

Interface VPC endpoint addresses a different objective, to reach supported services through private network interfaces in a subnet, because privateLink-backed endpoints create private IP endpoints with associated security groups; the checklist instead requires the distinct outcomes to answer DNS requests with an endpoint selected for lower network latency; connect many VPCs and supported on-premises networks through a central hub.

VPC endpoint addresses a different objective, to connect supported VPC workloads privately to selected AWS services, because VPC endpoints provide service connectivity without requiring a public internet path; the checklist instead requires the distinct outcomes to answer DNS requests with an endpoint selected for lower network latency; connect many VPCs and supported on-premises networks through a central hub.

Security group addresses a different objective, to enforce stateful inbound and outbound rules on supported resources, because security groups act as virtual firewalls associated with network interfaces; the checklist instead requires the distinct outcomes to answer DNS requests with an endpoint selected for lower network latency; connect many VPCs and supported on-premises networks through a central hub.

Amazon SageMaker AI primarily supports the earlier need to build train and deploy custom machine learning models because sageMaker AI offers managed tooling for ML data preparation training and inference workflows, but the new task is to act on measurements or clicks as they arrive; that is why Real-time event analytics is preferable here.

Amazon Lex is intended to build conversational chat or voice interfaces with intent recognition because lex supports conversational bots using natural language understanding; in this design the new outcome is to act on measurements or clicks as they arrive, which calls for Real-time event analytics rather than Amazon Lex or the earlier Amazon SageMaker AI.

Amazon Comprehend is intended to extract sentiment entities and other insights from text because comprehend provides managed natural-language processing APIs; in this design the new outcome is to act on measurements or clicks as they arrive, which calls for Real-time event analytics rather than Amazon Comprehend or the earlier Amazon SageMaker AI.

That description belongs to AWS Service Catalog because service Catalog lets administrators define centrally governed products users can launch; it is used to offer approved infrastructure products through governed self-service, not to explain how AWS Management Console provides the function to perform occasional AWS administration through a browser interface.

That description belongs to Manual console provisioning because the console suits an infrequent human-guided operation when repetition is not the priority; it is used to perform a one-off configuration with interactive review, not to explain how AWS Management Console provides the function to perform occasional AWS administration through a browser interface.

That description belongs to AWS CLI because the AWS Command Line Interface exposes AWS service operations to terminals and automation; it is used to run scripted AWS API operations from shell commands, not to explain how AWS Management Console provides the function to perform occasional AWS administration through a browser interface.