AWS CLI is intended to run scripted AWS API operations from shell commands because the AWS Command Line Interface exposes AWS service operations to terminals and automation; in this design the new outcome is to run AWS-managed infrastructure at a customer premises for local requirements, which calls for AWS Outposts rather than AWS CLI or the earlier AWS CloudFormation.

AWS CloudFormation primarily supports the earlier need to recreate multi-resource infrastructure from versioned templates because cloudFormation models resources as stacks and applies managed creation and update operations, but the new task is to run AWS-managed infrastructure at a customer premises for local requirements; that is why AWS Outposts is preferable here.

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 run AWS-managed infrastructure at a customer premises for local requirements, which calls for AWS Outposts rather than AWS Cloud Development Kit (AWS CDK) or the earlier AWS CloudFormation.

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 search and analyze indexed logs and document collections, which calls for Amazon OpenSearch Service rather than Amazon Textract or the earlier Text sentiment classification.

Text sentiment classification primarily supports the earlier need to identify positive negative or neutral tone in a document because managed NLP sentiment analysis assesses the emotional polarity of text, but the new task is to search and analyze indexed logs and document collections; that is why Amazon OpenSearch Service is preferable here.

Amazon Rekognition is intended to analyze image or video content for objects and visual attributes because rekognition offers managed computer-vision detection and analysis APIs; in this design the new outcome is to search and analyze indexed logs and document collections, which calls for Amazon OpenSearch Service rather than Amazon Rekognition or the earlier Text sentiment classification.

Regional service availability check is intended to verify a particular offering is available in the chosen Region because AWS service availability varies by Region and sometimes by instance family or feature; in this design the new outcome is to place supported resources closer to large population centers where a full Region is farther away, which calls for AWS Local Zones rather than Regional service availability check or the earlier Regional service scope.

Regional service scope primarily supports the earlier need to recognize that many AWS resources exist only in a selected Region because regional services require selecting the location where supported resources are created, but the new task is to place supported resources closer to large population centers where a full Region is farther away; that is why AWS Local Zones is preferable here.

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 place supported resources closer to large population centers where a full Region is farther away, which calls for AWS Local Zones rather than AWS Region or the earlier Regional service scope.

S3 Block Public Access addresses the separate need to help prevent unintended public access to buckets and objects because block Public Access settings override or restrict public access paths where enabled; it is not as direct as EBS snapshot for the actual requirement to back up an EBS volume to durable AWS-managed snapshot storage.

Amazon EFS addresses the separate need to mount elastic shared file storage from multiple Linux workloads because eFS supplies managed NFS file systems that can be accessed concurrently by supported clients; it is not as direct as EBS snapshot for the actual requirement to back up an EBS volume to durable AWS-managed snapshot storage.

Amazon S3 Object Lock addresses the separate need to enforce supported WORM retention against object deletion or modification because object Lock supports retention modes and legal holds on eligible S3 object versions; it is not as direct as EBS snapshot for the actual requirement to back up an EBS volume to durable AWS-managed snapshot storage.

Database on Amazon EC2 is intended to retain direct control of database host OS and engine installation because self-managing a database on EC2 leaves patching, backups and high availability largely to the customer; in this design the new outcome is to use a cloud-optimized relational engine compatible with MySQL or PostgreSQL, which calls for Amazon Aurora rather than Database on Amazon EC2 or the earlier RDS read replica.

Amazon DocumentDB is intended to run JSON document workloads using MongoDB-compatible APIs because documentDB offers managed document database capabilities for suitable MongoDB workloads; in this design the new outcome is to use a cloud-optimized relational engine compatible with MySQL or PostgreSQL, which calls for Amazon Aurora rather than Amazon DocumentDB or the earlier RDS read replica.

RDS read replica primarily supports the earlier need to offload eligible read queries from a relational database primary because read replicas provide copies usable to serve read traffic with replication behavior, but the new task is to use a cloud-optimized relational engine compatible with MySQL or PostgreSQL; that is why Amazon Aurora is preferable here.

AWS Organizations addresses the separate need to centrally manage accounts rather than configuring each account independently because organizations groups accounts for governance and consolidated billing; it is not as direct as AWS Control Tower for the actual requirement to establish and govern a multi-account landing zone.

AWS service APIs addresses the separate need to interact programmatically with AWS using supported service requests because AWS APIs expose actions and resource operations through defined programmatic interfaces; it is not as direct as AWS Control Tower for the actual requirement to establish and govern a multi-account landing zone.

AWS CodePipeline addresses the separate need to orchestrate source-to-deployment stages automatically because codePipeline coordinates supported actions across a delivery workflow; it is not as direct as AWS Control Tower for the actual requirement to establish and govern a multi-account landing zone.

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 convert spoken audio into a text transcript, which calls for Amazon Transcribe rather than Amazon Textract or the earlier Amazon Comprehend.

Amazon Comprehend primarily supports the earlier need to extract sentiment entities and other insights from text because comprehend provides managed natural-language processing APIs, but the new task is to convert spoken audio into a text transcript; that is why Amazon Transcribe is preferable here.

Amazon Translate is intended to translate text between supported human languages because translate is a machine-translation service used by multilingual applications; in this design the new outcome is to convert spoken audio into a text transcript, which calls for Amazon Transcribe rather than Amazon Translate or the earlier Amazon Comprehend.

That description belongs to Private hosted zone because Route 53 private hosted zones provide DNS answers for selected VPCs; it is used to resolve private domain names inside associated VPC networks, not to explain how AWS Client VPN provides the function to provide individual remote users with a managed VPN connection to AWS or attached networks.

That description belongs to AWS PrivateLink because privateLink carries traffic using VPC endpoint connectivity without public exposure; it is used to provide private access to supported services across network boundaries, not to explain how AWS Client VPN provides the function to provide individual remote users with a managed VPN connection to AWS or attached networks.

That description belongs to AWS Site-to-Site VPN because site-to-Site VPN establishes IPsec tunnels between a customer network and AWS connectivity endpoints; it is used to connect office networks to AWS through encrypted tunnels over IP networks, not to explain how AWS Client VPN provides the function to provide individual remote users with a managed VPN connection to AWS or attached networks.

Horizontal EC2 scaling primarily supports the earlier need to add parallel instance capacity for a distributed application because horizontal scaling adds multiple instances that can share workload when architecture supports it, but the new task is to design flexible EC2 workloads to withstand capacity reclamation; that is why Spot interruption handling is preferable here.

Vertical EC2 scaling is intended to increase resource capacity by changing the instance type because vertical scaling provides more CPU or RAM within a single virtual machine; in this design the new outcome is to design flexible EC2 workloads to withstand capacity reclamation, which calls for Spot interruption handling rather than Vertical EC2 scaling or the earlier Horizontal EC2 scaling.

Elasticity through scaling policies is intended to match compute capacity to traffic fluctuations automatically because metric-driven policies can change running capacity in response to utilization or demand; in this design the new outcome is to design flexible EC2 workloads to withstand capacity reclamation, which calls for Spot interruption handling rather than Elasticity through scaling policies or the earlier Horizontal EC2 scaling.

Amazon EventBridge primarily supports the earlier need to route events from producers to targets using event patterns because eventBridge provides event buses and rule-based matching for supported events, but the new task is to distinguish event streams from independently consumed queued tasks; that is why Amazon Kinesis versus SQS is preferable here.

Amazon SQS is intended to decouple systems with durable asynchronous message queues because sQS holds messages for consumers to process independently; in this design the new outcome is to distinguish event streams from independently consumed queued tasks, which calls for Amazon Kinesis versus SQS rather than Amazon SQS or the earlier Amazon EventBridge.

Amazon SNS is intended to fan out notifications to multiple subscribed endpoints because sNS uses topics and subscriptions to publish messages to multiple destinations; in this design the new outcome is to distinguish event streams from independently consumed queued tasks, which calls for Amazon Kinesis versus SQS rather than Amazon SNS or the earlier Amazon EventBridge.

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.