- A
Continue using the instance endpoint, but increase application retry count so the writer changes are handled more quickly.
Why wrong: Retries can reduce perceived impact, but the instance endpoint can become non-writer after failover. If the application continues targeting an instance endpoint that no longer accepts writes, retries will continue to fail until the code or endpoint selection is corrected.
- B
Use the Aurora cluster writer endpoint for all write operations.
Aurora provides a writer endpoint designed specifically for write traffic. During failover, Aurora updates where the writer endpoint points, so the same DNS name continues to resolve to the current writer instance without requiring manual endpoint changes in the application.
- C
Use a read replica endpoint for writes because it is typically stable across failovers.
Why wrong: Read replica (reader) endpoints are intended for read workloads. They can route to non-writer instances, and those endpoints should not be used for writes because they may reject write operations.
- D
Disable Multi-AZ failover so the writer instance never changes and writes remain consistent.
Why wrong: Disabling failover removes an important resiliency mechanism and increases downtime risk. It improves endpoint stability only by trading away availability during instance or AZ issues.
Quick Answer
The answer is to use the Aurora cluster writer endpoint for all write operations. This is correct because the cluster writer endpoint always resolves to the current primary instance, even after a failover, while the instance endpoint is tied to a specific physical node. When you use the instance endpoint and a failover occurs, the application continues trying to write to the old, now-read-only instance, causing connection errors and timeouts until the DNS record is manually updated. On the SAA-C03 exam, this scenario tests your understanding of Aurora endpoint types and how they enable automatic failover without manual updates. A common trap is confusing the instance endpoint with the cluster endpoint; remember that only the cluster writer endpoint provides seamless failover resilience. Memory tip: think of the cluster writer endpoint as a “dynamic pointer” that always follows the leader, whereas an instance endpoint is a “static address” that breaks when the leader moves.
SAA-C03 Design Resilient Architectures Practice Question
This SAA-C03 practice question tests your understanding of design resilient architectures. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.
A company uses an Amazon Aurora DB cluster in a Multi-AZ configuration. During a planned failover of the writer instance, the database endpoints in the application are updated incorrectly. After failover, reads work but writes fail with connection errors and timeouts for several minutes. The team currently uses the instance endpoint for the writer. What should they change to improve write resilience during failovers?
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 writer endpoint for all write operations.
The Aurora cluster writer endpoint always points to the current primary (writer) instance, even after a failover. By using this endpoint instead of a static instance endpoint, the application automatically resolves to the new writer without manual updates, eliminating connection errors and timeouts during failover transitions.
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.
- ✗
Continue using the instance endpoint, but increase application retry count so the writer changes are handled more quickly.
Why it's wrong here
Retries can reduce perceived impact, but the instance endpoint can become non-writer after failover. If the application continues targeting an instance endpoint that no longer accepts writes, retries will continue to fail until the code or endpoint selection is corrected.
- ✓
Use the Aurora cluster writer endpoint for all write operations.
Why this is correct
Aurora provides a writer endpoint designed specifically for write traffic. During failover, Aurora updates where the writer endpoint points, so the same DNS name continues to resolve to the current writer instance without requiring manual endpoint changes in the application.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use a read replica endpoint for writes because it is typically stable across failovers.
Why it's wrong here
Read replica (reader) endpoints are intended for read workloads. They can route to non-writer instances, and those endpoints should not be used for writes because they may reject write operations.
- ✗
Disable Multi-AZ failover so the writer instance never changes and writes remain consistent.
Why it's wrong here
Disabling failover removes an important resiliency mechanism and increases downtime risk. It improves endpoint stability only by trading away availability during instance or AZ issues.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse the instance endpoint (which is static and tied to a specific instance) with the cluster endpoint (which is dynamic and always points to the current writer), assuming any endpoint will automatically follow failover.
Detailed technical explanation
How to think about this question
Under the hood, the Aurora cluster writer endpoint is a DNS name that is automatically updated within seconds of a failover to resolve to the new writer instance's private IP. The application's database driver typically caches DNS results, so configuring a short TTL (e.g., 1–5 seconds) on the DNS record and enabling JDBC connection validation (e.g., with `testOnBorrow` or `connectionTestQuery`) ensures stale connections are recycled quickly. In real-world scenarios, failing to use the cluster endpoint can cause extended outages during patching or AZ-level failures, especially in auto-scaling environments where instance IPs change frequently.
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 — study guide chapter
Learn the concepts, then practise the questions
- →
Design Resilient Architectures practice questions
Targeted practice on this topic area only
- →
All SAA-C03 questions
1,040 questions across all exam domains
- →
SAA-C03 study guide
Full concept coverage aligned to exam objectives
- →
SAA-C03 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related SAA-C03 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design Secure Architectures practice questions
Practise SAA-C03 questions linked to Design Secure Architectures.
Design Resilient Architectures practice questions
Practise SAA-C03 questions linked to Design Resilient Architectures.
Design High-Performing Architectures practice questions
Practise SAA-C03 questions linked to Design High-Performing Architectures.
Design Cost-Optimized Architectures practice questions
Practise SAA-C03 questions linked to Design Cost-Optimized Architectures.
SAA-C03 VPC practice questions
Practise SAA-C03 questions linked to SAA-C03 VPC.
SAA-C03 S3 lifecycle policy questions
Practise SAA-C03 questions linked to SAA-C03 S3 lifecycle policy questions.
SAA-C03 RDS Multi-AZ questions
Practise SAA-C03 questions linked to SAA-C03 RDS Multi-AZ questions.
SAA-C03 IAM policy practice questions
Practise SAA-C03 questions linked to SAA-C03 IAM policy.
SAA-C03 Route 53 failover questions
Practise SAA-C03 questions linked to SAA-C03 Route 53 failover questions.
SAA-C03 CloudFront practice questions
Practise SAA-C03 questions linked to SAA-C03 CloudFront.
SAA-C03 NAT gateway questions
Practise SAA-C03 questions linked to SAA-C03 NAT gateway questions.
SAA-C03 VPC endpoint questions
Practise SAA-C03 questions linked to SAA-C03 VPC endpoint questions.
Practice this exam
Start a free SAA-C03 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this SAA-C03 question test?
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: Use the Aurora cluster writer endpoint for all write operations. — The Aurora cluster writer endpoint always points to the current primary (writer) instance, even after a failover. By using this endpoint instead of a static instance endpoint, the application automatically resolves to the new writer without manual updates, eliminating connection errors and timeouts during failover transitions.
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 →
Same concept, more angles
3 more ways this is tested on SAA-C03
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. 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?
medium- ✓ A.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.
- B.Keep using the original writer instance endpoint so the database host name never changes during failover.
- C.Convert the Aurora cluster to Single-AZ so there is only one database node to connect to.
- D.Place Route 53 in front of the database and manually update DNS records whenever failover occurs.
Why A: 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.
Variation 2. 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?
medium- ✓ A.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.
- B.Keep using the original writer instance endpoint so the database host name never changes during failover.
- C.Convert the Aurora cluster to Single-AZ so there is only one database node to connect to.
- D.Place Route 53 in front of the database and manually update DNS records whenever failover occurs.
Why A: The Aurora cluster endpoint automatically points to the current writer instance and updates DNS after a failover, so the application can reconnect without manual intervention. However, because the application keeps long-lived connections, it must implement connection retry or reconnect logic to detect the broken connection and re-resolve the DNS name to the new writer. This combination ensures writes resume automatically after failover.
Variation 3. A company runs an Amazon Aurora DB cluster with a Multi-AZ deployment. The application is configured with a hard-coded endpoint that points to the current writer *DB instance* (an instance-specific endpoint), rather than the Aurora cluster writer endpoint. During an unexpected AZ failure, Aurora promotes the standby to become the new writer. However, the application continues to fail to connect until an operator updates the hard-coded endpoint. What change most directly improves resiliency so the application automatically reconnects after failover?
medium- A.Keep using the writer DB instance endpoint, but increase the client connection timeout.
- ✓ B.Connect using the Aurora cluster writer endpoint so DNS resolves to the current writer after failover.
- C.Disable Multi-AZ failover and rely on manual snapshot restore to bring the database back online.
- D.Enable cross-Region read replicas and route application traffic to the replica during the outage.
Why B: Option B is correct because the Aurora cluster writer endpoint is a DNS name that always resolves to the current writer instance in the cluster, even after a failover. By using this endpoint instead of a hard-coded instance-specific endpoint, the application automatically reconnects to the new writer without manual intervention, directly improving resiliency.
Keep practising
More SAA-C03 practice questions
- A content publishing system uses Lambda functions that call an unreliable third-party API. Failed events must be retaine…
- A startup runs two EC2-based workloads in the same AWS Region. Its customer-facing API is always on, and its nightly vid…
- A warehouse integration service must use shared file storage across Linux EC2 instances in multiple Availability Zones.…
- A team runs a stateless web app on Amazon EC2 behind an Application Load Balancer. During traffic spikes, new EC2 instan…
- A service in private subnets downloads product images from Amazon S3 and stores job state in DynamoDB. A NAT Gateway is…
- A static site is hosted in Amazon S3 and delivered by CloudFront. After a frontend release, the same JavaScript bundles…
Last reviewed: Jun 11, 2026
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.