That description belongs to AWS Lambda because lambda runs functions in managed execution environments with service-defined execution constraints; it is used to execute event-triggered code without managing virtual servers, not to explain how Application Load Balancer provides the function to route HTTP and HTTPS requests using application-layer rules.

That description belongs to Amazon EC2 because EC2 provides configurable compute instances where customers manage guest OS and application software; it is used to operate virtual servers with explicit OS and instance management, not to explain how Application Load Balancer provides the function to route HTTP and HTTPS requests using application-layer rules.

That description belongs to Horizontal EC2 scaling because horizontal scaling adds multiple instances that can share workload when architecture supports it; it is used to add parallel instance capacity for a distributed application, not to explain how Application Load Balancer provides the function to route HTTP and HTTPS requests using application-layer rules.

That description belongs to Availability Zone because an Availability Zone is one or more discrete data centers with independent infrastructure in a Region; it is used to separate redundant application components across isolated facilities within one Region, not to explain how AZ failure-domain separation provides the function to reduce correlated failures between redundant service nodes.

That description belongs to Application availability versus data durability because availability concerns whether a service is usable; durability concerns retaining stored data; it is used to separate immediate service accessibility from long-term data survival, not to explain how AZ failure-domain separation provides the function to reduce correlated failures between redundant service nodes.

That description belongs to Content delivery latency because cDN caching stores content nearer viewers and lowers repeat retrieval distance; it is used to reduce time to download reusable web assets in different countries, not to explain how AZ failure-domain separation provides the function to reduce correlated failures between redundant service nodes.

Amazon Q addresses a different objective, to offer generative AI assistance for supported business and developer workflows, because Amazon Q provides AI-powered assistant capabilities in integrated AWS settings; the checklist instead requires the distinct outcomes to choose an appropriate level of model customization; extract sentiment entities and other insights from text.

Amazon Athena addresses a different objective, to query supported data in S3 using serverless SQL, because athena runs interactive SQL queries without provisioning a dedicated database server; the checklist instead requires the distinct outcomes to choose an appropriate level of model customization; extract sentiment entities and other insights from text.

AWS Glue addresses a different objective, to discover prepare and integrate data across supported sources, because glue provides data integration workflows and a metadata Data Catalog; the checklist instead requires the distinct outcomes to choose an appropriate level of model customization; extract sentiment entities and other insights from text.

Dedicated circuit connectivity alone does not necessarily encrypt application traffic; that caveat is associated more closely with AWS Direct Connect for the need to establish dedicated private network connectivity from a site to AWS than with VPC Flow Logs for the requirement to capture metadata about traffic to and from network interfaces.

Creating a VPC does not automatically make every resource internet-accessible; that caveat is associated more closely with Amazon VPC for the need to create a logically isolated IP network for AWS resources than with VPC Flow Logs for the requirement to capture metadata about traffic to and from network interfaces.

Routes specify paths but do not grant application permissions or open firewall rules; that caveat is associated more closely with Route table for the need to decide where traffic from a subnet should be directed than with VPC Flow Logs for the requirement to capture metadata about traffic to and from network interfaces.

That description belongs to Amazon S3 because S3 is an object storage service for files and data blobs rather than mounted block devices; it is used to store durable objects and retrieve them by bucket and key, not to explain how Amazon S3 Standard-IA provides the function to store infrequently accessed objects that still need rapid retrieval.

That description belongs to Amazon S3 Standard because S3 Standard is appropriate for data requiring regular access across multiple AZs; it is used to serve frequently accessed objects with low-latency retrieval, not to explain how Amazon S3 Standard-IA provides the function to store infrequently accessed objects that still need rapid retrieval.

That description belongs to Amazon S3 One Zone-IA because one Zone-IA has a single-AZ resilience profile and lower storage cost; it is used to store recreatable infrequently accessed objects within one Availability Zone, not to explain how Amazon S3 Standard-IA provides the function to store infrequently accessed objects that still need rapid retrieval.

RDS Multi-AZ configuration addresses the separate need to improve database availability using a standby in another Availability Zone because RDS Multi-AZ options support failover when the primary or supporting infrastructure fails; it is not as direct as DynamoDB global tables for the actual requirement to provide multi-Region active-active replication for a DynamoDB application.

Amazon RDS addresses the separate need to operate a managed relational database engine because RDS automates selected relational database operations including backup and patching; it is not as direct as DynamoDB global tables for the actual requirement to provide multi-Region active-active replication for a DynamoDB application.

Heterogeneous database migration addresses the separate need to move between dissimilar database engines with possible schema translation because heterogeneous migration may require converting schema objects and application SQL; it is not as direct as DynamoDB global tables for the actual requirement to provide multi-Region active-active replication for a DynamoDB application.

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 DocumentDB provides the function to run JSON document workloads using MongoDB-compatible APIs.

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 DocumentDB provides the function to run JSON document workloads using MongoDB-compatible APIs.

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 DocumentDB provides the function to run JSON document workloads using MongoDB-compatible APIs.

That description belongs to AWS Lambda because lambda runs functions in managed execution environments with service-defined execution constraints; it is used to execute event-triggered code without managing virtual servers, not to explain how EC2 instance store provides the function to use temporary host-attached storage with very low latency.

That description belongs to Storage optimized EC2 instance because storage-optimized families offer specialized local storage performance for eligible workloads; it is used to run applications needing high local storage IOPS or throughput, not to explain how EC2 instance store provides the function to use temporary host-attached storage with very low latency.

That description belongs to Amazon EC2 because EC2 provides configurable compute instances where customers manage guest OS and application software; it is used to operate virtual servers with explicit OS and instance management, not to explain how EC2 instance store provides the function to use temporary host-attached storage with very low latency.

That description belongs to AWS Transit Gateway because transit Gateway simplifies hub-and-spoke network connectivity at scale; it is used to connect many VPCs and supported on-premises networks through a central hub, not to explain how AWS Site-to-Site VPN provides the function to connect office networks to AWS through encrypted tunnels over IP networks.

That description belongs to Gateway VPC endpoint because gateway endpoints provide private service paths for S3 and DynamoDB; it is used to connect a VPC to supported Amazon S3 or DynamoDB services through route-table entries, not to explain how AWS Site-to-Site VPN provides the function to connect office networks to AWS through encrypted tunnels over IP networks.

That description belongs to VPC endpoint because VPC endpoints provide service connectivity without requiring a public internet path; it is used to connect supported VPC workloads privately to selected AWS services, not to explain how AWS Site-to-Site VPN provides the function to connect office networks to AWS through encrypted tunnels over IP networks.

Amazon CloudFront is intended 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; in this design the new outcome is to deliver cached content closer to geographically dispersed end users, which calls for Edge location rather than Amazon CloudFront or the earlier Global IAM identity scope.

Global IAM identity scope primarily supports the earlier need to manage IAM identities used to authorize actions across AWS Regions because IAM is a global AWS service within an account, while service resources may be regional, but the new task is to deliver cached content closer to geographically dispersed end users; that is why Edge location is preferable here.

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 Global IAM identity scope.

Amazon Textract is intended to extract printed and handwritten text and document structure because textract reads forms tables and text from supported document inputs; in this design the new outcome is to identify positive negative or neutral tone in a document, which calls for Text sentiment classification rather than Amazon Textract or the earlier Amazon SageMaker AI.

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 identify positive negative or neutral tone in a document; that is why Text sentiment classification is preferable here.

Amazon OpenSearch Service is intended to search and analyze indexed logs and document collections because openSearch Service supports search analytics and log exploration; in this design the new outcome is to identify positive negative or neutral tone in a document, which calls for Text sentiment classification rather than Amazon OpenSearch Service or the earlier Amazon SageMaker AI.