DBS-C01 · Question #6
A company with branch offices in Portland, New York, and Singapore has a three-tier web application that leverages a shared database. The database runs on Amazon RDS for MySQL and is hosted in the…
The correct answer is B. Create an RDS read replica in the ap-southeast-1 Region from the primary RDS DB instance in. Explanation Option B is correct because creating an RDS Read Replica in ap-southeast-1 (Singapore's nearest AWS region) allows Singapore-based users to read data from a local replica rather than reaching all the way to us-west-2, dramatically reducing latency and improving…
Question
A company with branch offices in Portland, New York, and Singapore has a three-tier web application that leverages a shared database. The database runs on Amazon RDS for MySQL and is hosted in the us-west-2 Region. The application has a distributed front end deployed in the us-west-2, ap-southheast-1, and us-east-2 Regions. This front end is used as a dashboard for Sales Managers in each branch office to see current sales statistics. There are complaints that the dashboard performs more slowly in the Singapore location than it does in Portland or New York. A solution is needed to provide consistent performance for all users in each location. Which set of actions will meet these requirements?
Options
- ATake a snapshot of the instance in the us-west-2 Region. Create a new instance from the
- BCreate an RDS read replica in the ap-southeast-1 Region from the primary RDS DB instance in
- CCreate a new RDS instance in the ap-southeast-1 Region. Use AWS DMS and change data
- DCreate an RDS read replica in the us-west-2 Region where the primary instance resides. Create a
How the community answered
(27 responses)- A7% (2)
- B81% (22)
- C4% (1)
- D7% (2)
Explanation
Explanation
Option B is correct because creating an RDS Read Replica in ap-southeast-1 (Singapore's nearest AWS region) allows Singapore-based users to read data from a local replica rather than reaching all the way to us-west-2, dramatically reducing latency and improving dashboard performance. Read Replicas are purpose-built for exactly this use case - offloading read-heavy workloads like dashboards to geographically distributed copies of the data.
Option A is wrong because taking a snapshot and creating a new instance is a one-time migration, not a continuously synchronized solution - the new instance would immediately become stale as new sales data is written. Option C is incorrect because AWS DMS with change data capture (CDC) is an overly complex and costly solution when RDS Read Replicas already provide built-in, managed replication natively within RDS. Option D is wrong because creating a Read Replica in the same region as the primary (us-west-2) does nothing to address the geographical distance that is causing Singapore's latency problem.
Memory Tip: Think "Read Replica = Read Relief at a Distance" - whenever users far from the primary DB are experiencing slow read performance (like viewing a dashboard), place a Read Replica in their nearest region. If writes were slow, that would be a different problem requiring a different solution.
Topics
Community Discussion
No community discussion yet for this question.