mediummultiple choiceObjective-mapped

An application writes to an Amazon Aurora DB cluster. After a planned Aurora failover, the application experiences several minutes of connection errors.

The logs show the application continues connecting to the specific DB instance endpoint that was the primary before the failover.

What change most directly improves resilience during Aurora failovers?

Question 1mediummultiple choice
Full question →

An application writes to an Amazon Aurora DB cluster. After a planned Aurora failover, the application experiences several minutes of connection errors.

The logs show the application continues connecting to the specific DB instance endpoint that was the primary before the failover.

What change most directly improves resilience during Aurora failovers?

Answer choices

Why each option matters

Good practice is not just finding the correct option. The wrong answers often show the exact trap the exam wants you to fall into.

A

Best answer

Update the application to use the Aurora cluster writer endpoint for write traffic so it always resolves to the current writer instance.

During failover, Aurora changes which underlying DB instance is the writer. The cluster writer endpoint (for the cluster) always resolves to the current writer. Using the writer endpoint prevents the application from being pinned to an old instance endpoint that may stop accepting writes after failover.

B

Distractor review

Increase Aurora storage autoscaling so failovers are unnecessary.

Storage autoscaling changes storage capacity growth; it does not prevent Aurora failover events caused by maintenance or writer health. Writer endpoint behavior during failover is not resolved by storage scaling.

C

Distractor review

Point both reads and writes to the Aurora reader endpoint to keep the DNS name the same.

The reader endpoint is intended for read traffic. Writes routed to the reader endpoint can fail or violate the intended read/write separation after topology changes.

D

Distractor review

Disable Aurora failover capability so the cluster never switches writer instances.

Disabling failover reduces availability and resilience. In the event the writer becomes unavailable, the application would continue attempting writes to an unhealthy instance longer, causing downtime.

Common exam trap

Common exam trap: answer the scenario, not the keyword

Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.

Technical deep dive

How to think about this question

This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.

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.
  • Use explanations to understand the rule behind the answer.

TExam Day Tips

  • Underline the problem statement mentally.
  • 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.

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.

More questions from this exam

Keep practising from the same exam bank, or move into a focused topic page if this question exposed a weak area.

FAQ

Questions learners often ask

What does this SAA-C03 question test?

Read the scenario before looking for a memorised answer.

What is the correct answer to this question?

The correct answer is: Update the application to use the Aurora cluster writer endpoint for write traffic so it always resolves to the current writer instance. — Aurora failover changes which underlying instance is the writer. If the application uses a fixed instance endpoint, it can keep connecting to the old writer after failover, resulting in connection errors until the endpoint is updated. By using the Aurora cluster writer endpoint, the application always targets the current writer instance, improving resilience across failovers. Why others are wrong: Storage autoscaling does not stop failover behavior. The reader endpoint is not appropriate for writes. Disabling failover directly contradicts the goal of resilience by reducing availability during writer events.

What should I do if I get this SAA-C03 question wrong?

Then try more questions from the same exam bank and focus on understanding why the wrong options are tempting.

Discussion

Loading comments…

Sign in to join the discussion.