SOA-C02 Question 68
Select 2You are managing a MySQL database on Amazon RDS in a production environment that requires high availability and low-latency reads for multiple geographically distributed applications. You need to configure a solution that uses read replicas to offload read traffic and ensures disaster recovery in case the primary database fails. Which of the following steps should you take to meet these requirements?
- A
Create an Amazon RDS read replica in the same region as the primary database and enable Multi-AZ deployment.
- B
Configure an Amazon Aurora Global Database and use Aurora Replicas in each secondary region.
- C
Create Amazon RDS read replicas in multiple regions to distribute read traffic across regions.
- D
Promote an Amazon RDS read replica to a standalone database instance for disaster recovery.
- E
Enable automatic failover for Amazon RDS read replicas to ensure continuity during primary instance failure.
Show answer and explanation
Correct answers: B, C
Explanation
To ensure high availability and low-latency reads for a geographically distributed application, Amazon Aurora Global Database with Aurora Replicas offers an optimal solution because it supports low-latency reads across regions and disaster recovery. Additionally, creating RDS read replicas in multiple regions helps distribute read traffic geographically, but it requires manual intervention for failover. Combining these approaches ensures scalability and availability for the production workload.
- A. Incorrect.
Incorrect: Amazon RDS read replicas cannot be configured with Multi-AZ deployment. Multi-AZ is for high availability of the primary database, while read replicas are used to scale read traffic.
- B. Correct.
Correct: Aurora Global Database allows you to use Aurora Replicas in secondary regions for low-latency reads and disaster recovery, making it an ideal solution for geographically distributed applications.
- C. Correct.
Correct: Creating Amazon RDS read replicas in multiple regions helps distribute read traffic geographically and provides a manual failover option in case of primary instance failure.
- D. Incorrect.
Incorrect: Promoting an RDS read replica to a standalone database is a manual process and does not automatically ensure disaster recovery or high availability for the primary database.
- E. Incorrect.
Incorrect: RDS read replicas do not support automatic failover. Failover is only available with Multi-AZ deployments for the primary database, not for read replicas.