A retail company runs a production transaction-processing application on an Amazon RDS for MySQL DB instance. The database must be highly resilient to Availability Zone outages with a Recovery Time Objective (RTO) of less than 120 seconds. Additionally, the application requires read scaling to handle heavy reporting queries during business hours without impacting write operations on the primary database instance.
Which two database configurations should the solutions architect choose to meet these requirements? (Select TWO.)
- Deploy the Amazon RDS DB instance in a Multi-AZ deployment.Answer
- Create Amazon RDS Read Replicas and direct read traffic to the read replica endpoints.Answer
- CDeploy the Amazon RDS DB instance in a Multi-AZ deployment and configure the application to route read queries to the standby database instance.
- DDeploy a single-AZ DB instance and configure the application to automatically promote a Read Replica to primary during a primary database outage.
- EDeploy the database in a single-AZ configuration and set up an Amazon Route 53 latency routing policy with health checks to automatically fail over database write traffic to a Read Replica.
Answer
Deploy the database in a Multi-AZ configuration to achieve high availability and low RTO, and create RDS Read Replicas to scale read performance.
To meet the requirements, the database must support automatic failover for high availability and read scaling. A Multi-AZ deployment creates a primary DB instance and a synchronous standby replica in a different Availability Zone. If the primary instance fails, RDS automatically performs a failover to the standby, achieving a low RTO. To scale read queries without affecting the primary write performance, creating RDS Read Replicas and directing reporting traffic to the read replica endpoints is the correct approach.
Step-by-Step Solution
Key Concept
Distinguishing between RDS Multi-AZ deployments for high availability/failover and RDS Read Replicas for scaling read operations.