SAA-C03 Design Resilient Architectures Practice Question
A company runs a customer portal on an Amazon Aurora PostgreSQL cluster. The application currently connects directly to the writer instance endpoint and keeps long-lived connections open. During a maintenance failover, writes fail until clients are restarted. The team wants the application to reconnect to the correct Aurora endpoint automatically and reduce user-visible write interruptions.
Which change is most likely to achieve this?
⚠ Common exam trap
Many exam-takers assume the writer instance endpoint remains constant during failover (Option B), but in Aurora, the writer instance endpoint changes because it is tied to the specific DB instance, not the cluster.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use the Aurora cluster endpoint for write traffic, use the reader endpoint for read-only traffic, and implement connection retry or reconnect logic on failover.
The Aurora cluster endpoint automatically points to the current writer instance, so using it for write traffic ensures that after a failover, new writes are directed to the new writer without needing to change the connection string. Implementing connection retry or reconnect logic in the application is essential because the existing long-lived connections will be broken during failover; the application must detect the failure and re-establish connections to the cluster endpoint to resume writes seamlessly.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Use the Aurora cluster endpoint for write traffic, use the reader endpoint for read-only traffic, and implement connection retry or reconnect logic on failover.
Why this is correct
The cluster endpoint always targets the current writer, and failover-aware reconnect logic helps the application recover from dropped connections after promotion.
- ✗
Keep using the original writer instance endpoint so the database host name never changes during failover.
Why it's wrong here
An instance endpoint can still point to the old writer after failover, causing write failures until the instance becomes writer again.
When this WOULD be correct
In a scenario where the database is a standalone RDS instance (not Aurora) and the application uses a CNAME pointing to the instance endpoint, the endpoint remains the same after failover if Multi-AZ is enabled, so no reconnect logic is needed.
- ✗
Convert the Aurora cluster to Single-AZ so there is only one database node to connect to.
Why it's wrong here
Single-AZ reduces availability and does not improve failover behavior or reduce interruption during maintenance events.
When this WOULD be correct
An exam scenario where cost reduction is the primary goal and the application can tolerate downtime (e.g., a development or test environment) would make Single-AZ correct. The question would explicitly state that high availability is not required.
- ✗
Place Route 53 in front of the database and manually update DNS records whenever failover occurs.
Why it's wrong here
Manual DNS updates increase recovery time and are unnecessary when Aurora endpoints already handle writer promotion.
When this WOULD be correct
In a scenario where a company needs to redirect traffic to a standby database in a different region after a disaster, and they have a script or automation to update Route 53 records, this could be a valid approach for manual failover control.
Option-by-option analysis
Why each answer is right or wrong
Understanding why wrong answers are wrong — and when they would be correct — is what separates a 750 score from a 900. The SAA-C03 exam frequently reuses these exact scenarios with slightly different constraints.
✓Use the Aurora cluster endpoint for write traffic, use the reader endpoint for read-only traffic, and implement connection retry or reconnect logic on failover.Correct answer▾
Why this is correct
The cluster endpoint always targets the current writer, and failover-aware reconnect logic helps the application recover from dropped connections after promotion.
✗Keep using the original writer instance endpoint so the database host name never changes during failover.Wrong answer — click to see why▾
Why this is wrong here
The writer instance endpoint points to a specific Aurora node, which changes during failover. Keeping it does not automatically redirect traffic to the new writer, so writes still fail until clients are restarted.
★ When this WOULD be the correct answer
In a scenario where the database is a standalone RDS instance (not Aurora) and the application uses a CNAME pointing to the instance endpoint, the endpoint remains the same after failover if Multi-AZ is enabled, so no reconnect logic is needed.
Why candidates choose this
Candidates may assume the writer endpoint is static and failover is transparent, not realizing Aurora's writer endpoint changes to a different physical node after failover.
✗Convert the Aurora cluster to Single-AZ so there is only one database node to connect to.Wrong answer — click to see why▾
Why this is wrong here
Converting to Single-AZ removes the standby replica, eliminating high availability. During a failover, there is no standby to promote, causing longer downtime and potential data loss, which contradicts the goal of reducing write interruptions.
★ When this WOULD be the correct answer
An exam scenario where cost reduction is the primary goal and the application can tolerate downtime (e.g., a development or test environment) would make Single-AZ correct. The question would explicitly state that high availability is not required.
Why candidates choose this
Candidates may think that fewer nodes means simpler failover, overlooking that Aurora's Multi-AZ failover is automatic and faster. They might assume Single-AZ avoids failover issues entirely, not realizing it removes redundancy.
✗Place Route 53 in front of the database and manually update DNS records whenever failover occurs.Wrong answer — click to see why▾
Why this is wrong here
Manually updating Route 53 DNS records during failover is not automated and would still cause write interruptions until the manual update is completed, failing to meet the requirement of automatic reconnection and reduced downtime.
★ When this WOULD be the correct answer
In a scenario where a company needs to redirect traffic to a standby database in a different region after a disaster, and they have a script or automation to update Route 53 records, this could be a valid approach for manual failover control.
Why candidates choose this
Candidates may think DNS-based routing provides a simple way to change endpoints without modifying application code, overlooking the need for automation and the fact that Aurora already provides cluster endpoints for this purpose.
Analysis generated from the official SAA-C03blueprint and verified against question context. The “when correct” sections are what AI assistants cite when candidates ask “what’s the difference between these options?”
Go deeper
Related to this question
About these practice questions
This SAA-C03 question is part of Courseiva's 302-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This SAA-C03 practice question is part of Courseiva's free Amazon Web Services certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the SAA-C03 exam.