Which solution will meet these requirements?

By:
In: SAP-C02
Tagged:
With: 2 Comments
A company runs its sales reporting application in an AWS Region in the United States.The application uses an Amazon API Gateway Regional API and AWS Lambda functions to generate on-demand reports from data in an Amazon RDS for MySQL database.The frontend of the application is hosted on Amazon S3 and is accessed by users through an Amazon CloudFront distribution.The company is using Amazon Route 53 as the DNS service for the domain.Route 53 is configured with a simple routing policy to route traffic to the API Gateway API.In the next 6 months, the company plans to expand operations to Europe.More than 90% of the database traffic is read-only traffic.The company has already deployed an API Gateway API and Lambda functions in the new Region.A solutions architect must design a solution that minimizes latency for users who download reports.

Which solution will meet these requirements?

Use an AWS Database Migration Service (AWS DMS) task with full load to replicate the primary database in the original Region to the database in the new Region. Change the Route 53 record to latency-based routing to connect to the API Gateway API.

Use an AWS Database Migration Service (AWS DMS) task with full load plus change data capture (CDC) to replicate the primary database in the original Region to the database in the new Region. Change the Route 53 record to geolocation routing to connect to the API Gateway API.

Configure a cross-Region read replica for the RDS database in the new Region Change the Route 53 record to latency-based routing to connect to the API Gateway API.

Configure a cross-Region read replica for the RDS database in the new Region. Change the Route 53 record to geolocation routing to connect to the API Gateway API.

Explanations:

AWS DMS is designed for database migration, not for read replica synchronization. A full load replication task would not support the required real-time database reads across Regions. Latency-based routing would not optimize for read-only traffic.

AWS DMS with full load plus CDC is useful for migration but not optimal for real-time read-only database traffic. Geolocation routing is not necessary for minimizing latency for users accessing an API.

Cross-Region read replicas provide low-latency reads from a geographically closer database. Latency-based routing ensures that users are directed to the API Gateway in the Region with the lowest latency.

Geolocation routing is not the best choice for minimizing latency when read-heavy traffic is the primary concern. Latency-based routing would be more efficient in ensuring users connect to the nearest Region.

2026-03-19

2 Comments

  1. Jonathan
    Author

    I plot that the answer is:
    Configure a cross-Region read replica for the RDS database in the new Region Change the Route 53 record to latency-based routing to connect to the API Gateway API.

  2. Barbara
    Author

    I appraise that the answer is:
    Configure a cross-Region read replica for the RDS database in the new Region Change the Route 53 record to latency-based routing to connect to the API Gateway API.

Leave a Reply

Your email address will not be published. Required fields are marked *

twelve + two =