Amazon CloudFront addresses the separate need to cache web content at distributed edge locations near viewers because cloudFront is a content delivery network that caches eligible content at global edge sites; it is not as direct as Route 53 failover routing for the actual requirement to redirect DNS responses when monitored endpoint health changes.

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 Route 53 failover routing for the actual requirement to redirect DNS responses when monitored endpoint health changes.

Amazon Route 53 DNS addresses the separate need to direct clients to an endpoint using managed domain name resolution because Route 53 answers DNS queries according to hosted-zone records and routing policies; it is not as direct as Route 53 failover routing for the actual requirement to redirect DNS responses when monitored endpoint health changes.

That description belongs to Amazon Bedrock because bedrock provides access to foundation models and tooling for generative AI solutions; it is used to build generative AI applications using foundation models through managed APIs, not to explain how Amazon Lex provides the function to build conversational chat or voice interfaces with intent recognition.

That description belongs to Amazon Comprehend because comprehend provides managed natural-language processing APIs; it is used to extract sentiment entities and other insights from text, not to explain how Amazon Lex provides the function to build conversational chat or voice interfaces with intent recognition.

That description belongs to Amazon SageMaker AI because sageMaker AI offers managed tooling for ML data preparation training and inference workflows; it is used to build train and deploy custom machine learning models, not to explain how Amazon Lex provides the function to build conversational chat or voice interfaces with intent recognition.

That description belongs to Amazon DynamoDB because DynamoDB is a fully managed NoSQL database with service-managed infrastructure; it is used to store key-value or document data with managed NoSQL scaling, not to explain how Amazon Neptune provides the function to manage highly connected entities and their relationships as a graph.

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 Amazon Neptune provides the function to manage highly connected entities and their relationships as a graph.

That description belongs to Amazon Aurora because aurora is a managed relational database with distributed storage and supported compatibility modes; it is used to use a cloud-optimized relational engine compatible with MySQL or PostgreSQL, not to explain how Amazon Neptune provides the function to manage highly connected entities and their relationships as a graph.

CloudFront origin is intended to provide the source from which edge caches fetch content on a miss because a CloudFront distribution retrieves objects or responses from a configured origin when needed; in this design the new outcome is to deliver cached content closer to geographically dispersed end users, which calls for Edge location rather than CloudFront origin or the earlier Amazon CloudFront.

Amazon CloudFront primarily supports the earlier need to cache web content at distributed edge locations near viewers because cloudFront is a content delivery network that caches eligible content at global edge sites, but the new task is to deliver cached content closer to geographically dispersed end users; that is why Edge location is preferable here.

AWS Local Zones is intended to place supported resources closer to large population centers where a full Region is farther away because local Zones extend certain AWS services near end users while connected to a parent Region; in this design the new outcome is to deliver cached content closer to geographically dispersed end users, which calls for Edge location rather than AWS Local Zones or the earlier Amazon CloudFront.

EBS versus EFS storage model primarily supports the earlier need to recognize block devices compared with managed network file systems because EBS offers block storage attached to instances; EFS offers a shared file system mounted over NFS, but the new task is to back up an EBS volume to durable AWS-managed snapshot storage; that is why EBS snapshot is preferable here.

EBS volume encryption is intended to protect block storage with supported at-rest encryption because encrypted EBS volumes use integrated key management for data at rest; in this design the new outcome is to back up an EBS volume to durable AWS-managed snapshot storage, which calls for EBS snapshot rather than EBS volume encryption or the earlier EBS versus EFS storage model.

AWS Storage Gateway is intended to connect on-premises applications to cloud-backed storage interfaces because storage Gateway supports hybrid file volume and tape integration scenarios; in this design the new outcome is to back up an EBS volume to durable AWS-managed snapshot storage, which calls for EBS snapshot rather than AWS Storage Gateway or the earlier EBS versus EFS storage model.

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 let private subnet resources initiate eligible outbound internet connections; connect two VPCs privately for their routable address ranges.

Internet gateway addresses a different objective, 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; the checklist instead requires the distinct outcomes to let private subnet resources initiate eligible outbound internet connections; connect two VPCs privately for their routable address ranges.

Private subnet addresses a different objective, to place backend resources without a direct internet gateway route, because a private subnet can reach only the networks available through its route table; the checklist instead requires the distinct outcomes to let private subnet resources initiate eligible outbound internet connections; connect two VPCs privately for their routable address ranges.

It focuses on hosted applications rather than full persistent virtual desktops; that caveat is associated more closely with Amazon AppStream 2.0 for the need to stream hosted desktop applications to end users than with Amazon Cognito for the requirement to provide sign-up sign-in and identity features for customer-facing applications.

It is not primarily an email relay or a backend task queue; that caveat is associated more closely with Amazon Connect for the need to run a cloud-based customer contact center than with Amazon Cognito for the requirement to provide sign-up sign-in and identity features for customer-facing applications.

Virtual desktop delivery is distinct from publishing one application stream; that caveat is associated more closely with Amazon WorkSpaces for the need to provide managed cloud virtual desktop environments than with Amazon Cognito for the requirement to provide sign-up sign-in and identity features for customer-facing applications.

That description belongs to AWS Management Console because the console provides graphical pages to view and configure AWS resources; it is used to perform occasional AWS administration through a browser interface, not to explain how AWS Control Tower provides the function to establish and govern a multi-account landing zone.

That description belongs to AWS CloudFormation because cloudFormation models resources as stacks and applies managed creation and update operations; it is used to recreate multi-resource infrastructure from versioned templates, not to explain how AWS Control Tower provides the function to establish and govern a multi-account landing zone.

That description belongs to AWS Organizations because organizations groups accounts for governance and consolidated billing; it is used to centrally manage accounts rather than configuring each account independently, not to explain how AWS Control Tower provides the function to establish and govern a multi-account landing zone.

Amazon EC2 AMI is intended to relaunch instances from a defined system image because an Amazon Machine Image supplies a template for instance boot volumes and configuration; in this design the new outcome is to place eligible instances on physical servers dedicated to one customer, which calls for EC2 dedicated host rather than Amazon EC2 AMI or the earlier Reserved Instances.

Amazon EC2 is intended to operate virtual servers with explicit OS and instance management because EC2 provides configurable compute instances where customers manage guest OS and application software; in this design the new outcome is to place eligible instances on physical servers dedicated to one customer, which calls for EC2 dedicated host rather than Amazon EC2 or the earlier Reserved Instances.

Reserved Instances primarily supports the earlier need to obtain eligible EC2 billing discounts for committed usage attributes because reserved Instances are a pricing mechanism for eligible instance usage commitments, but the new task is to place eligible instances on physical servers dedicated to one customer; that is why EC2 dedicated host is preferable here.

That description belongs to Amazon Aurora because aurora is a managed relational database with distributed storage and supported compatibility modes; it is used to use a cloud-optimized relational engine compatible with MySQL or PostgreSQL, not to explain how ACID relational transactions provides the function to preserve multi-step data consistency in a relational workload.

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 ACID relational transactions provides the function to preserve multi-step data consistency in a relational workload.

That description belongs to Database engine choice by use case because AWS purpose-built databases span relational key-value document graph and in-memory patterns; it is used to match persistence technology to workload queries and consistency needs, not to explain how ACID relational transactions provides the function to preserve multi-step data consistency in a relational workload.

AWS Local Zones addresses the separate need to place supported resources closer to large population centers where a full Region is farther away because local Zones extend certain AWS services near end users while connected to a parent Region; it is not as direct as Regional jurisdiction planning for the actual requirement to select deployment geography to align with applicable organizational requirements.

CloudFront origin addresses the separate need to provide the source from which edge caches fetch content on a miss because a CloudFront distribution retrieves objects or responses from a configured origin when needed; it is not as direct as Regional jurisdiction planning for the actual requirement to select deployment geography to align with applicable organizational requirements.

Regional disaster recovery tests addresses the separate need to verify a workload can resume in its backup Region because recovery exercises check replication, dependencies and traffic-routing procedures before a real incident; it is not as direct as Regional jurisdiction planning for the actual requirement to select deployment geography to align with applicable organizational requirements.