A SysOps Administrator is tasked with configuring high availability for an Amazon RDS for MariaDB DB instance. The database must support automated, synchronous failover with zero data loss in the event of an Availability Zone outage. Additionally, the administrator must offload read-heavy reporting queries to a separate database endpoint to minimize performance impact on the primary write instance. Which database configuration will satisfy these requirements?
- Modify the database to a Multi-AZ deployment, and create a Read Replica in a separate Availability Zone to handle reporting queries.Answer
- BCreate an RDS Read Replica in a different Availability Zone, and configure the application to perform automated failover to this replica during an outage.
- CModify the DB instance to a Multi-AZ deployment, and configure the reporting application to connect directly to the standby database instance's endpoint.
- DDeploy a Read Replica in a different Availability Zone, and configure an Amazon Route 53 failover routing policy to automatically promote the Read Replica when the primary instance becomes unhealthy.
Answer
Modify the database to a Multi-AZ deployment, and create a Read Replica in a separate Availability Zone to handle reporting queries.
To satisfy both requirements, the database must be configured for Multi-AZ to enable synchronous replication and automatic DNS-based failover. A separate Read Replica must be created to handle the reporting queries because the standby instance in a standard Multi-AZ configuration is passive and cannot be accessed for read queries.
Step-by-Step Solution
Key Concept
RDS Multi-AZ vs. Read Replicas for High Availability and Read Scaling
Estimated Time:1m 30s