Network Load Balancer primarily supports the earlier need to handle high-performance connection-level TCP or UDP traffic because nLB routes connections at the transport layer and supports static IP behavior, but the new task is to deploy supported applications while the platform provisions common resources; that is why AWS Elastic Beanstalk is preferable here.

Amazon ECS is intended to orchestrate containerized applications using AWS-managed control capabilities because eCS schedules and manages containers in clusters on supported launch types; in this design the new outcome is to deploy supported applications while the platform provisions common resources, which calls for AWS Elastic Beanstalk rather than Amazon ECS or the earlier Network Load Balancer.

Memory optimized EC2 instance is intended to support applications with large in-memory working sets because memory-optimized families provide higher RAM-to-vCPU ratios for memory-bound applications; in this design the new outcome is to deploy supported applications while the platform provisions common resources, which calls for AWS Elastic Beanstalk rather than Memory optimized EC2 instance or the earlier Network Load Balancer.

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 Amazon Textract for the actual requirement to extract printed and handwritten text and document structure.

Data catalog metadata addresses the separate need to discover schemas and locations of datasets for analytics engines because a data catalog records metadata used by compatible query and ETL tools; it is not as direct as Amazon Textract for the actual requirement to extract printed and handwritten text and document structure.

Amazon OpenSearch Service addresses the separate need to search and analyze indexed logs and document collections because openSearch Service supports search analytics and log exploration; it is not as direct as Amazon Textract for the actual requirement to extract printed and handwritten text and document structure.

NAT gateway addresses the separate need to let private subnet resources initiate eligible outbound internet connections because a NAT gateway translates egress traffic when appropriate routes are configured; it is not as direct as AWS Client VPN for the actual requirement to provide individual remote users with a managed VPN connection to AWS or attached networks.

Network ACL addresses the separate need to apply stateless allow and deny rules at the subnet boundary because network ACLs evaluate subnet traffic using ordered rules in each direction; it is not as direct as AWS Client VPN for the actual requirement to provide individual remote users with a managed VPN connection to AWS or attached networks.

AWS Transit Gateway addresses the separate need to connect many VPCs and supported on-premises networks through a central hub because transit Gateway simplifies hub-and-spoke network connectivity at scale; it is not as direct as AWS Client VPN for the actual requirement to provide individual remote users with a managed VPN connection to AWS or attached networks.

Route 53 weighted routing addresses the separate need to distribute DNS responses among configured endpoints according to weights because weighted routing directs shares of DNS answers toward configured records; it is not as direct as AWS Client VPN for the actual requirement to provide individual remote users with a managed VPN connection to AWS or attached networks.

That description belongs to Amazon Translate because translate is a machine-translation service used by multilingual applications; it is used to translate text between supported human languages, not to explain how Amazon Polly provides the function to convert written text into natural-sounding spoken audio.

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 Polly provides the function to convert written text into natural-sounding spoken audio.

That description belongs to Amazon Textract because textract reads forms tables and text from supported document inputs; it is used to extract printed and handwritten text and document structure, not to explain how Amazon Polly provides the function to convert written text into natural-sounding spoken audio.

Amazon ECS is intended to orchestrate containerized applications using AWS-managed control capabilities because eCS schedules and manages containers in clusters on supported launch types; in this design the new outcome is to support applications with large in-memory working sets, which calls for Memory optimized EC2 instance rather than Amazon ECS or the earlier General purpose EC2 instance.

Compute optimized EC2 instance is intended to provide comparatively more CPU resources for CPU-intensive applications because compute-optimized instance families emphasize processing power for compute-bound tasks; in this design the new outcome is to support applications with large in-memory working sets, which calls for Memory optimized EC2 instance rather than Compute optimized EC2 instance or the earlier General purpose EC2 instance.

General purpose EC2 instance primarily supports the earlier need to balance CPU memory and networking for broadly mixed workloads because general-purpose instances provide a balanced resource profile without specializing in one bottleneck, but the new task is to support applications with large in-memory working sets; that is why Memory optimized EC2 instance is preferable here.

Amazon Cognito addresses the separate need to provide sign-up sign-in and identity features for customer-facing applications because cognito supports application user directories and federation; it is not as direct as Amazon Connect for the actual requirement to run a cloud-based customer contact center.

Amazon Kinesis versus SQS addresses the separate need to distinguish event streams from independently consumed queued tasks because kinesis is oriented toward ordered streaming data while SQS supports decoupled message processing; it is not as direct as Amazon Connect for the actual requirement to run a cloud-based customer contact center.

Amazon WorkSpaces addresses the separate need to provide managed cloud virtual desktop environments because workSpaces delivers desktop computing to remote users; it is not as direct as Amazon Connect for the actual requirement to run a cloud-based customer contact center.

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 Configuration drift detection provides the function to identify when deployed resources diverge from defined templates.

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 Configuration drift detection provides the function to identify when deployed resources diverge from defined templates.

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 Configuration drift detection provides the function to identify when deployed resources diverge from defined templates.

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 accelerate and automate transfers between supported storage locations, which calls for AWS DataSync rather than AWS Storage Gateway or the earlier EBS volume encryption.

EBS volume encryption primarily supports the earlier need to protect block storage with supported at-rest encryption because encrypted EBS volumes use integrated key management for data at rest, but the new task is to accelerate and automate transfers between supported storage locations; that is why AWS DataSync is preferable here.

S3 server-side encryption is intended to encrypt S3 object data at rest using supported key arrangements because S3 encrypts stored object data at rest and supports key-management choices; in this design the new outcome is to accelerate and automate transfers between supported storage locations, which calls for AWS DataSync rather than S3 server-side encryption or the earlier EBS volume encryption.

RDS read replica addresses a different objective, to offload eligible read queries from a relational database primary, because read replicas provide copies usable to serve read traffic with replication behavior; the checklist instead requires the distinct outcomes to design a database around known key lookups and throughput patterns; cache frequently accessed application data in memory.

AWS Migration Hub addresses a different objective, to track multiple migration activities in one view, because migration Hub centralizes migration progress information from supported tools; the checklist instead requires the distinct outcomes to design a database around known key lookups and throughput patterns; cache frequently accessed application data in memory.

Homogeneous database migration addresses a different objective, to move data between database engines of the same general type, because a homogeneous migration usually involves compatible source and target database engines; the checklist instead requires the distinct outcomes to design a database around known key lookups and throughput patterns; cache frequently accessed application data in memory.

That description belongs to Route table because VPC route tables contain destination-prefix routing entries for network traffic; it is used to decide where traffic from a subnet should be directed, not to explain how VPC Flow Logs provides the function to capture metadata about traffic to and from network interfaces.

That description belongs to Amazon VPC because a VPC defines virtual networking boundaries and hosts configurable subnets and routing; it is used to create a logically isolated IP network for AWS resources, not to explain how VPC Flow Logs provides the function to capture metadata about traffic to and from network interfaces.

That description belongs to Interface VPC endpoint because privateLink-backed endpoints create private IP endpoints with associated security groups; it is used to reach supported services through private network interfaces in a subnet, not to explain how VPC Flow Logs provides the function to capture metadata about traffic to and from network interfaces.

Regional disaster recovery tests is intended to verify a workload can resume in its backup Region because recovery exercises check replication, dependencies and traffic-routing procedures before a real incident; in this design the new outcome is to select a geographic area in which to place a workload, which calls for AWS Region rather than Regional disaster recovery tests or the earlier CloudFront origin.

CloudFront origin primarily supports the earlier 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, but the new task is to select a geographic area in which to place a workload; that is why AWS Region is preferable here.

Regional jurisdiction planning is intended to select deployment geography to align with applicable organizational requirements because region choices can help address jurisdictional and contractual requirements for where workloads run; in this design the new outcome is to select a geographic area in which to place a workload, which calls for AWS Region rather than Regional jurisdiction planning or the earlier CloudFront origin.