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 AWS Backup for the actual requirement to centrally manage backup plans across supported AWS resources.

EC2 instance store addresses the separate need to hold scratch data temporarily on host-attached disks because instance store provides fast ephemeral data storage tied to the host; it is not as direct as AWS Backup for the actual requirement to centrally manage backup plans across supported AWS resources.

Amazon S3 addresses the separate need to store durable objects and retrieve them by bucket and key because S3 is an object storage service for files and data blobs rather than mounted block devices; it is not as direct as AWS Backup for the actual requirement to centrally manage backup plans across supported AWS resources.

S3 lifecycle rule addresses the separate need to transition or expire objects automatically based on age and criteria because lifecycle configuration can move objects into eligible classes or delete them on schedule; it is not as direct as AWS Backup for the actual requirement to centrally manage backup plans across supported AWS resources.

That description belongs to AWS Direct Connect because direct Connect provides a dedicated network connection through supported locations; it is used to establish dedicated private network connectivity from a site to AWS, not to explain how AWS Global Accelerator provides the function to improve global network paths and health-based endpoint selection using anycast IPs.

That description belongs to Route 53 latency routing because latency-based policies choose among configured Region records using AWS latency observations; it is used to answer DNS requests with an endpoint selected for lower network latency, not to explain how AWS Global Accelerator provides the function to improve global network paths and health-based endpoint selection using anycast IPs.

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 AWS Global Accelerator provides the function to improve global network paths and health-based endpoint selection using anycast IPs.

AWS Service Catalog addresses the separate need to offer provisionable approved products to internal teams because service Catalog enables controlled self-service of predefined infrastructure products; it is not as direct as Amazon EventBridge for the actual requirement to route events from producers to targets using event patterns.

Amazon CloudWatch addresses the separate need to observe metrics logs alarms and events for running resources because cloudWatch helps monitor AWS workloads and alert on selected conditions; it is not as direct as Amazon EventBridge for the actual requirement to route events from producers to targets using event patterns.

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 EventBridge for the actual requirement to route events from producers to targets using event patterns.

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 Quick provides the function to create dashboards and business intelligence visualizations.

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 Quick provides the function to create dashboards and business intelligence visualizations.

That description belongs to Amazon Q because Amazon Q provides AI-powered assistant capabilities in integrated AWS settings; it is used to offer generative AI assistance for supported business and developer workflows, not to explain how Amazon Quick provides the function to create dashboards and business intelligence visualizations.

That description belongs to Cross-Region replication because cross-Region replication moves eligible objects or database data into a different geography when configured; it is used to maintain copies of selected data outside its source Region, not to explain how CloudFront origin provides the function to provide the source from which edge caches fetch content on a miss.

That description belongs to Amazon CloudFront because cloudFront is a content delivery network that caches eligible content at global edge sites; it is used to cache web content at distributed edge locations near viewers, not to explain how CloudFront origin provides the function to provide the source from which edge caches fetch content on a miss.

That description belongs to AWS Region because an AWS Region is a distinct geographic location containing multiple Availability Zones; it is used to select a geographic area in which to place a workload, not to explain how CloudFront origin provides the function to provide the source from which edge caches fetch content on a miss.

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 Manual console provisioning provides the function to perform a one-off configuration with interactive review.

That description belongs to AWS CloudFormation change sets because change sets preview resource modifications CloudFormation plans to make; it is used to review proposed stack changes before executing them, not to explain how Manual console provisioning provides the function to perform a one-off configuration with interactive review.

That description belongs to AWS CloudWatch dashboards because dashboards visualize metrics and alarms for monitored systems; it is used to inspect selected operational measurements in one view, not to explain how Manual console provisioning provides the function to perform a one-off configuration with interactive review.

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 move data between database engines of the same general type, which calls for Homogeneous database migration rather than Amazon ElastiCache or the earlier AWS Database Migration Service.

AWS Database Migration Service primarily supports the earlier need to move ongoing database data between supported source and destination engines because AWS DMS can perform initial loading and change data capture for supported databases, but the new task is to move data between database engines of the same general type; that is why Homogeneous database migration is preferable here.

Amazon RDS is intended to operate a managed relational database engine because RDS automates selected relational database operations including backup and patching; in this design the new outcome is to move data between database engines of the same general type, which calls for Homogeneous database migration rather than Amazon RDS or the earlier AWS Database Migration Service.

Amazon Redshift primarily supports the earlier need to analyze large structured data sets in a columnar warehouse because redshift provides a cloud data warehouse optimized for analytical SQL workloads, but the new task is to cache frequently accessed application data in memory; that is why Amazon ElastiCache is preferable here.

DynamoDB global tables is intended to provide multi-Region active-active replication for a DynamoDB application because global tables replicate supported data across selected Regions for regional workloads; in this design the new outcome is to cache frequently accessed application data in memory, which calls for Amazon ElastiCache rather than DynamoDB global tables or the earlier Amazon Redshift.

DynamoDB point-in-time recovery is intended 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; in this design the new outcome is to cache frequently accessed application data in memory, which calls for Amazon ElastiCache rather than DynamoDB point-in-time recovery or the earlier Amazon Redshift.

Amazon Connect primarily supports the earlier need to run a cloud-based customer contact center because connect supplies hosted omnichannel contact-center capabilities, but the new task is to observe metrics logs alarms and events for running resources; that is why Amazon CloudWatch 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 observe metrics logs alarms and events for running resources, which calls for Amazon CloudWatch rather than Amazon SQS or the earlier Amazon Connect.

Amazon EventBridge is intended to route events from producers to targets using event patterns because eventBridge provides event buses and rule-based matching for supported events; in this design the new outcome is to observe metrics logs alarms and events for running resources, which calls for Amazon CloudWatch rather than Amazon EventBridge or the earlier Amazon Connect.

S3 multi-part upload addresses the separate need to upload very large objects as separately transmitted parts because Multi-part upload improves resilience and transfer management for large S3 objects; it is not as direct as S3 Glacier Flexible Retrieval for the actual requirement to archive data with retrieval time measured in minutes to hours.

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 S3 Glacier Flexible Retrieval for the actual requirement to archive data with retrieval time measured in minutes to hours.

S3 Glacier Deep Archive addresses the separate need 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; it is not as direct as S3 Glacier Flexible Retrieval for the actual requirement to archive data with retrieval time measured in minutes to hours.

A Region selection determines geography but does not automatically make an application multi-Region; that caveat is associated more closely with AWS Region for the need to select a geographic area in which to place a workload than with AWS Global Accelerator for the requirement to route user traffic toward healthy regional endpoints through AWS global network paths.

An edge site is not a full substitute for application compute in an AWS Region; that caveat is associated more closely with Edge location for the need to deliver cached content closer to geographically dispersed end users than with AWS Global Accelerator for the requirement to route user traffic toward healthy regional endpoints through AWS global network paths.

Multiple AZs help with facility-level failures without being geographically separate Regions; that caveat is associated more closely with Availability Zone for the need to separate redundant application components across isolated facilities within one Region than with AWS Global Accelerator for the requirement to route user traffic toward healthy regional endpoints through AWS global network paths.