← SAA-C03·Amazon Web Services

Question 272 of 1,040

Design Resilient Architectures →mediumMultiple SelectObjective-mapped

Quick Answer

The answer is to use the RDS endpoint rather than a hard-coded IP and to implement retry logic with exponential backoff. The RDS endpoint is a DNS name that automatically resolves to the current writer instance’s IP address; during a Multi-AZ failover, the DNS record updates to point to the new primary, so relying on the endpoint ensures the application reconnects without manual intervention. Adding retry logic with exponential backoff handles transient failures during DNS resolution and connection establishment, which occur when the DNS TTL has not yet expired after a failover. On the SAA-C03 exam, this tests your understanding of how DNS-based endpoints and application-layer resilience patterns work together—a common trap is assuming the application will reconnect automatically without retry logic or using a static IP. Remember the mnemonic: “Endpoint for direction, retry for protection.”

SAA-C03 Design Resilient Architectures Practice Question

This SAA-C03 practice question tests your understanding of design resilient architectures. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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.

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 →

A
Cache and reconnect to the current writer IP address to avoid DNS lookups during failover.
Why wrong: 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
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
Switch to a read replica and let it promote manually after every outage.
Why wrong: 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
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
Disable connection pooling so each request opens a fresh socket during normal operation.
Why wrong: 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.

Full breakdown with real-world context →

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 RDS endpoint name instead of hard-coding the current instance IP or hostname in the application.

Option B is correct because the RDS endpoint is a DNS name that automatically resolves to the current writer instance's IP address. During a failover, the DNS record is updated to point to the new primary, so using the endpoint instead of a hard-coded IP or hostname allows the application to reconnect without manual intervention. Option D is correct because adding retry logic with exponential backoff handles transient failures during DNS resolution and connection establishment, which are common during the brief period when the DNS TTL has not yet expired after a failover.

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.

✗
Cache and reconnect to the current writer IP address to avoid DNS lookups during failover.
Why it's wrong here
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.
✓
Use the RDS endpoint name instead of hard-coding the current instance IP or hostname in the application.
Why this is correct
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.
Related concept
Read the scenario before looking for a memorised answer.
✗
Switch to a read replica and let it promote manually after every outage.
Why it's wrong here
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.
✓
Add retry logic with exponential backoff for transient connection and DNS resolution errors.
Why this is correct
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.
Related concept
Read the scenario before looking for a memorised answer.
✗
Disable connection pooling so each request opens a fresh socket during normal operation.
Why it's wrong here
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 traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often think caching the IP (Option A) improves performance, but it actually breaks failover resilience because the application never learns the new writer's address after a failover.

Detailed technical explanation

How to think about this question

Under the hood, RDS Multi-AZ uses a synchronous standby replica in a different Availability Zone, and failover typically completes within 60–120 seconds. During this time, the DNS record for the RDS endpoint is updated with a TTL of 5 seconds (default for RDS), but client-side DNS caches may still hold the old IP. Retry logic with exponential backoff (e.g., starting at 100 ms and doubling up to a few seconds) allows the application to survive this window. In real-world scenarios, applications using connection pools like HikariCP or DBCP must also configure connection validation queries (e.g., SELECT 1) to detect stale connections and trigger reconnects.

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.

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.

10 questions 20 questions 30 questions 50 questions Timed 30

SAA-C03 practice-test guide →Study guide →Browse all practice tests

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 RDS endpoint name instead of hard-coding the current instance IP or hostname in the application. — Option B is correct because the RDS endpoint is a DNS name that automatically resolves to the current writer instance's IP address. During a failover, the DNS record is updated to point to the new primary, so using the endpoint instead of a hard-coded IP or hostname allows the application to reconnect without manual intervention. Option D is correct because adding retry logic with exponential backoff handles transient failures during DNS resolution and connection establishment, which are common during the brief period when the DNS TTL has not yet expired after a failover.

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.

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 →

How Courseiva writes practice questions · Editorial policy

Same concept, more angles

1 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 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?

easy

A.Hard-code the new writer instance IP address after failover completes.
✓ B.Keep using the same RDS endpoint and implement connection retry logic on failures.
C.Disable Multi-AZ and rely on manual intervention to switch endpoints.
D.Move reads to application-side caching only, and avoid reopening DB connections.

Why B: Option B is correct because the RDS Multi-AZ DNS endpoint remains unchanged during a failover, automatically pointing to the new writer instance. Implementing connection retry logic with exponential backoff allows the application to handle the brief DNS propagation delay and connection interruption, ensuring reliable recovery without manual intervention.

Keep practising

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.

Loading comments…

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.