easymultiple choiceObjective-mapped

A production application uses an Amazon RDS Multi-AZ DB instance. During an unplanned failover, the database endpoint remains the same. What change should the application team make to handle the failover reliably?

Question 1easymultiple choice
Full question →

A production application uses an Amazon RDS Multi-AZ DB instance. During an unplanned failover, the database endpoint remains the same. What change should the application team make to handle the failover reliably?

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

Distractor review

Hard-code the new writer instance IP address after failover completes.

Multi-AZ failover can route the writer role to a different instance, and instance IP addresses are not stable. Hard-coding IPs creates brittle client configuration and increases recovery time.

B

Best answer

Keep using the same RDS endpoint and implement connection retry logic on failures.

For RDS Multi-AZ, the DB endpoint is designed to remain consistent. During failover, in-flight connections may drop, so the application should treat connection/transaction errors as transient and reconnect with retry (for example, exponential backoff).

C

Distractor review

Disable Multi-AZ and rely on manual intervention to switch endpoints.

Disabling Multi-AZ removes automatic standby failover behavior and increases downtime, which contradicts the goal of resilient failover handling.

D

Distractor review

Move reads to application-side caching only, and avoid reopening DB connections.

Caching does not eliminate write-path dependencies, and failover can terminate existing connections. Avoiding reconnection can cause failed requests and inconsistent behavior when the database becomes available again.

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: Keep using the same RDS endpoint and implement connection retry logic on failures. — In RDS Multi-AZ, AWS performs failover to the standby instance while keeping the DB endpoint unchanged, so the application does not need to look up a new hostname or IP. However, failover can interrupt existing in-flight connections and transactions. The application should therefore use the stable endpoint and implement safe, bounded retry behavior: catch transient DB connection errors, reconnect, and re-attempt the operation where appropriate (often with backoff). This makes the system resilient to the brief disruption caused by the failover. A is wrong because IP addresses for the underlying instances are not meant to be stable across failover events. C is wrong because manual endpoint switching undermines the automated availability benefits of Multi-AZ. D is wrong because caching does not prevent connection interruption during failover, and avoiding reconnections prevents the application from communicating with the database once it is back to a healthy writer state.

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.