- 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.
The cluster endpoint always targets the current writer, and failover-aware reconnect logic helps the application recover from dropped connections after promotion.
- B
Keep using the original writer instance endpoint so the database host name never changes during failover.
Why wrong: An instance endpoint can still point to the old writer after failover, causing write failures until the instance becomes writer again.
- C
Convert the Aurora cluster to Single-AZ so there is only one database node to connect to.
Why wrong: Single-AZ reduces availability and does not improve failover behavior or reduce interruption during maintenance events.
- D
Place Route 53 in front of the database and manually update DNS records whenever failover occurs.
Why wrong: Manual DNS updates increase recovery time and are unnecessary when Aurora endpoints already handle writer promotion.
Aurora Cluster Endpoint Failover: Automatic Reconnection Strategy
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.
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?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue:
"most likely"Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.
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.
- ✓
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.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
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?”
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates 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.
Detailed technical explanation
How to think about this question
Under the hood, the Aurora cluster endpoint is a DNS name that resolves to the current writer instance's IP address; Aurora automatically updates this DNS record within seconds of a failover. The reader endpoint similarly resolves to one of the available reader instances, distributing read-only traffic. In a real-world scenario, applications using connection pooling (e.g., with pgBouncer or RDS Proxy) must also handle connection draining and retry logic to avoid stale connections, as the cluster endpoint DNS change alone does not invalidate already-established TCP connections.
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 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.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 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?
medium- A.Continue using the instance endpoint, but increase application retry count so the writer changes are handled more quickly.
- ✓ B.Use the Aurora cluster writer endpoint for all write operations.
- C.Use a read replica endpoint for writes because it is typically stable across failovers.
- D.Disable Multi-AZ failover so the writer instance never changes and writes remain consistent.
Why B: 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.
Variation 2. 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.
Variation 3. 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.
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.