That description belongs to Multi-AZ application deployment because replicated tiers across separate AZs reduce dependence on a single facility group; it is used to survive a failure confined to one Availability Zone, not to explain how Availability Zone provides the function to separate redundant application components across isolated facilities within one Region.

That description belongs to Regional disaster recovery tests because recovery exercises check replication, dependencies and traffic-routing procedures before a real incident; it is used to verify a workload can resume in its backup Region, not to explain how Availability Zone provides the function to separate redundant application components across isolated facilities within one Region.

That description belongs to Regional service availability check because AWS service availability varies by Region and sometimes by instance family or feature; it is used to verify a particular offering is available in the chosen Region, not to explain how Availability Zone provides the function to separate redundant application components across isolated facilities within one Region.

That description belongs to Amazon EMR because eMR provides managed cluster and serverless options for big-data processing; it is used to run supported big-data frameworks such as Apache Spark, not to explain how Amazon Athena provides the function to query supported data in S3 using serverless SQL.

That description belongs to AWS Glue because glue provides data integration workflows and a metadata Data Catalog; it is used to discover prepare and integrate data across supported sources, not to explain how Amazon Athena provides the function to query supported data in S3 using serverless SQL.

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 Athena provides the function to query supported data in S3 using serverless SQL.

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 adjust the number of matching EC2 instances as demand changes; that is why EC2 Auto Scaling is preferable here.

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 adjust the number of matching EC2 instances as demand changes, which calls for EC2 Auto Scaling rather than Amazon EC2 AMI or the earlier Horizontal EC2 scaling.

AWS Fargate is intended to run container tasks without managing EC2 container hosts because fargate supplies serverless compute for supported ECS and EKS workloads; in this design the new outcome is to adjust the number of matching EC2 instances as demand changes, which calls for EC2 Auto Scaling rather than AWS Fargate or the earlier Horizontal EC2 scaling.

Amazon ElastiCache is intended to cache frequently accessed application data in memory because elastiCache offers managed in-memory caching engines to reduce repetitive backend reads; in this design the new outcome is to analyze large structured data sets in a columnar warehouse, which calls for Amazon Redshift rather than Amazon ElastiCache or the earlier DynamoDB point-in-time recovery.

ACID relational transactions is intended to preserve multi-step data consistency in a relational workload because relational engines support transactional properties appropriate to tightly consistent operations; in this design the new outcome is to analyze large structured data sets in a columnar warehouse, which calls for Amazon Redshift rather than ACID relational transactions or the earlier DynamoDB point-in-time recovery.

DynamoDB point-in-time recovery primarily supports the earlier need to restore supported table data to a recent earlier point because pITR continuously backs up eligible DynamoDB table data for point-in-time restore within its retention window, but the new task is to analyze large structured data sets in a columnar warehouse; that is why Amazon Redshift is preferable here.

AWS DataSync primarily supports the earlier need to accelerate and automate transfers between supported storage locations because dataSync moves files or objects between on-premises and AWS storage systems with verification, but the new task is to optimize storage charges when object access patterns are unpredictable; that is why Amazon S3 Intelligent-Tiering is preferable here.

S3 pre-signed URL is intended to grant time-limited access to a specific object operation under signing credentials because a pre-signed URL encodes a limited request authorization with expiration; in this design the new outcome is to optimize storage charges when object access patterns are unpredictable, which calls for Amazon S3 Intelligent-Tiering rather than S3 pre-signed URL or the earlier AWS DataSync.

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 optimize storage charges when object access patterns are unpredictable, which calls for Amazon S3 Intelligent-Tiering rather than S3 Glacier Deep Archive or the earlier AWS DataSync.

Multi-Region architecture primarily supports the earlier need to address disaster recovery or geography-spanning application availability because deploying and replicating across Regions can isolate regional failures and serve separate markets, but the new task is to keep stored customer data in a selected geography; that is why Data residency by Region is preferable here.

Regional service scope is intended to recognize that many AWS resources exist only in a selected Region because regional services require selecting the location where supported resources are created; in this design the new outcome is to keep stored customer data in a selected geography, which calls for Data residency by Region rather than Regional service scope or the earlier Multi-Region architecture.

Low-latency regional placement is intended to locate dynamic application backends nearer a customer population because deploying compute and data in an appropriate Region can reduce geographic round-trip latency; in this design the new outcome is to keep stored customer data in a selected geography, which calls for Data residency by Region rather than Low-latency regional placement or the earlier Multi-Region architecture.

Private hosted zone addresses a different objective, to resolve private domain names inside associated VPC networks, because Route 53 private hosted zones provide DNS answers for selected VPCs; the checklist instead requires the distinct outcomes to provide private access to supported services across network boundaries; expose and manage HTTP REST or WebSocket APIs.

Route 53 latency routing addresses a different objective, to answer DNS requests with an endpoint selected for lower network latency, because latency-based policies choose among configured Region records using AWS latency observations; the checklist instead requires the distinct outcomes to provide private access to supported services across network boundaries; expose and manage HTTP REST or WebSocket APIs.

AWS Global Accelerator addresses a different objective, to improve global network paths and health-based endpoint selection using anycast IPs, because global Accelerator uses the AWS global network to route traffic to regional endpoints; the checklist instead requires the distinct outcomes to provide private access to supported services across network boundaries; expose and manage HTTP REST or WebSocket APIs.

EC2 dedicated host primarily supports the earlier need to place eligible instances on physical servers dedicated to one customer because dedicated Hosts provide visibility or control over host placement for some licensing requirements, but the new task is to relaunch instances from a defined system image; that is why Amazon EC2 AMI is preferable here.

EC2 Auto Scaling is intended to adjust the number of matching EC2 instances as demand changes because EC2 Auto Scaling can launch and terminate instances according to configured scaling policies; in this design the new outcome is to relaunch instances from a defined system image, which calls for Amazon EC2 AMI rather than EC2 Auto Scaling or the earlier EC2 dedicated host.

EC2 placement groups is intended to influence how supported instances are distributed across underlying hardware because placement groups support strategies for network performance or fault isolation; in this design the new outcome is to relaunch instances from a defined system image, which calls for Amazon EC2 AMI rather than EC2 placement groups or the earlier EC2 dedicated host.

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 extract sentiment entities and other insights from text, which calls for Amazon Comprehend rather than Amazon Translate or the earlier Amazon Athena.

Amazon Athena primarily supports the earlier need to query supported data in S3 using serverless SQL because athena runs interactive SQL queries without provisioning a dedicated database server, but the new task is to extract sentiment entities and other insights from text; that is why Amazon Comprehend is preferable here.

Amazon Transcribe is intended to convert spoken audio into a text transcript because transcribe provides managed automatic speech recognition; in this design the new outcome is to extract sentiment entities and other insights from text, which calls for Amazon Comprehend rather than Amazon Transcribe or the earlier Amazon Athena.

AWS Amplify addresses the separate need to build and host web or mobile application frontends with integrated workflows because amplify provides frontend deployment and backend integrations for app teams; it is not as direct as Amazon SNS for the actual requirement to fan out notifications to multiple subscribed endpoints.

AWS Systems Manager addresses the separate need to perform operational automation and inventory for fleets because systems Manager supplies run command automation patching and fleet management; it is not as direct as Amazon SNS for the actual requirement to fan out notifications to multiple subscribed endpoints.

AWS CodePipeline addresses the separate need to coordinate continuous delivery stages between tools because codePipeline orchestrates source build test and deployment actions; it is not as direct as Amazon SNS for the actual requirement to fan out notifications to multiple subscribed endpoints.

AWS CloudTrail addresses the separate need to audit supported AWS account activity and API operations because cloudTrail records AWS actions for governance and incident review; it is not as direct as Amazon SNS for the actual requirement to fan out notifications to multiple subscribed endpoints.

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.