mediummulti selectObjective-mapped

An application uses an Amazon RDS Multi-AZ DB instance. During a failover test, connections fail until the application is restarted, even though the database comes back online. Which two changes should the team make to improve resilience during failover? Select two.

Question 1mediummulti select
Full question →

An application uses an Amazon RDS Multi-AZ DB instance. During a failover test, connections fail until the application is restarted, even though the database comes back online. Which two changes should the team make to improve resilience during failover? Select two.

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

Cache and reconnect to the current writer IP address to avoid DNS lookups during failover.

Caching an IP address makes failover worse because the writer endpoint can move during a Multi-AZ event. The cached address becomes stale and keeps the application pointed at the old database node.

B

Best answer

Use the RDS endpoint name instead of hard-coding the current instance IP or hostname in the application.

The RDS endpoint abstracts the underlying writer instance. When failover occurs, AWS updates the endpoint to point at the new writer, so the application should reconnect by using the managed name rather than a fixed IP or hostname.

C

Distractor review

Switch to a read replica and let it promote manually after every outage.

A read replica is primarily for read scaling and asynchronous replication. It is not the standard automatic failover mechanism for an RDS Multi-AZ deployment, and manual promotion increases recovery time and operational complexity.

D

Best answer

Add retry logic with exponential backoff for transient connection and DNS resolution errors.

Failover causes a short interruption while connections drop and DNS records converge. Client-side retries with exponential backoff allow the application to absorb temporary connection failures without requiring a restart.

E

Distractor review

Disable connection pooling so each request opens a fresh socket during normal operation.

Disabling pooling increases connection overhead and adds latency, but it does not solve the failover problem. The application still needs endpoint abstraction and retry behavior to reconnect successfully after the writer changes.

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 RDS endpoint name instead of hard-coding the current instance IP or hostname in the application. — Using the database endpoint keeps the application pointed at the correct writer after failover, because the endpoint abstracts the underlying instance change. Adding retry logic with exponential backoff lets the application absorb the short disruption that occurs while DNS and connections converge. These two changes are the most practical way to make an RDS Multi-AZ application recover cleanly without manual restarts. Hard-coding an IP or hostname defeats the purpose of the managed endpoint and will break when the writer changes. A read replica is for read scaling and does not provide the same automatic writer failover behavior. Disabling connection pooling only adds overhead; it does not improve failover resilience and can hurt performance.

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.