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.

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 perform occasional AWS administration through a browser interface, which calls for AWS Management Console rather than AWS CLI or the earlier Manual console provisioning.

AWS Service Catalog is intended to offer approved infrastructure products through governed self-service because service Catalog lets administrators define centrally governed products users can launch; in this design the new outcome is to perform occasional AWS administration through a browser interface, which calls for AWS Management Console rather than AWS Service Catalog or the earlier Manual console provisioning.

Manual console provisioning primarily supports the earlier need to perform a one-off configuration with interactive review because the console suits an infrequent human-guided operation when repetition is not the priority, but the new task is to perform occasional AWS administration through a browser interface; that is why AWS Management Console is preferable here.

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 Gateway VPC endpoint provides the function to connect a VPC to supported Amazon S3 or DynamoDB services through route-table entries.

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 Gateway VPC endpoint provides the function to connect a VPC to supported Amazon S3 or DynamoDB services through route-table entries.

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 Gateway VPC endpoint provides the function to connect a VPC to supported Amazon S3 or DynamoDB services through route-table entries.

S3 bucket policy primarily supports the earlier need to control allowed and denied access to an S3 bucket and its objects because bucket policies are resource-based JSON permissions for supported S3 actions, but the new task is to help prevent unintended public access to buckets and objects; that is why S3 Block Public Access is preferable here.

Amazon S3 Inventory is intended to generate lists of objects and associated metadata for analysis because S3 Inventory produces scheduled reports about bucket objects and properties; in this design the new outcome is to help prevent unintended public access to buckets and objects, which calls for S3 Block Public Access rather than Amazon S3 Inventory or the earlier S3 bucket policy.

Amazon S3 is intended 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; in this design the new outcome is to help prevent unintended public access to buckets and objects, which calls for S3 Block Public Access rather than Amazon S3 or the earlier S3 bucket policy.

Database engine choice by use case addresses the separate need to match persistence technology to workload queries and consistency needs because AWS purpose-built databases span relational key-value document graph and in-memory patterns; it is not as direct as Database on Amazon EC2 for the actual requirement to retain direct control of database host OS and engine installation.

AWS Database Migration Service addresses the separate 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; it is not as direct as Database on Amazon EC2 for the actual requirement to retain direct control of database host OS and engine installation.

Homogeneous database migration addresses the separate need to move data between database engines of the same general type because a homogeneous migration usually involves compatible source and target database engines; it is not as direct as Database on Amazon EC2 for the actual requirement to retain direct control of database host OS and engine installation.

Region outage planning primarily supports the earlier need to prepare recovery beyond failure of one Availability Zone because a regional recovery design uses another Region and explicit data and traffic recovery plans, but the new task is to verify a particular offering is available in the chosen Region; that is why Regional service availability check 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 verify a particular offering is available in the chosen Region, which calls for Regional service availability check rather than Regional service scope or the earlier Region outage planning.

Cross-Region replication is intended to maintain copies of selected data outside its source Region because cross-Region replication moves eligible objects or database data into a different geography when configured; in this design the new outcome is to verify a particular offering is available in the chosen Region, which calls for Regional service availability check rather than Cross-Region replication or the earlier Region outage planning.

AWS Step Functions addresses the separate need to coordinate multi-step application workflows with managed state because step Functions orchestrates service integrations and branching steps over time; it is not as direct as AWS Amplify for the actual requirement to build and host web or mobile application frontends with integrated workflows.

AWS Developer Tools addresses the separate need to recognize the separation of build release deploy and tracing functions because AWS developer services specialize in different steps of software delivery; it is not as direct as AWS Amplify for the actual requirement to build and host web or mobile application frontends with integrated workflows.

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 AWS Amplify for the actual requirement to build and host web or mobile application frontends with integrated workflows.

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 Pretrained AI API versus custom ML provides the function to choose an appropriate level of model customization.

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 Pretrained AI API versus custom ML provides the function to choose an appropriate level of model customization.

That description belongs to Amazon Lex because lex supports conversational bots using natural language understanding; it is used to build conversational chat or voice interfaces with intent recognition, not to explain how Pretrained AI API versus custom ML provides the function to choose an appropriate level of model customization.

Application Load Balancer is intended to route HTTP and HTTPS requests using application-layer rules because aLB supports layer 7 routing by host names or URL paths to target groups; in this design the new outcome is to add parallel instance capacity for a distributed application, which calls for Horizontal EC2 scaling rather than Application Load Balancer or the earlier Elasticity through scaling policies.

Amazon EC2 is intended to operate virtual servers with explicit OS and instance management because EC2 provides configurable compute instances where customers manage guest OS and application software; in this design the new outcome is to add parallel instance capacity for a distributed application, which calls for Horizontal EC2 scaling rather than Amazon EC2 or the earlier Elasticity through scaling policies.

Elasticity through scaling policies primarily supports the earlier need to match compute capacity to traffic fluctuations automatically because metric-driven policies can change running capacity in response to utilization or demand, but the new task is to add parallel instance capacity for a distributed application; that is why Horizontal EC2 scaling is preferable here.

Amazon EKS addresses the separate need to run Kubernetes-based container workloads using an AWS-managed control plane because eKS integrates managed Kubernetes cluster control plane services with AWS infrastructure; it is not as direct as Amazon CloudWatch EC2 metrics for the actual requirement to monitor resource behavior to inform scaling and alerts.

EC2 instance store addresses the separate need to use temporary host-attached storage with very low latency because instance store volumes are physically associated with the host and have ephemeral characteristics; it is not as direct as Amazon CloudWatch EC2 metrics for the actual requirement to monitor resource behavior to inform scaling and alerts.

Amazon ECR addresses the separate need to store and distribute container images for deployment because eCR is a managed container image registry integrated with AWS deployment tooling; it is not as direct as Amazon CloudWatch EC2 metrics for the actual requirement to monitor resource behavior to inform scaling and alerts.

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.