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 offload eligible read queries from a relational database primary; that is why RDS read replica is preferable here.

RDS Multi-AZ configuration is intended to improve database availability using a standby in another Availability Zone because RDS Multi-AZ options support failover when the primary or supporting infrastructure fails; in this design the new outcome is to offload eligible read queries from a relational database primary, which calls for RDS read replica rather than RDS Multi-AZ configuration or the earlier Amazon RDS.

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 offload eligible read queries from a relational database primary, which calls for RDS read replica rather than Amazon Aurora or the earlier Amazon RDS.

On-premises deployment addresses the separate need to keep computing equipment operated entirely in an organization's facility because an on-premises environment remains hosted and administered at the organization's sites; it is not as direct as AWS SDKs for the actual requirement to integrate AWS service requests directly into application source code.

Hybrid cloud deployment addresses the separate need to retain some local systems while extending selected workloads into AWS because hybrid environments combine on-premises resources with cloud services and connectivity; it is not as direct as AWS SDKs for the actual requirement to integrate AWS service requests directly into application source code.

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 SDKs for the actual requirement to integrate AWS service requests directly into application source code.

AWS Transit Gateway primarily supports the earlier need to connect many VPCs and supported on-premises networks through a central hub because transit Gateway simplifies hub-and-spoke network connectivity at scale, but the new task is to establish dedicated private network connectivity from a site to AWS; that is why AWS Direct Connect is preferable here.

VPC Flow Logs is intended to capture metadata about traffic to and from network interfaces because VPC Flow Logs record accepted or rejected network-flow metadata in supported destinations; in this design the new outcome is to establish dedicated private network connectivity from a site to AWS, which calls for AWS Direct Connect rather than VPC Flow Logs or the earlier AWS Transit Gateway.

Amazon VPC is intended to create a logically isolated IP network for AWS resources because a VPC defines virtual networking boundaries and hosts configurable subnets and routing; in this design the new outcome is to establish dedicated private network connectivity from a site to AWS, which calls for AWS Direct Connect rather than Amazon VPC or the earlier AWS Transit Gateway.

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 address disaster recovery or geography-spanning application availability; that is why Multi-Region architecture is preferable here.

Multi-AZ application deployment is intended to survive a failure confined to one Availability Zone because replicated tiers across separate AZs reduce dependence on a single facility group; in this design the new outcome is to address disaster recovery or geography-spanning application availability, which calls for Multi-Region architecture rather than Multi-AZ application deployment or the earlier Regional service scope.

Data residency by Region is intended to keep stored customer data in a selected geography because region placement and configured replication determine where supported AWS workload data resides; in this design the new outcome is to address disaster recovery or geography-spanning application availability, which calls for Multi-Region architecture rather than Data residency by Region or the earlier Regional service scope.

That description belongs to Amazon Redshift because redshift supports warehouse-oriented queries across large structured datasets; it is used to run analytical workloads in a purpose-built data warehouse, not to explain how Amazon Kinesis provides the function to ingest and process streaming event data near real time.

That description belongs to Amazon Athena because athena runs interactive SQL queries without provisioning a dedicated database server; it is used to query supported data in S3 using serverless SQL, not to explain how Amazon Kinesis provides the function to ingest and process streaming event data near real time.

That description belongs to AWS Lake Formation because lake Formation helps establish and secure data-lake environments using AWS data services; it is used to govern data lakes with access and catalog integration, not to explain how Amazon Kinesis provides the function to ingest and process streaming event data near real time.

Amazon AppStream 2.0 is intended to stream hosted desktop applications to end users because appStream 2.0 streams supported applications through a browser or client; in this design the new outcome is to connect IoT devices securely to cloud applications and messaging, which calls for AWS IoT Core rather than Amazon AppStream 2.0 or the earlier AWS IoT Device Management.

Amazon Cognito is intended to provide sign-up sign-in and identity features for customer-facing applications because cognito supports application user directories and federation; in this design the new outcome is to connect IoT devices securely to cloud applications and messaging, which calls for AWS IoT Core rather than Amazon Cognito or the earlier AWS IoT Device Management.

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 connect IoT devices securely to cloud applications and messaging; that is why AWS IoT Core is preferable here.

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 increase resource capacity by changing the instance type, which calls for Vertical EC2 scaling rather than Elasticity through scaling policies or the earlier Horizontal EC2 scaling.

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 increase resource capacity by changing the instance type, which calls for Vertical EC2 scaling rather than Amazon EC2 or the earlier Horizontal EC2 scaling.

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 increase resource capacity by changing the instance type; that is why Vertical EC2 scaling is preferable here.

That description belongs to CloudFront origin because a CloudFront distribution retrieves objects or responses from a configured origin when needed; it is used to provide the source from which edge caches fetch content on a miss, not to explain how AWS Region provides the function to select a geographic area in which to place a workload.

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 AWS Region provides the function to select a geographic area in which to place a workload.

That description belongs to Regional jurisdiction planning because region choices can help address jurisdictional and contractual requirements for where workloads run; it is used to select deployment geography to align with applicable organizational requirements, not to explain how AWS Region provides the function to select a geographic area in which to place a workload.

Vertical EC2 scaling addresses the separate need to increase resource capacity by changing the instance type because vertical scaling provides more CPU or RAM within a single virtual machine; it is not as direct as Amazon EKS for the actual requirement to run Kubernetes-based container workloads using an AWS-managed control plane.

EC2 Auto Scaling addresses the separate need 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; it is not as direct as Amazon EKS for the actual requirement to run Kubernetes-based container workloads using an AWS-managed control plane.

Amazon CloudWatch EC2 metrics addresses the separate need to monitor resource behavior to inform scaling and alerts because cloudWatch collects supported measurements such as CPU utilization from EC2; it is not as direct as Amazon EKS for the actual requirement to run Kubernetes-based container workloads using an AWS-managed control plane.

RDS Multi-AZ configuration addresses the separate need to improve database availability using a standby in another Availability Zone because RDS Multi-AZ options support failover when the primary or supporting infrastructure fails; it is not as direct as AWS Database Migration Service for the actual requirement to move ongoing database data between supported source and destination engines.

Amazon Redshift addresses the separate need to analyze large structured data sets in a columnar warehouse because redshift provides a cloud data warehouse optimized for analytical SQL workloads; it is not as direct as AWS Database Migration Service for the actual requirement to move ongoing database data between supported source and destination engines.

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 AWS Database Migration Service for the actual requirement to move ongoing database data between supported source and destination engines.

Amazon Neptune addresses the separate need to manage highly connected entities and their relationships as a graph because neptune is a managed graph database for graph traversals and relationships; it is not as direct as AWS Database Migration Service for the actual requirement to move ongoing database data between supported source and destination engines.

That description belongs to Amazon S3 because S3 is an object storage service for files and data blobs rather than mounted block devices; it is used to store durable objects and retrieve them by bucket and key, not to explain how S3 event notification provides the function to trigger configured downstream work when selected bucket events occur.

That description belongs to S3 bucket policy because bucket policies are resource-based JSON permissions for supported S3 actions; it is used to control allowed and denied access to an S3 bucket and its objects, not to explain how S3 event notification provides the function to trigger configured downstream work when selected bucket events occur.

That description belongs to S3 Cross-Region Replication because cross-Region Replication provides configured cross-Region object replication for supported cases; it is used to copy eligible objects asynchronously to a bucket in a different AWS Region, not to explain how S3 event notification provides the function to trigger configured downstream work when selected bucket events occur.