SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Application configuration
JDBC URL: jdbc:postgresql://mydb-instance-1.abcdefghijkl.us-east-1.rds.amazonaws.com:5432/app
Aurora event log
11:15:02 Failover initiated
11:15:04 Writer moved to a different instance
11:18:20 Application still reporting connection refused errors
Notes from the team
The application uses a connection pool and does not re-resolve the endpoint quickly.
Based on the exhibit, the application sees several minutes of connection errors during an Aurora failover. What is the best change to reduce failover impact?
Exhibit
Application configuration
JDBC URL: jdbc:postgresql://mydb-instance-1.abcdefghijkl.us-east-1.rds.amazonaws.com:5432/app
Aurora event log
11:15:02 Failover initiated
11:15:04 Writer moved to a different instance
11:18:20 Application still reporting connection refused errors
Notes from the team
The application uses a connection pool and does not re-resolve the endpoint quickly.
A
Change the application to use the Aurora cluster writer endpoint and retry transient connections.
The current configuration targets a specific instance endpoint, which becomes stale after failover. The Aurora cluster writer endpoint always resolves to the current writer, so the application can reconnect without manual endpoint changes. Adding retries with backoff helps the application survive the short DNS and connection transition during failover.
B
Add an Aurora read replica and keep using the same JDBC URL.
Why wrong: A read replica helps scale read traffic, but it does not solve failover for the writer or the stale-connection problem caused by using a fixed instance endpoint. The application still needs to connect through the cluster writer endpoint.
C
Increase the EC2 instance size of the application servers.
Why wrong: More application server capacity does not address database endpoint changes or stale pooled connections. The failure mode is connectivity to the wrong database endpoint, not lack of compute resources on the app tier.
D
Switch to a single-AZ RDS PostgreSQL instance for simpler connectivity.
Why wrong: A single-AZ database would reduce resilience rather than improve it. It might simplify the topology, but it would increase downtime during infrastructure failure and defeat the purpose of Aurora failover.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change the application to use the Aurora cluster writer endpoint and retry transient connections.
The Aurora cluster writer endpoint always points to the current primary instance, even after a failover. By using this endpoint and implementing retry logic for transient connection errors, the application can automatically reconnect to the new writer without manual intervention, reducing the impact of the failover from several minutes to seconds.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✓
Change the application to use the Aurora cluster writer endpoint and retry transient connections.
Why this is correct
The current configuration targets a specific instance endpoint, which becomes stale after failover. The Aurora cluster writer endpoint always resolves to the current writer, so the application can reconnect without manual endpoint changes. Adding retries with backoff helps the application survive the short DNS and connection transition during failover.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add an Aurora read replica and keep using the same JDBC URL.
Why it's wrong here
A read replica helps scale read traffic, but it does not solve failover for the writer or the stale-connection problem caused by using a fixed instance endpoint. The application still needs to connect through the cluster writer endpoint.
When this WOULD be correct
This option would be correct in a scenario where the application primarily performs read operations and needs to offload read traffic from the primary database to improve read performance or availability. For example, a reporting application that can tolerate stale reads could use read replicas to distribute load.
✗
Increase the EC2 instance size of the application servers.
Why it's wrong here
More application server capacity does not address database endpoint changes or stale pooled connections. The failure mode is connectivity to the wrong database endpoint, not lack of compute resources on the app tier.
When this WOULD be correct
This option would be correct in a scenario where the application is experiencing performance degradation due to CPU or memory exhaustion on the application servers, and the database is healthy. For example, if an application's response times increase under load and CloudWatch shows high EC2 CPU utilization, resizing to a larger instance type would alleviate the bottleneck.
✗
Switch to a single-AZ RDS PostgreSQL instance for simpler connectivity.
Why it's wrong here
A single-AZ database would reduce resilience rather than improve it. It might simplify the topology, but it would increase downtime during infrastructure failure and defeat the purpose of Aurora failover.
When this WOULD be correct
This option would be correct if the question asked for the simplest, lowest-cost database solution for a non-critical application that can tolerate downtime and does not require high availability or failover support.
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.
✓Change the application to use the Aurora cluster writer endpoint and retry transient connections.Correct answer▾
Why this is correct
The current configuration targets a specific instance endpoint, which becomes stale after failover. The Aurora cluster writer endpoint always resolves to the current writer, so the application can reconnect without manual endpoint changes. Adding retries with backoff helps the application survive the short DNS and connection transition during failover.
✗Add an Aurora read replica and keep using the same JDBC URL.Wrong answer — click to see why▾
Why this is wrong here
Adding a read replica does not reduce failover impact because the application still uses the same JDBC URL, which points to the writer endpoint. During failover, the writer endpoint may be unavailable, and read replicas cannot handle write operations, so connection errors persist.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the application primarily performs read operations and needs to offload read traffic from the primary database to improve read performance or availability. For example, a reporting application that can tolerate stale reads could use read replicas to distribute load.
Why candidates choose this
Candidates may think that adding a read replica provides high availability or redundancy, but they overlook that the application's JDBC URL still points to the writer endpoint, which is the single point of failure during failover.
✗Increase the EC2 instance size of the application servers.Wrong answer — click to see why▾
Why this is wrong here
Increasing EC2 instance size addresses application-side compute capacity, not database failover connectivity issues. The connection errors stem from DNS propagation delays and endpoint changes during Aurora failover, which are unaffected by application server size.
★ When this WOULD be the correct answer
This option would be correct in a scenario where the application is experiencing performance degradation due to CPU or memory exhaustion on the application servers, and the database is healthy. For example, if an application's response times increase under load and CloudWatch shows high EC2 CPU utilization, resizing to a larger instance type would alleviate the bottleneck.
Why candidates choose this
Candidates may assume that increasing server resources can compensate for any performance issue, including database failover delays, or they might misinterpret 'connection errors' as a symptom of insufficient application capacity rather than a database endpoint issue.
✗Switch to a single-AZ RDS PostgreSQL instance for simpler connectivity.Wrong answer — click to see why▾
Why this is wrong here
Switching to a single-AZ RDS PostgreSQL instance removes high availability and does not address failover impact; it actually increases downtime risk during a failure.
★ When this WOULD be the correct answer
This option would be correct if the question asked for the simplest, lowest-cost database solution for a non-critical application that can tolerate downtime and does not require high availability or failover support.
Why candidates choose this
Candidates may think simplifying the architecture by removing Aurora's complexity will reduce failover issues, but they overlook that single-AZ lacks failover capability entirely.
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?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think adding read replicas or scaling application servers will fix failover connectivity, but the real issue is that the application must use the correct endpoint and handle transient disconnections gracefully.
Detailed technical explanation
How to think about this question
Aurora failover typically completes within 30–60 seconds, but application connection pools may hold stale DNS or TCP connections to the old writer. Using the cluster writer endpoint (a DNS name that updates within seconds after failover) combined with retry logic (e.g., exponential backoff with jitter) allows the application to recover quickly. The JDBC driver's connection timeout and validation queries (e.g., SELECT 1) can further reduce perceived downtime.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Design Resilient Architectures — This question tests Design Resilient Architectures — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Change the application to use the Aurora cluster writer endpoint and retry transient connections. — The Aurora cluster writer endpoint always points to the current primary instance, even after a failover. By using this endpoint and implementing retry logic for transient connection errors, the application can automatically reconnect to the new writer without manual intervention, reducing the impact of the failover from several minutes to seconds.
What should I do if I get this SAA-C03 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.