RDS Multi-AZ vs Read Replica — When to Use Each (SAA-C03)
RDS Multi-AZ and Read Replicas are the two most-confused RDS features on the AWS Solutions Architect Associate exam. They solve different problems. This page explains the difference, shows how AWS tests it, and gives you a rule that covers most exam variations.
Short answer
The correct answer is B. Enable Multi-AZ deployment and create one or more Read Replicas in a separate Availability Zone.
This scenario has two distinct requirements: read offload and AZ-failure resilience. Multi-AZ provides automatic failover to a synchronous standby in a different AZ — the endpoint DNS name is updated automatically and no data is lost because replication is synchronous. Read Replicas offload read traffic by providing additional read endpoints using asynchronous replication. These two features are complementary, not mutually exclusive. You can have both a Multi-AZ standby (for HA) and Read Replicas (for read scale) simultaneously. Option A is wrong because a Read Replica in the same AZ as the primary does not help with AZ failure. Option C is wrong because Read Replicas use asynchronous replication — in a failover scenario they may have slight lag and require manual promotion. Option D is wrong because automated backups with a manual standby provides neither automatic failover nor low RTO.
The Question
A company runs a production MySQL database on Amazon RDS. The database experiences heavy read traffic from reporting queries that slow down the primary instance. The company also needs to ensure the database can automatically recover from an Availability Zone failure with minimal downtime and no data loss. Which combination of features should a solutions architect recommend?
Why B is correct
This scenario has two distinct requirements: read offload and AZ-failure resilience. Multi-AZ provides automatic failover to a synchronous standby in a different AZ — the endpoint DNS name is updated automatically and no data is lost because replication is synchronous. Read Replicas offload read traffic by providing additional read endpoints using asynchronous replication. These two features are complementary, not mutually exclusive. You can have both a Multi-AZ standby (for HA) and Read Replicas (for read scale) simultaneously. Option A is wrong because a Read Replica in the same AZ as the primary does not help with AZ failure. Option C is wrong because Read Replicas use asynchronous replication — in a failover scenario they may have slight lag and require manual promotion. Option D is wrong because automated backups with a manual standby provides neither automatic failover nor low RTO.
Why the other options are wrong
A Read Replica in the same AZ as the primary provides read offload but zero protection against an AZ failure — if the AZ goes down, both the primary and the replica become unavailable.
Read Replicas use asynchronous replication, meaning they may lag the primary by seconds. In a failover scenario, they require manual promotion, manual DNS updates, and may have a small amount of data loss. They are not a substitute for Multi-AZ.
Automated backups restore from a point in time but require significant recovery time (RTO of minutes to hours). A manually maintained standby has no automatic failover and does not qualify as "minimal downtime."
RDS Multi-AZ vs Read Replica: the decision framework
Multi-AZ and Read Replicas are designed for different jobs and AWS tests this distinction on almost every SAA-C03 exam. Multi-AZ is a high availability feature. When you enable Multi-AZ, AWS maintains a synchronous standby replica in a different Availability Zone. The standby receives every transaction at the same time as the primary — there is no replication lag. If the primary AZ fails, RDS automatically updates the DNS endpoint to point to the standby. This failover typically completes in 60–120 seconds. The standby is NOT accessible for reads or any other purpose during normal operations — it exists only for failover. Key words on the exam: "high availability," "automatic failover," "minimal downtime," "no data loss," "AZ failure" — all point to Multi-AZ. Read Replicas are a read scalability feature. They use asynchronous replication, which means they may be slightly behind the primary. You connect to a Read Replica using a separate DNS endpoint and route read-only queries (SELECT statements) to it to offload the primary. Key words: "read-heavy workload," "reporting queries," "read traffic," "analytics" — all point to Read Replicas. Read Replicas can be promoted to standalone primary databases, but this is a manual operation that takes time and causes brief downtime. Exam trap: "promote a Read Replica" is NOT the same as Multi-AZ automatic failover. Another trap: you CAN enable Multi-AZ on a Read Replica itself (nested), creating a read replica that also has HA. Important defaults: Read Replicas can be in the same Region or cross-region. Cross-region Read Replicas add disaster recovery capability. Multi-AZ standby always stays in the same Region.
Ready to see how you'd score?
Take the free practice quiz and find out which AWS Solutions Architect Associate domains you need to focus on. No signup required.
Practice 5 similar questions
Same cert, same or adjacent domain. Use these after reviewing the explanation.