VPC endpoint primarily supports the earlier need to connect supported VPC workloads privately to selected AWS services because VPC endpoints provide service connectivity without requiring a public internet path, but the new task is to resolve application domain names and apply supported DNS routing policies; that is why Amazon Route 53 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 resolve application domain names and apply supported DNS routing policies, which calls for Amazon Route 53 rather than Security group or the earlier VPC endpoint.

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 application domain names and apply supported DNS routing policies, which calls for Amazon Route 53 rather than Internet gateway or the earlier VPC endpoint.

Amazon SQS is intended to decouple systems with durable asynchronous message queues because sQS holds messages for consumers to process independently; in this design the new outcome is to run continuous-integration builds and automated tests, which calls for AWS CodeBuild rather than Amazon SQS or the earlier Amazon Connect.

Amazon Connect primarily supports the earlier need to run a cloud-based customer contact center because connect supplies hosted omnichannel contact-center capabilities, but the new task is to run continuous-integration builds and automated tests; that is why AWS CodeBuild is preferable here.

AWS CodePipeline is intended to coordinate continuous delivery stages between tools because codePipeline orchestrates source build test and deployment actions; in this design the new outcome is to run continuous-integration builds and automated tests, which calls for AWS CodeBuild rather than AWS CodePipeline or the earlier Amazon Connect.

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 connect on-premises applications to cloud-backed storage interfaces, which calls for AWS Storage Gateway rather than EBS volume encryption or the earlier AWS DataSync.

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 connect on-premises applications to cloud-backed storage interfaces, which calls for AWS Storage Gateway rather than EBS snapshot or the earlier AWS DataSync.

AWS DataSync primarily supports the earlier need to accelerate and automate transfers between supported storage locations because dataSync moves files or objects between on-premises and AWS storage systems with verification, but the new task is to connect on-premises applications to cloud-backed storage interfaces; that is why AWS Storage Gateway is preferable here.

Amazon Quick is intended to create dashboards and business intelligence visualizations because Amazon Quick offers analytics and business intelligence capabilities for exploring data; in this design the new outcome is to offer generative AI assistance for supported business and developer workflows, which calls for Amazon Q rather than Amazon Quick or the earlier Amazon Athena.

Amazon Translate is intended to translate text between supported human languages because translate is a machine-translation service used by multilingual applications; in this design the new outcome is to offer generative AI assistance for supported business and developer workflows, which calls for Amazon Q rather than Amazon Translate or the earlier Amazon Athena.

Amazon Athena primarily supports the earlier need to query supported data in S3 using serverless SQL because athena runs interactive SQL queries without provisioning a dedicated database server, but the new task is to offer generative AI assistance for supported business and developer workflows; that is why Amazon Q is preferable here.

RDS read replica addresses the separate need to offload eligible read queries from a relational database primary because read replicas provide copies usable to serve read traffic with replication behavior; it is not as direct as AWS Schema Conversion Tool for the actual requirement to translate supported database schemas and code for heterogeneous migrations.

Database on Amazon EC2 addresses the separate need to retain direct control of database host OS and engine installation because self-managing a database on EC2 leaves patching, backups and high availability largely to the customer; it is not as direct as AWS Schema Conversion Tool for the actual requirement to translate supported database schemas and code for heterogeneous migrations.

AWS Database Migration Service addresses the separate need to move ongoing database data between supported source and destination engines because AWS DMS can perform initial loading and change data capture for supported databases; it is not as direct as AWS Schema Conversion Tool for the actual requirement to translate supported database schemas and code for heterogeneous migrations.

ACID relational transactions addresses the separate need to preserve multi-step data consistency in a relational workload because relational engines support transactional properties appropriate to tightly consistent operations; it is not as direct as AWS Schema Conversion Tool for the actual requirement to translate supported database schemas and code for heterogeneous migrations.

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 AWS Schema Conversion Tool for the actual requirement to translate supported database schemas and code for heterogeneous migrations.

AWS Elastic Beanstalk addresses the separate need to deploy application code with managed environment provisioning because elastic Beanstalk orchestrates supporting AWS resources for supported web application platforms; it is not as direct as Configuration drift detection for the actual requirement to identify when deployed resources diverge from defined templates.

AWS Cloud Development Kit (AWS CDK) addresses the separate need to define AWS infrastructure using familiar programming languages because AWS CDK constructs synthesize infrastructure definitions for deployment through CloudFormation; it is not as direct as Configuration drift detection for the actual requirement to identify when deployed resources diverge from defined templates.

AWS CodeBuild addresses the separate need to compile and test software in a managed build environment because codeBuild runs build and test commands without operating dedicated build servers; it is not as direct as Configuration drift detection for the actual requirement to identify when deployed resources diverge from defined templates.

AWS CloudFormation addresses the separate need to recreate multi-resource infrastructure from versioned templates because cloudFormation models resources as stacks and applies managed creation and update operations; it is not as direct as Configuration drift detection for the actual requirement to identify when deployed resources diverge from defined templates.

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 enable internet routing for resources in a VPC with suitable configuration, which calls for Internet gateway rather than Security group or the earlier NAT 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 enable internet routing for resources in a VPC with suitable configuration, which calls for Internet gateway rather than Amazon VPC or the earlier NAT gateway.

NAT gateway primarily supports the earlier need to let private subnet resources initiate eligible outbound internet connections because a NAT gateway translates egress traffic when appropriate routes are configured, but the new task is to enable internet routing for resources in a VPC with suitable configuration; that is why Internet gateway 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 run container tasks without managing EC2 container hosts, which calls for AWS Fargate rather than EC2 Auto Scaling or the earlier AWS App Runner.

AWS App Runner primarily supports the earlier need to deploy supported web applications or container services without operating servers because app Runner automates build or container deployment and scales supported web services, but the new task is to run container tasks without managing EC2 container hosts; that is why AWS Fargate 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 container tasks without managing EC2 container hosts, which calls for AWS Fargate rather than Amazon ECR or the earlier AWS App Runner.

Multi-AZ application deployment addresses the separate need to survive a failure confined to one Availability Zone because replicated tiers across separate AZs reduce dependence on a single facility group; it is not as direct as Regional disaster recovery tests for the actual requirement to verify a workload can resume in its backup Region.

Regional service scope addresses the separate need to recognize that many AWS resources exist only in a selected Region because regional services require selecting the location where supported resources are created; it is not as direct as Regional disaster recovery tests for the actual requirement to verify a workload can resume in its backup Region.

Multi-Region architecture addresses the separate need to address disaster recovery or geography-spanning application availability because deploying and replicating across Regions can isolate regional failures and serve separate markets; it is not as direct as Regional disaster recovery tests for the actual requirement to verify a workload can resume in its backup Region.

RDS read replica is intended to offload eligible read queries from a relational database primary because read replicas provide copies usable to serve read traffic with replication behavior; in this design the new outcome is to match persistence technology to workload queries and consistency needs, which calls for Database engine choice by use case rather than RDS read replica or the earlier Amazon RDS.

Amazon RDS primarily supports the earlier need to operate a managed relational database engine because RDS automates selected relational database operations including backup and patching, but the new task is to match persistence technology to workload queries and consistency needs; that is why Database engine choice by use case is preferable here.

ACID relational transactions is intended to preserve multi-step data consistency in a relational workload because relational engines support transactional properties appropriate to tightly consistent operations; in this design the new outcome is to match persistence technology to workload queries and consistency needs, which calls for Database engine choice by use case rather than ACID relational transactions or the earlier Amazon RDS.

That description belongs to AWS Management Console because the console provides graphical pages to view and configure AWS resources; it is used to perform occasional AWS administration through a browser interface, not to explain how On-premises deployment provides the function to keep computing equipment operated entirely in an organization's facility.

That description belongs to AWS SDKs because sDKs provide language libraries and request handling for application integrations with AWS APIs; it is used to integrate AWS service requests directly into application source code, not to explain how On-premises deployment provides the function to keep computing equipment operated entirely in an organization's facility.

That description belongs to AWS CLI because the AWS Command Line Interface exposes AWS service operations to terminals and automation; it is used to run scripted AWS API operations from shell commands, not to explain how On-premises deployment provides the function to keep computing equipment operated entirely in an organization's facility.