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.
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.