That description belongs to EBS volume encryption because encrypted EBS volumes use integrated key management for data at rest; it is used to protect block storage with supported at-rest encryption, not to explain how AWS Storage Gateway provides the function to connect on-premises applications to cloud-backed storage interfaces.

That description belongs to AWS DataSync because dataSync moves files or objects between on-premises and AWS storage systems with verification; it is used to accelerate and automate transfers between supported storage locations, not to explain how AWS Storage Gateway provides the function to connect on-premises applications to cloud-backed storage interfaces.

That description belongs to EBS snapshot because EBS snapshots capture volume data and can support recovery or creating new volumes; it is used to back up an EBS volume to durable AWS-managed snapshot storage, not to explain how AWS Storage Gateway provides the function to connect on-premises applications to cloud-backed storage interfaces.

Network ACL addresses the separate need to apply stateless allow and deny rules at the subnet boundary because network ACLs evaluate subnet traffic using ordered rules in each direction; it is not as direct as Amazon VPC for the actual requirement to create a logically isolated IP network for AWS resources.

AWS Site-to-Site VPN addresses the separate need to connect office networks to AWS through encrypted tunnels over IP networks because site-to-Site VPN establishes IPsec tunnels between a customer network and AWS connectivity endpoints; it is not as direct as Amazon VPC for the actual requirement to create a logically isolated IP network for AWS resources.

NAT gateway addresses the separate need to let private subnet resources initiate eligible outbound internet connections because a NAT gateway translates egress traffic when appropriate routes are configured; it is not as direct as Amazon VPC for the actual requirement to create a logically isolated IP network for AWS resources.

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 EC2 user data for the actual requirement to perform initial bootstrap actions during instance launch.

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 EC2 user data for the actual requirement to perform initial bootstrap actions during instance launch.

General purpose EC2 instance addresses the separate need to balance CPU memory and networking for broadly mixed workloads because general-purpose instances provide a balanced resource profile without specializing in one bottleneck; it is not as direct as EC2 user data for the actual requirement to perform initial bootstrap actions during instance launch.

AWS Organizations addresses the separate need to centrally manage accounts rather than configuring each account independently because organizations groups accounts for governance and consolidated billing; it is not as direct as Manual console provisioning for the actual requirement to perform a one-off configuration with interactive review.

AWS Control Tower addresses the separate need to establish and govern a multi-account landing zone because control Tower provides guardrails and account governance for supported AWS Organizations environments; it is not as direct as Manual console provisioning for the actual requirement to perform a one-off configuration with interactive review.

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

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

Content delivery latency is intended to reduce time to download reusable web assets in different countries because cDN caching stores content nearer viewers and lowers repeat retrieval distance; in this design the new outcome is to cache web content at distributed edge locations near viewers, which calls for Amazon CloudFront rather than Content delivery latency or the earlier CloudFront origin.

Edge location is intended to deliver cached content closer to geographically dispersed end users because edge sites support services such as CloudFront close to viewers to reduce delivery latency; in this design the new outcome is to cache web content at distributed edge locations near viewers, which calls for Amazon CloudFront rather than Edge location 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 cache web content at distributed edge locations near viewers; that is why Amazon CloudFront is preferable here.

AWS Global Accelerator addresses the separate need 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; it is not as direct as Route 53 weighted routing for the actual requirement to distribute DNS responses among configured endpoints according to weights.

Public subnet addresses the separate need to place resources in a subnet with a route toward an internet gateway because a public subnet has a route to an attached internet gateway where applicable; it is not as direct as Route 53 weighted routing for the actual requirement to distribute DNS responses among configured endpoints according to weights.

VPC subnet CIDR planning addresses the separate need to allocate non-overlapping address ranges for interconnected environments because vPCs and subnets use address ranges that affect future peering and routing options; it is not as direct as Route 53 weighted routing for the actual requirement to distribute DNS responses among configured endpoints according to weights.

Amazon DynamoDB addresses the separate need to store key-value or document data with managed NoSQL scaling because DynamoDB is a fully managed NoSQL database with service-managed infrastructure; it is not as direct as Heterogeneous database migration for the actual requirement to move between dissimilar database engines with possible schema translation.

RDS automated backups addresses the separate need to enable managed point-in-time recovery for an eligible RDS database because RDS backups and transaction logs support recovery within a configured retention period; it is not as direct as Heterogeneous database migration for the actual requirement to move between dissimilar database engines with possible schema translation.

AWS Migration Hub addresses the separate need to track multiple migration activities in one view because migration Hub centralizes migration progress information from supported tools; it is not as direct as Heterogeneous database migration for the actual requirement to move between dissimilar database engines with possible schema translation.

Network Load Balancer primarily supports the earlier need to handle high-performance connection-level TCP or UDP traffic because nLB routes connections at the transport layer and supports static IP behavior, but the new task is to queue and execute batch computing jobs with managed scheduling; that is why AWS Batch is preferable here.

AWS Lambda is intended to execute event-triggered code without managing virtual servers because lambda runs functions in managed execution environments with service-defined execution constraints; in this design the new outcome is to queue and execute batch computing jobs with managed scheduling, which calls for AWS Batch rather than AWS Lambda or the earlier Network Load Balancer.

Amazon ECS is intended to orchestrate containerized applications using AWS-managed control capabilities because eCS schedules and manages containers in clusters on supported launch types; in this design the new outcome is to queue and execute batch computing jobs with managed scheduling, which calls for AWS Batch rather than Amazon ECS or the earlier Network Load Balancer.

Amazon SES primarily supports the earlier need to send transactional or bulk application email because sES provides managed email sending and receiving capabilities, but the new task is to stream hosted desktop applications to end users; that is why Amazon AppStream 2.0 is preferable here.

Amazon WorkSpaces is intended to provide managed cloud virtual desktop environments because workSpaces delivers desktop computing to remote users; in this design the new outcome is to stream hosted desktop applications to end users, which calls for Amazon AppStream 2.0 rather than Amazon WorkSpaces or the earlier Amazon SES.

AWS IoT Core is intended to connect IoT devices securely to cloud applications and messaging because ioT Core provides managed device communication and integration; in this design the new outcome is to stream hosted desktop applications to end users, which calls for Amazon AppStream 2.0 rather than AWS IoT Core or the earlier Amazon SES.

S3 Cross-Region Replication addresses the separate need to copy eligible objects asynchronously to a bucket in a different AWS Region because cross-Region Replication provides configured cross-Region object replication for supported cases; it is not as direct as Amazon S3 Standard-IA for the actual requirement to store infrequently accessed objects that still need rapid retrieval.

Amazon S3 Standard addresses the separate need to serve frequently accessed objects with low-latency retrieval because S3 Standard is appropriate for data requiring regular access across multiple AZs; it is not as direct as Amazon S3 Standard-IA for the actual requirement to store infrequently accessed objects that still need rapid retrieval.

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 Amazon S3 Standard-IA for the actual requirement to store infrequently accessed objects that still need rapid retrieval.

Amazon Comprehend is intended to extract sentiment entities and other insights from text because comprehend provides managed natural-language processing APIs; in this design the new outcome is to create dashboards and business intelligence visualizations, which calls for Amazon Quick rather than Amazon Comprehend or the earlier Amazon Q.

Amazon SageMaker AI is intended to build train and deploy custom machine learning models because sageMaker AI offers managed tooling for ML data preparation training and inference workflows; in this design the new outcome is to create dashboards and business intelligence visualizations, which calls for Amazon Quick rather than Amazon SageMaker AI or the earlier Amazon Q.

Amazon Q primarily supports the earlier need to offer generative AI assistance for supported business and developer workflows because Amazon Q provides AI-powered assistant capabilities in integrated AWS settings, but the new task is to create dashboards and business intelligence visualizations; that is why Amazon Quick is preferable here.