mediummultiple choiceObjective-mapped

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?

Question 1mediummultiple choice
Full 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?

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

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

Distractor review

Keep using the original writer instance endpoint so the database host name never changes during failover.

An instance endpoint can still point to the old writer after failover, causing write failures until the instance becomes writer again.

C

Distractor review

Convert the Aurora cluster to Single-AZ so there is only one database node to connect to.

Single-AZ reduces availability and does not improve failover behavior or reduce interruption during maintenance events.

D

Distractor review

Place Route 53 in front of the database and manually update DNS records whenever failover occurs.

Manual DNS updates increase recovery time and are unnecessary when Aurora endpoints already handle writer promotion.

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: 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. — Aurora failover promotes a new writer and updates the cluster endpoint to point to that writer, but applications with long-lived connections still need to reconnect or retry after the old connection drops. Using the cluster endpoint for write traffic avoids pinning the app to a specific instance, and using the reader endpoint for read-only traffic keeps read scaling separate. Failover-aware reconnect logic is what reduces user-visible write interruptions after a maintenance event. Why others are wrong: Pinning the application to the original writer instance endpoint can leave the app connected to the old instance after failover, causing write errors. Switching to Single-AZ removes the resilience benefit of Aurora failover. Putting Route 53 in front of the database is unnecessary and would add operational overhead without solving stale database connections.

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.