SAP-C02 · Question #582
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…
The correct answer is C. Configure a cross-Region read replica for the RDS database in the new Region Change the. The company needs to expand its sales reporting application to a new European AWS Region, leveraging an existing RDS MySQL database with a high read-to-write ratio, and route European users to the new regional API endpoint.
Question
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?
Options
- AUse an AWS Database Migration Service (AWS DMS) task with full load to replicate the primary
- BUse an AWS Database Migration Service (AWS DMS) task with full load plus change data
- CConfigure a cross-Region read replica for the RDS database in the new Region Change the
- DConfigure a cross-Region read replica for the RDS database in the new Region. Change the
How the community answered
(21 responses)- A14% (3)
- B5% (1)
- C76% (16)
- D5% (1)
Why each option
The company needs to expand its sales reporting application to a new European AWS Region, leveraging an existing RDS MySQL database with a high read-to-write ratio, and route European users to the new regional API endpoint.
Using AWS DMS with a full load task is typically for initial migration or one-time data transfer, not for continuous, low-latency, cross-Region replication of a read-heavy relational database, which an RDS read replica is specifically designed for.
While AWS DMS with CDC can provide continuous replication, an RDS cross-Region read replica is a more integrated and operationally simpler solution specifically for replicating an RDS database, especially for read-heavy workloads.
Configuring a cross-Region read replica for the Amazon RDS MySQL database in the new European Region effectively handles the >90% read-only traffic locally, reducing latency for European users. Changing the Route 53 routing policy to geolocation or latency-based then directs users to the nearest API Gateway endpoint, optimizing performance and availability.
This option is a partial statement, but assuming it implies something similar to C, it is not the chosen correct option as it lacks the full context of the routing policy change.
Concept tested: Cross-Region RDS Read Replicas and Global Routing
Source: https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/Overview.Replication.CrossRegion.html
Community Discussion
No community discussion yet for this question.