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 VPC peering provides the function to connect two VPCs privately for their routable address ranges.

That description belongs to VPC endpoint because VPC endpoints provide service connectivity without requiring a public internet path; it is used to connect supported VPC workloads privately to selected AWS services, not to explain how VPC peering provides the function to connect two VPCs privately for their routable address ranges.

That description belongs to VPC subnet CIDR planning because vPCs and subnets use address ranges that affect future peering and routing options; it is used to allocate non-overlapping address ranges for interconnected environments, not to explain how VPC peering provides the function to connect two VPCs privately for their routable address ranges.

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 Data residency by Region provides the function to keep stored customer data in a selected geography.

That description belongs to Cross-Region replication because cross-Region replication moves eligible objects or database data into a different geography when configured; it is used to maintain copies of selected data outside its source Region, not to explain how Data residency by Region provides the function to keep stored customer data in a selected geography.

That description belongs to Low-latency regional placement because deploying compute and data in an appropriate Region can reduce geographic round-trip latency; it is used to locate dynamic application backends nearer a customer population, not to explain how Data residency by Region provides the function to keep stored customer data in a selected geography.

EBS volume encryption addresses a different objective, to protect block storage with supported at-rest encryption, because encrypted EBS volumes use integrated key management for data at rest; the checklist instead requires the distinct outcomes to encrypt S3 object data at rest using supported key arrangements; speed long-distance S3 uploads using AWS edge networking.

Amazon EBS addresses a different objective, to attach persistent block-level storage to supported EC2 instances, because EBS volumes provide durable block storage within an Availability Zone with supported snapshot options; the checklist instead requires the distinct outcomes to encrypt S3 object data at rest using supported key arrangements; speed long-distance S3 uploads using AWS edge networking.

S3 bucket policy addresses a different objective, 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; the checklist instead requires the distinct outcomes to encrypt S3 object data at rest using supported key arrangements; speed long-distance S3 uploads using AWS edge networking.

AWS Region is intended to select a geographic area in which to place a workload because an AWS Region is a distinct geographic location containing multiple Availability Zones; in this design the new outcome is to manage IAM identities used to authorize actions across AWS Regions, which calls for Global IAM identity scope rather than AWS Region or the earlier Region outage planning.

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 manage IAM identities used to authorize actions across AWS Regions; that is why Global IAM identity scope is preferable here.

Availability Zone is intended to separate redundant application components across isolated facilities within one Region because an Availability Zone is one or more discrete data centers with independent infrastructure in a Region; in this design the new outcome is to manage IAM identities used to authorize actions across AWS Regions, which calls for Global IAM identity scope rather than Availability Zone or the earlier Region outage planning.

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 Network Load Balancer for the actual requirement to handle high-performance connection-level TCP or UDP traffic.

EC2 user data addresses the separate need to perform initial bootstrap actions during instance launch because user data can provide launch-time configuration and installation scripts; it is not as direct as Network Load Balancer for the actual requirement to handle high-performance connection-level TCP or UDP traffic.

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 Network Load Balancer for the actual requirement to handle high-performance connection-level TCP or UDP traffic.

Elasticity through scaling policies addresses the separate need to match compute capacity to traffic fluctuations automatically because metric-driven policies can change running capacity in response to utilization or demand; it is not as direct as Network Load Balancer for the actual requirement to handle high-performance connection-level TCP or UDP traffic.

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 table for the actual requirement to decide where traffic from a subnet should be directed.

Stateless versus stateful filtering addresses the separate need to select whether connection return traffic needs independent explicit rules because security groups track allowed connections while network ACLs evaluate both directions without state; it is not as direct as Route table for the actual requirement to decide where traffic from a subnet should be directed.

Amazon CloudFront addresses the separate need to accelerate delivery of static and dynamic web content with CDN edge sites because cloudFront caches eligible objects and routes viewers through distributed edge locations; it is not as direct as Route table for the actual requirement to decide where traffic from a subnet should be directed.

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 multi-part upload provides the function to upload very large objects as separately transmitted parts.

That description belongs to Amazon S3 Inventory because S3 Inventory produces scheduled reports about bucket objects and properties; it is used to generate lists of objects and associated metadata for analysis, not to explain how S3 multi-part upload provides the function to upload very large objects as separately transmitted parts.

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 multi-part upload provides the function to upload very large objects as separately transmitted parts.

EC2 placement groups addresses the separate need to influence how supported instances are distributed across underlying hardware because placement groups support strategies for network performance or fault isolation; it is not as direct as Amazon Lightsail for the actual requirement to launch simple virtual servers with bundled management and predictable plans.

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 Lightsail for the actual requirement to launch simple virtual servers with bundled management and predictable plans.

Gateway Load Balancer addresses the separate need to insert compatible virtual network appliances into traffic paths because gateway Load Balancer distributes flows across appliance targets for inspection or similar tasks; it is not as direct as Amazon Lightsail for the actual requirement to launch simple virtual servers with bundled management and predictable plans.

AWS Global Accelerator primarily supports the earlier 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, but the new task is to apply stateless allow and deny rules at the subnet boundary; that is why Network ACL is preferable here.

Route table is intended to decide where traffic from a subnet should be directed because VPC route tables contain destination-prefix routing entries for network traffic; in this design the new outcome is to apply stateless allow and deny rules at the subnet boundary, which calls for Network ACL rather than Route table or the earlier AWS Global Accelerator.

Public subnet is intended 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; in this design the new outcome is to apply stateless allow and deny rules at the subnet boundary, which calls for Network ACL rather than Public subnet or the earlier AWS Global Accelerator.

S3 Block Public Access primarily supports the earlier need to help prevent unintended public access to buckets and objects because block Public Access settings override or restrict public access paths where enabled, but the new task is to transition or expire objects automatically based on age and criteria; that is why S3 lifecycle rule 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 transition or expire objects automatically based on age and criteria, which calls for S3 lifecycle rule rather than Amazon S3 Inventory or the earlier S3 Block Public Access.

S3 bucket policy is intended 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; in this design the new outcome is to transition or expire objects automatically based on age and criteria, which calls for S3 lifecycle rule rather than S3 bucket policy or the earlier S3 Block Public Access.

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.