Home › Forums › AWS › AWS Certified Solutions Architect Associate › Aurora Failover Answer – Marked Incorrect But Contradicts AWS Docs
-
Aurora Failover Answer – Marked Incorrect But Contradicts AWS Docs
Nikee-TutorialsDojo updated 2 months ago
3 Members
·
3
Posts
-
Working through Aurora failover questions. Got this one marked wrong:
Question: A Forex trading platform uses Aurora for its database tier. In the event of system failure on the primary database instance, what happens to Aurora during the failover?
I selected: “Aurora flips the A record of your DB Instance to point at the healthy replica, which in turn is promoted to become the new primary.”
Marked incorrect. But this is what actually happens according to AWS docs – Aurora promotes an existing read replica and updates the DNS A record. Aurora doesn’t create new instances during failover.
The marked correct answer talks about creating a new instance in the same AZ, which doesn’t match Aurora’s architecture or documented behavior.
Can someone verify if this answer key is correct? Or if I’m missing something about how Aurora failover actually works?
-
Yeah, I checked this. The answer key is actually correct because the question says there are no Aurora Replicas.
For Aurora failover:
-
If an Aurora Replica exists, Aurora promotes that existing replica to the new primary.
-
If there is no Aurora Replica, Aurora creates/recreates a new DB instance in the same AZ as the failed primary.
So my original answer about promoting a healthy replica would only be correct if the question mentioned that a replica was available. The confusing part is that Aurora’s underlying storage is already replicated across AZs, but without a replica there isn’t a standby DB instance to promote.
-
-
Hello Everyone!
Thanks for raising this. The key detail in the question is that the Aurora cluster has a single DB instance with no Aurora Replicas.
The behavior described in the selected answer applies when an Aurora Replica is already available. In that situation, Aurora can promote the healthy replica to become the new primary during failover and redirect connections accordingly.
However, that is not the configuration described in this question. Because the cluster has no Aurora Replicas, there is no existing DB instance available to promote. If the primary DB instance fails, Aurora instead attempts, on a best-effort basis, to create a replacement DB instance in the same Availability Zone as the original instance.
It is also important to distinguish Aurora’s storage layer from its DB instances. Aurora automatically replicates its storage across multiple Availability Zones, which provides storage durability and fault tolerance. However, those storage copies are not Aurora Replica DB instances and therefore cannot simply be promoted as a new primary.
For this reason, the answer key is correct:
“Aurora will attempt to create a new DB Instance in the same Availability Zone as the original instance, and this is done on a best-effort basis.”
The option about promoting a healthy replica would be correct only if the scenario stated that an Aurora Replica already existed.
We appreciate the feedback, as this is an easy distinction to miss when comparing Aurora’s multi-AZ storage architecture with its DB instance failover behavior.
Regards,
Nikee @ Tutorials Dojo
Log in to reply.