Amazon ECR addresses the separate need to store and distribute container images for deployment because eCR is a managed container image registry integrated with AWS deployment tooling; it is not as direct as Spot interruption handling for the actual requirement to design flexible EC2 workloads to withstand capacity reclamation.

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 Spot interruption handling for the actual requirement to design flexible EC2 workloads to withstand capacity reclamation.

Memory optimized EC2 instance addresses the separate need to support applications with large in-memory working sets because memory-optimized families provide higher RAM-to-vCPU ratios for memory-bound applications; it is not as direct as Spot interruption handling for the actual requirement to design flexible EC2 workloads to withstand capacity reclamation.

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 Spot interruption handling for the actual requirement to design flexible EC2 workloads to withstand capacity reclamation.

Amazon S3 One Zone-IA addresses a different objective, to store recreatable infrequently accessed objects within one Availability Zone, because one Zone-IA has a single-AZ resilience profile and lower storage cost; the checklist instead requires the distinct outcomes to optimize storage charges when object access patterns are unpredictable; serve frequently accessed objects with low-latency retrieval; upload very large objects as separately transmitted parts.

Amazon FSx for Windows File Server addresses a different objective, to provide managed SMB file shares for Windows workloads, because fSx for Windows File Server supports Windows file protocols and Active Directory integration; the checklist instead requires the distinct outcomes to optimize storage charges when object access patterns are unpredictable; serve frequently accessed objects with low-latency retrieval; upload very large objects as separately transmitted parts.

S3 Glacier Instant Retrieval addresses a different objective, to keep rarely accessed archives with millisecond access when requested, because glacier Instant Retrieval combines archival pricing characteristics with immediate retrieval; the checklist instead requires the distinct outcomes to optimize storage charges when object access patterns are unpredictable; serve frequently accessed objects with low-latency retrieval; upload very large objects as separately transmitted parts.

That description belongs to Horizontal EC2 scaling because horizontal scaling adds multiple instances that can share workload when architecture supports it; it is used to add parallel instance capacity for a distributed application, not to explain how Vertical EC2 scaling provides the function to increase resource capacity by changing the instance type.

That description belongs to Elasticity through scaling policies because metric-driven policies can change running capacity in response to utilization or demand; it is used to match compute capacity to traffic fluctuations automatically, not to explain how Vertical EC2 scaling provides the function to increase resource capacity by changing the instance type.

That description belongs to Amazon EC2 because EC2 provides configurable compute instances where customers manage guest OS and application software; it is used to operate virtual servers with explicit OS and instance management, not to explain how Vertical EC2 scaling provides the function to increase resource capacity by changing the instance type.

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 serve frequently accessed objects with low-latency retrieval, which calls for Amazon S3 Standard rather than Amazon S3 Inventory or the earlier Amazon S3 Standard-IA.

Amazon S3 Standard-IA primarily supports the earlier need to store infrequently accessed objects that still need rapid retrieval because standard-IA offers lower storage cost for lower access frequency with retrieval charges, but the new task is to serve frequently accessed objects with low-latency retrieval; that is why Amazon S3 Standard is preferable here.

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 serve frequently accessed objects with low-latency retrieval, which calls for Amazon S3 Standard rather than S3 bucket policy or the earlier Amazon S3 Standard-IA.

That description belongs to Amazon FSx for Windows File Server because fSx for Windows File Server supports Windows file protocols and Active Directory integration; it is used to provide managed SMB file shares for Windows workloads, not to explain how AWS Elastic Disaster Recovery provides the function to restore servers and workloads in AWS after an infrastructure disaster.

That description belongs to Amazon EFS because eFS supplies managed NFS file systems that can be accessed concurrently by supported clients; it is used to mount elastic shared file storage from multiple Linux workloads, not to explain how AWS Elastic Disaster Recovery provides the function to restore servers and workloads in AWS after an infrastructure disaster.

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 AWS Elastic Disaster Recovery provides the function to restore servers and workloads in AWS after an infrastructure disaster.

AWS Fargate addresses a different objective, to run container tasks without managing EC2 container hosts, because fargate supplies serverless compute for supported ECS and EKS workloads; the checklist instead requires the distinct outcomes to queue and execute batch computing jobs with managed scheduling; adjust the number of matching EC2 instances as demand changes.

Reserved Instances addresses a different objective, to obtain eligible EC2 billing discounts for committed usage attributes, because reserved Instances are a pricing mechanism for eligible instance usage commitments; the checklist instead requires the distinct outcomes to queue and execute batch computing jobs with managed scheduling; adjust the number of matching EC2 instances as demand changes.

Amazon Lightsail addresses a different objective, to launch simple virtual servers with bundled management and predictable plans, because lightsail packages compute networking and storage for straightforward applications; the checklist instead requires the distinct outcomes to queue and execute batch computing jobs with managed scheduling; adjust the number of matching EC2 instances as demand changes.

That description belongs to AWS App Runner because app Runner automates build or container deployment and scales supported web services; it is used to deploy supported web applications or container services without operating servers, not to explain how Amazon ECR provides the function to store and distribute container images for deployment.

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 Amazon ECR provides the function to store and distribute container images for deployment.

That description belongs to Amazon EKS because eKS integrates managed Kubernetes cluster control plane services with AWS infrastructure; it is used to run Kubernetes-based container workloads using an AWS-managed control plane, not to explain how Amazon ECR provides the function to store and distribute container images for deployment.

Amazon S3 Intelligent-Tiering addresses the separate need to optimize storage charges when object access patterns are unpredictable because intelligent-Tiering can move eligible objects between access tiers based on use; it is not as direct as S3 Versioning for the actual requirement to retain multiple object versions to aid recovery from deletion or overwrite.

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 S3 Versioning for the actual requirement to retain multiple object versions to aid recovery from deletion or overwrite.

Amazon EBS addresses the separate need 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; it is not as direct as S3 Versioning for the actual requirement to retain multiple object versions to aid recovery from deletion or overwrite.

S3 Glacier Instant Retrieval addresses the separate need to keep rarely accessed archives with millisecond access when requested because glacier Instant Retrieval combines archival pricing characteristics with immediate retrieval; it is not as direct as S3 Versioning for the actual requirement to retain multiple object versions to aid recovery from deletion or overwrite.

Horizontal EC2 scaling addresses the separate need to add parallel instance capacity for a distributed application because horizontal scaling adds multiple instances that can share workload when architecture supports it; it is not as direct as AWS Fargate for the actual requirement to run container tasks without managing EC2 container hosts.

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 AWS Fargate for the actual requirement to run container tasks without managing EC2 container hosts.

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 AWS Fargate for the actual requirement to run container tasks without managing EC2 container hosts.

EC2 Auto Scaling primarily supports the earlier 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, but the new task is to influence how supported instances are distributed across underlying hardware; that is why EC2 placement groups is preferable here.

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 influence how supported instances are distributed across underlying hardware, which calls for EC2 placement groups rather than Horizontal EC2 scaling or the earlier EC2 Auto Scaling.

Amazon EC2 AMI is intended to relaunch instances from a defined system image because an Amazon Machine Image supplies a template for instance boot volumes and configuration; in this design the new outcome is to influence how supported instances are distributed across underlying hardware, which calls for EC2 placement groups rather than Amazon EC2 AMI or the earlier EC2 Auto Scaling.

Accelerated computing EC2 instance is intended to handle workloads requiring GPUs or specialized hardware acceleration because accelerated instance families provide processors suited to parallel graphics or ML workloads; in this design the new outcome is to run Kubernetes-based container workloads using an AWS-managed control plane, which calls for Amazon EKS rather than Accelerated computing EC2 instance or the earlier AWS Fargate.

AWS Fargate primarily supports the earlier need to run container tasks without managing EC2 container hosts because fargate supplies serverless compute for supported ECS and EKS workloads, but the new task is to run Kubernetes-based container workloads using an AWS-managed control plane; that is why Amazon EKS is preferable here.

Amazon ECR is intended to store and distribute container images for deployment because eCR is a managed container image registry integrated with AWS deployment tooling; in this design the new outcome is to run Kubernetes-based container workloads using an AWS-managed control plane, which calls for Amazon EKS rather than Amazon ECR or the earlier AWS Fargate.