Amazon Textract is intended to extract printed and handwritten text and document structure because textract reads forms tables and text from supported document inputs; in this design the new outcome is to identify positive negative or neutral tone in a document, which calls for Text sentiment classification rather than Amazon Textract or the earlier Amazon SageMaker AI.

Amazon SageMaker AI primarily supports the earlier need to build train and deploy custom machine learning models because sageMaker AI offers managed tooling for ML data preparation training and inference workflows, but the new task is to identify positive negative or neutral tone in a document; that is why Text sentiment classification is preferable here.

Amazon OpenSearch Service is intended to search and analyze indexed logs and document collections because openSearch Service supports search analytics and log exploration; in this design the new outcome is to identify positive negative or neutral tone in a document, which calls for Text sentiment classification rather than Amazon OpenSearch Service or the earlier Amazon SageMaker AI.

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 hold scratch data temporarily on host-attached disks; centrally manage backup plans across supported AWS resources.

Amazon S3 addresses a different objective, to store durable objects and retrieve them by bucket and key, because S3 is an object storage service for files and data blobs rather than mounted block devices; the checklist instead requires the distinct outcomes to hold scratch data temporarily on host-attached disks; centrally manage backup plans across supported AWS resources.

Amazon EFS addresses a different objective, to mount elastic shared file storage from multiple Linux workloads, because eFS supplies managed NFS file systems that can be accessed concurrently by supported clients; the checklist instead requires the distinct outcomes to hold scratch data temporarily on host-attached disks; centrally manage backup plans across supported AWS resources.

Heterogeneous database migration primarily supports the earlier need to move between dissimilar database engines with possible schema translation because heterogeneous migration may require converting schema objects and application SQL, but the new task is to translate supported database schemas and code for heterogeneous migrations; that is why AWS Schema Conversion Tool 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 translate supported database schemas and code for heterogeneous migrations, which calls for AWS Schema Conversion Tool rather than RDS Multi-AZ configuration or the earlier Heterogeneous database migration.

Amazon RDS is intended to operate a managed relational database engine because RDS automates selected relational database operations including backup and patching; in this design the new outcome is to translate supported database schemas and code for heterogeneous migrations, which calls for AWS Schema Conversion Tool rather than Amazon RDS or the earlier Heterogeneous database migration.

That description belongs to AWS Region because an AWS Region is a distinct geographic location containing multiple Availability Zones; it is used to select a geographic area in which to place a workload, not to explain how Regional disaster recovery tests provides the function to verify a workload can resume in its backup Region.

That description belongs to Regional service availability check because AWS service availability varies by Region and sometimes by instance family or feature; it is used to verify a particular offering is available in the chosen Region, not to explain how Regional disaster recovery tests provides the function to verify a workload can resume in its backup Region.

That description belongs to Regional service scope because regional services require selecting the location where supported resources are created; it is used to recognize that many AWS resources exist only in a selected Region, not to explain how Regional disaster recovery tests provides the function to verify a workload can resume in its backup Region.

Route table addresses the separate need to decide where traffic from a subnet should be directed because VPC route tables contain destination-prefix routing entries for network traffic; it is not as direct as NAT versus internet gateway for the actual requirement to distinguish outbound address translation from direct public routing.

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 NAT versus internet gateway for the actual requirement to distinguish outbound address translation from direct public routing.

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 NAT versus internet gateway for the actual requirement to distinguish outbound address translation from direct public routing.

S3 Same-Region Replication addresses the separate need to replicate eligible objects between buckets within the same AWS Region because same-Region Replication can support same-region copy and ownership workflows; it is not as direct as AWS DataSync for the actual requirement to accelerate and automate transfers between supported storage locations.

Amazon EFS addresses the separate need to mount elastic shared file storage from multiple Linux workloads because eFS supplies managed NFS file systems that can be accessed concurrently by supported clients; it is not as direct as AWS DataSync for the actual requirement to accelerate and automate transfers between supported storage locations.

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 AWS DataSync for the actual requirement to accelerate and automate transfers between supported storage locations.

S3 server-side encryption addresses the separate need to encrypt S3 object data at rest using supported key arrangements because S3 encrypts stored object data at rest and supports key-management choices; it is not as direct as AWS DataSync for the actual requirement to accelerate and automate transfers between supported storage locations.

EBS snapshot addresses the separate need 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; it is not as direct as AWS DataSync for the actual requirement to accelerate and automate transfers between supported storage locations.

That description belongs to Spot interruption handling because Spot capacity may be interrupted by AWS, so tasks should checkpoint or retry; it is used to design flexible EC2 workloads to withstand capacity reclamation, not to explain how Accelerated computing EC2 instance provides the function to handle workloads requiring GPUs or specialized hardware acceleration.

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 Accelerated computing EC2 instance provides the function to handle workloads requiring GPUs or specialized hardware acceleration.

That description belongs to General purpose EC2 instance because general-purpose instances provide a balanced resource profile without specializing in one bottleneck; it is used to balance CPU memory and networking for broadly mixed workloads, not to explain how Accelerated computing EC2 instance provides the function to handle workloads requiring GPUs or specialized hardware acceleration.

NAT versus internet gateway addresses the separate need to distinguish outbound address translation from direct public routing because NAT gateways enable private egress; internet gateways provide the VPC's internet attachment; it is not as direct as Security group for the actual requirement to enforce stateful inbound and outbound rules on supported 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 Security group for the actual requirement to enforce stateful inbound and outbound rules on supported resources.

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 Security group for the actual requirement to enforce stateful inbound and outbound rules on supported resources.

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 CloudWatch EC2 metrics.

Amazon CloudWatch EC2 metrics primarily supports the earlier need to monitor resource behavior to inform scaling and alerts because cloudWatch collects supported measurements such as CPU utilization from EC2, 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 CloudWatch EC2 metrics.

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 Amazon S3 Standard.

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 Amazon S3 Standard.

Amazon S3 Standard primarily supports the earlier need to serve frequently accessed objects with low-latency retrieval because S3 Standard is appropriate for data requiring regular access across multiple AZs, 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 ElastiCache addresses a different objective, to cache frequently accessed application data in memory, because elastiCache offers managed in-memory caching engines to reduce repetitive backend reads; the checklist instead requires the distinct outcomes to retain direct control of database host OS and engine installation; reduce avoidable connection pressure on an RDS application backend.

Amazon DocumentDB addresses a different objective, to run JSON document workloads using MongoDB-compatible APIs, because documentDB offers managed document database capabilities for suitable MongoDB workloads; the checklist instead requires the distinct outcomes to retain direct control of database host OS and engine installation; reduce avoidable connection pressure on an RDS application backend.

Amazon RDS addresses a different objective, to operate a managed relational database engine, because RDS automates selected relational database operations including backup and patching; the checklist instead requires the distinct outcomes to retain direct control of database host OS and engine installation; reduce avoidable connection pressure on an RDS application backend.