Amazon EC2 AMI primarily supports the earlier need to relaunch instances from a defined system image because an Amazon Machine Image supplies a template for instance boot volumes and configuration, but the new task is to obtain eligible EC2 billing discounts for committed usage attributes; that is why Reserved Instances is preferable here.

EC2 Auto Scaling is intended 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; in this design the new outcome is to obtain eligible EC2 billing discounts for committed usage attributes, which calls for Reserved Instances rather than EC2 Auto Scaling or the earlier Amazon EC2 AMI.

AWS Fargate is intended to run container tasks without managing EC2 container hosts because fargate supplies serverless compute for supported ECS and EKS workloads; in this design the new outcome is to obtain eligible EC2 billing discounts for committed usage attributes, which calls for Reserved Instances rather than AWS Fargate or the earlier Amazon EC2 AMI.

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 geolocation routing for the actual requirement to select DNS answers based on the geographic origin of DNS queries.

AWS Direct Connect addresses the separate need to establish dedicated private network connectivity from a site to AWS because direct Connect provides a dedicated network connection through supported locations; it is not as direct as Route 53 geolocation routing for the actual requirement to select DNS answers based on the geographic origin of DNS queries.

VPC endpoint addresses the separate need to connect supported VPC workloads privately to selected AWS services because VPC endpoints provide service connectivity without requiring a public internet path; it is not as direct as Route 53 geolocation routing for the actual requirement to select DNS answers based on the geographic origin of DNS queries.

Amazon VPC addresses the separate need to create a logically isolated IP network for AWS resources because a VPC defines virtual networking boundaries and hosts configurable subnets and routing; it is not as direct as Route 53 geolocation routing for the actual requirement to select DNS answers based on the geographic origin of DNS queries.

That description belongs to Amazon EBS because EBS volumes provide durable block storage within an Availability Zone with supported snapshot options; it is used to attach persistent block-level storage to supported EC2 instances, not to explain how EBS volume encryption provides the function to protect block storage with supported at-rest encryption.

That description belongs to S3 server-side encryption because S3 encrypts stored object data at rest and supports key-management choices; it is used to encrypt S3 object data at rest using supported key arrangements, not to explain how EBS volume encryption provides the function to protect block storage with supported at-rest encryption.

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 EBS volume encryption provides the function to protect block storage with supported at-rest encryption.

Vertical EC2 scaling primarily supports the earlier need to increase resource capacity by changing the instance type because vertical scaling provides more CPU or RAM within a single virtual machine, but the new task is to match compute capacity to traffic fluctuations automatically; that is why Elasticity through scaling policies is preferable here.

Elastic Load Balancing is intended to spread inbound traffic across multiple eligible targets because eLB directs client traffic toward configured healthy application targets; in this design the new outcome is to match compute capacity to traffic fluctuations automatically, which calls for Elasticity through scaling policies rather than Elastic Load Balancing or the earlier Vertical EC2 scaling.

Horizontal EC2 scaling is intended to add parallel instance capacity for a distributed application because horizontal scaling adds multiple instances that can share workload when architecture supports it; in this design the new outcome is to match compute capacity to traffic fluctuations automatically, which calls for Elasticity through scaling policies rather than Horizontal EC2 scaling or the earlier Vertical EC2 scaling.

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 allocate non-overlapping address ranges for interconnected environments, which calls for VPC subnet CIDR planning rather than VPC peering or the earlier NAT versus internet gateway.

NAT versus internet gateway primarily supports the earlier need to distinguish outbound address translation from direct public routing because NAT gateways enable private egress; internet gateways provide the VPC's internet attachment, but the new task is to allocate non-overlapping address ranges for interconnected environments; that is why VPC subnet CIDR planning is preferable here.

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 allocate non-overlapping address ranges for interconnected environments, which calls for VPC subnet CIDR planning rather than Amazon VPC or the earlier NAT versus internet gateway.

Amazon Route 53 primarily supports the earlier need to resolve application domain names and apply supported DNS routing policies because Route 53 is a managed DNS and domain service with traffic-routing and health-check features, but the new task is to resolve private domain names inside associated VPC networks; that is why Private hosted zone is preferable here.

Internet gateway is intended to enable internet routing for resources in a VPC with suitable configuration because an internet gateway connects a VPC to the internet for eligible public addressing paths; in this design the new outcome is to resolve private domain names inside associated VPC networks, which calls for Private hosted zone rather than Internet gateway or the earlier Amazon Route 53.

AWS Direct Connect is intended to establish dedicated private network connectivity from a site to AWS because direct Connect provides a dedicated network connection through supported locations; in this design the new outcome is to resolve private domain names inside associated VPC networks, which calls for Private hosted zone rather than AWS Direct Connect or the earlier Amazon Route 53.

AWS Storage Gateway primarily supports the earlier need to connect on-premises applications to cloud-backed storage interfaces because storage Gateway supports hybrid file volume and tape integration scenarios, but the new task is to provide managed SMB file shares for Windows workloads; that is why Amazon FSx for Windows File Server is preferable here.

AWS Elastic Disaster Recovery is intended to restore servers and workloads in AWS after an infrastructure disaster because elastic Disaster Recovery uses continuous block replication and orchestrated recovery; in this design the new outcome is to provide managed SMB file shares for Windows workloads, which calls for Amazon FSx for Windows File Server rather than AWS Elastic Disaster Recovery or the earlier AWS Storage Gateway.

EBS snapshot is intended to back up an EBS volume to durable AWS-managed snapshot storage because EBS snapshots capture volume data and can support recovery or creating new volumes; in this design the new outcome is to provide managed SMB file shares for Windows workloads, which calls for Amazon FSx for Windows File Server rather than EBS snapshot or the earlier AWS Storage Gateway.

That description belongs to AWS Lambda because lambda runs functions in managed execution environments with service-defined execution constraints; it is used to execute event-triggered code without managing virtual servers, not to explain how AWS App Runner provides the function to deploy supported web applications or container services without operating servers.

That description belongs to AWS Elastic Beanstalk because elastic Beanstalk simplifies web-app deployment and orchestrates the supporting AWS components; it is used to deploy supported applications while the platform provisions common resources, not to explain how AWS App Runner provides the function to deploy supported web applications or container services without operating servers.

That description belongs to AWS Fargate because fargate supplies serverless compute for supported ECS and EKS workloads; it is used to run container tasks without managing EC2 container hosts, not to explain how AWS App Runner provides the function to deploy supported web applications or container services without operating servers.

Internet gateway primarily supports the earlier need to enable internet routing for resources in a VPC with suitable configuration because an internet gateway connects a VPC to the internet for eligible public addressing paths, but the new task is to place backend resources without a direct internet gateway route; that is why Private subnet is preferable here.

Security group is intended to enforce stateful inbound and outbound rules on supported resources because security groups act as virtual firewalls associated with network interfaces; in this design the new outcome is to place backend resources without a direct internet gateway route, which calls for Private subnet rather than Security group or the earlier Internet 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 place backend resources without a direct internet gateway route, which calls for Private subnet rather than Amazon VPC or the earlier Internet gateway.

EBS versus EFS storage model primarily supports the earlier need to recognize block devices compared with managed network file systems because EBS offers block storage attached to instances; EFS offers a shared file system mounted over NFS, but the new task is to mount elastic shared file storage from multiple Linux workloads; that is why Amazon EFS is preferable here.

EBS volume encryption is intended to protect block storage with supported at-rest encryption because encrypted EBS volumes use integrated key management for data at rest; in this design the new outcome is to mount elastic shared file storage from multiple Linux workloads, which calls for Amazon EFS rather than EBS volume encryption or the earlier EBS versus EFS storage model.

AWS Storage Gateway is intended to connect on-premises applications to cloud-backed storage interfaces because storage Gateway supports hybrid file volume and tape integration scenarios; in this design the new outcome is to mount elastic shared file storage from multiple Linux workloads, which calls for Amazon EFS rather than AWS Storage Gateway or the earlier EBS versus EFS storage model.

Accelerated computing EC2 instance addresses the separate need to handle workloads requiring GPUs or specialized hardware acceleration because accelerated instance families provide processors suited to parallel graphics or ML workloads; it is not as direct as Amazon EC2 AMI for the actual requirement to relaunch instances from a defined system image.

Amazon Lightsail addresses the separate need to launch simple virtual servers with bundled management and predictable plans because lightsail packages compute networking and storage for straightforward applications; it is not as direct as Amazon EC2 AMI for the actual requirement to relaunch instances from a defined system image.

EC2 dedicated host addresses the separate need to place eligible instances on physical servers dedicated to one customer because dedicated Hosts provide visibility or control over host placement for some licensing requirements; it is not as direct as Amazon EC2 AMI for the actual requirement to relaunch instances from a defined system image.