EC2 user data is intended to perform initial bootstrap actions during instance launch because user data can provide launch-time configuration and installation scripts; in this design the new outcome is to launch simple virtual servers with bundled management and predictable plans, which calls for Amazon Lightsail rather than EC2 user data or the earlier AWS Lambda.

Gateway Load Balancer is intended to insert compatible virtual network appliances into traffic paths because gateway Load Balancer distributes flows across appliance targets for inspection or similar tasks; in this design the new outcome is to launch simple virtual servers with bundled management and predictable plans, which calls for Amazon Lightsail rather than Gateway Load Balancer or the earlier AWS Lambda.

AWS Lambda primarily supports the earlier need to execute event-triggered code without managing virtual servers because lambda runs functions in managed execution environments with service-defined execution constraints, but the new task is to launch simple virtual servers with bundled management and predictable plans; that is why Amazon Lightsail is preferable here.

Amazon Aurora is intended to use a cloud-optimized relational engine compatible with MySQL or PostgreSQL because aurora is a managed relational database with distributed storage and supported compatibility modes; in this design the new outcome is to preserve multi-step data consistency in a relational workload, which calls for ACID relational transactions rather than Amazon Aurora or the earlier Amazon RDS.

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 preserve multi-step data consistency in a relational workload, which calls for ACID relational transactions rather than Amazon ElastiCache or the earlier Amazon RDS.

Amazon RDS primarily supports the earlier need to operate a managed relational database engine because RDS automates selected relational database operations including backup and patching, but the new task is to preserve multi-step data consistency in a relational workload; that is why ACID relational transactions is preferable here.

Real-time event analytics addresses the separate need to act on measurements or clicks as they arrive because streaming architectures use ingestion and processing to reduce analysis latency; it is not as direct as Amazon Redshift for the actual requirement to run analytical workloads in a purpose-built data warehouse.

ETL data preparation addresses the separate need to clean transform and load datasets before reporting because eTL services such as AWS Glue transform records into analysis-ready formats; it is not as direct as Amazon Redshift for the actual requirement to run analytical workloads in a purpose-built data warehouse.

Amazon Textract addresses the separate need to extract printed and handwritten text and document structure because textract reads forms tables and text from supported document inputs; it is not as direct as Amazon Redshift for the actual requirement to run analytical workloads in a purpose-built data warehouse.

Amazon EMR addresses the separate need to run supported big-data frameworks such as Apache Spark because eMR provides managed cluster and serverless options for big-data processing; it is not as direct as Amazon Redshift for the actual requirement to run analytical workloads in a purpose-built data warehouse.

Text sentiment classification addresses the separate need to identify positive negative or neutral tone in a document because managed NLP sentiment analysis assesses the emotional polarity of text; it is not as direct as Amazon Redshift for the actual requirement to run analytical workloads in a purpose-built data warehouse.

That description belongs to Multi-Region architecture because deploying and replicating across Regions can isolate regional failures and serve separate markets; it is used to address disaster recovery or geography-spanning application availability, not to explain how Region outage planning provides the function to prepare recovery beyond failure of one Availability Zone.

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 Region outage planning provides the function to prepare recovery beyond failure of one Availability Zone.

That description belongs to Availability Zone because an Availability Zone is one or more discrete data centers with independent infrastructure in a Region; it is used to separate redundant application components across isolated facilities within one Region, not to explain how Region outage planning provides the function to prepare recovery beyond failure of one Availability Zone.

VPC peering is intended to connect two VPCs privately for their routable address ranges because peering allows traffic between eligible VPCs with non-overlapping CIDRs and appropriate routes; in this design the new outcome is to connect many VPCs and supported on-premises networks through a central hub, which calls for AWS Transit Gateway rather than VPC peering or the earlier Gateway VPC endpoint.

Interface VPC endpoint is intended to reach supported services through private network interfaces in a subnet because privateLink-backed endpoints create private IP endpoints with associated security groups; in this design the new outcome is to connect many VPCs and supported on-premises networks through a central hub, which calls for AWS Transit Gateway rather than Interface VPC endpoint or the earlier Gateway VPC endpoint.

Gateway VPC endpoint primarily supports the earlier need to connect a VPC to supported Amazon S3 or DynamoDB services through route-table entries because gateway endpoints provide private service paths for S3 and DynamoDB, but the new task is to connect many VPCs and supported on-premises networks through a central hub; that is why AWS Transit Gateway is preferable here.

Amazon SES is intended to send transactional or bulk application email because sES provides managed email sending and receiving capabilities; in this design the new outcome is to create a managed front door for application APIs, which calls for Amazon API Gateway rather than Amazon SES or the earlier Amazon WorkSpaces.

Amazon WorkSpaces primarily supports the earlier need to provide managed cloud virtual desktop environments because workSpaces delivers desktop computing to remote users, but the new task is to create a managed front door for application APIs; that is why Amazon API Gateway is preferable here.

AWS X-Ray is intended to trace distributed requests through supported application components because x-Ray provides distributed tracing to help find latency and failure sources; in this design the new outcome is to create a managed front door for application APIs, which calls for Amazon API Gateway rather than AWS X-Ray or the earlier Amazon WorkSpaces.

AWS Outposts is intended to run AWS-managed infrastructure at a customer premises for local requirements because outposts extends selected AWS infrastructure and services to supported on-premises locations; in this design the new outcome is to run scripted AWS API operations from shell commands, which calls for AWS CLI rather than AWS Outposts or the earlier Infrastructure as code.

Infrastructure as code primarily supports the earlier need to treat resource configurations as version-controlled declarative definitions because infrastructure as code makes deployments repeatable and reviewable through machine-readable files, but the new task is to run scripted AWS API operations from shell commands; that is why AWS CLI is preferable here.

Public cloud deployment is intended to run workloads on provider infrastructure without maintaining local servers because a public cloud model uses infrastructure operated by an external cloud provider; in this design the new outcome is to run scripted AWS API operations from shell commands, which calls for AWS CLI rather than Public cloud deployment or the earlier Infrastructure as code.

DynamoDB global tables primarily supports the earlier need to provide multi-Region active-active replication for a DynamoDB application because global tables replicate supported data across selected Regions for regional workloads, but the new task is to cache frequently accessed application data in memory; that is why Amazon ElastiCache is preferable here.

Amazon Redshift is intended to analyze large structured data sets in a columnar warehouse because redshift provides a cloud data warehouse optimized for analytical SQL workloads; in this design the new outcome is to cache frequently accessed application data in memory, which calls for Amazon ElastiCache rather than Amazon Redshift or the earlier DynamoDB global tables.

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 DynamoDB global tables.

AWS IoT Device Management primarily supports the earlier need to organize and manage fleets of supported connected devices because ioT device management capabilities help register organize and monitor connected devices, but the new task is to audit supported AWS account activity and API operations; that is why AWS CloudTrail is preferable here.

Amazon EventBridge Scheduler is intended to invoke supported targets according to one-time or recurring schedules because eventBridge Scheduler manages event-driven scheduled invocations; in this design the new outcome is to audit supported AWS account activity and API operations, which calls for AWS CloudTrail rather than Amazon EventBridge Scheduler or the earlier AWS IoT Device Management.

AWS X-Ray is intended to trace distributed requests through supported application components because x-Ray provides distributed tracing to help find latency and failure sources; in this design the new outcome is to audit supported AWS account activity and API operations, which calls for AWS CloudTrail rather than AWS X-Ray or the earlier AWS IoT Device Management.

That description belongs to AWS Service Catalog because service Catalog lets administrators define centrally governed products users can launch; it is used to offer approved infrastructure products through governed self-service, not to explain how AWS service APIs provides the function to interact programmatically with AWS using supported service requests.

That description belongs to AWS SDKs because sDKs provide language libraries and request handling for application integrations with AWS APIs; it is used to integrate AWS service requests directly into application source code, not to explain how AWS service APIs provides the function to interact programmatically with AWS using supported service requests.

That description belongs to AWS Systems Manager because systems Manager provides inventory, automation, patching and remote operational capabilities; it is used to manage operational tasks across supported compute fleets, not to explain how AWS service APIs provides the function to interact programmatically with AWS using supported service requests.

AWS Storage Gateway addresses the separate need to connect on-premises applications to cloud-backed storage interfaces because storage Gateway supports hybrid file volume and tape integration scenarios; it is not as direct as Amazon S3 One Zone-IA for the actual requirement to store recreatable infrequently accessed objects within one Availability Zone.

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 Amazon S3 One Zone-IA for the actual requirement to store recreatable infrequently accessed objects within one Availability Zone.

S3 server-side encryption addresses the separate need to encrypt S3 object data at rest using supported key arrangements because S3 encrypts stored object data at rest and supports key-management choices; it is not as direct as Amazon S3 One Zone-IA for the actual requirement to store recreatable infrequently accessed objects within one Availability Zone.