Question 1,457 of 1,546
Reliability and Business ContinuitymediumMultiple ChoiceObjective-mapped

Quick Answer

The answer is to ensure the application retries or reconnects using the same DB instance endpoint. This is correct because RDS Multi-AZ failover automatically updates the DNS record for the endpoint to point to the new standby primary, so the application never needs a new connection string. The endpoint remains valid throughout the failover, and the application simply needs to handle transient connection loss by implementing retry logic. On the AWS Certified SysOps Administrator Associate SOA-C02 exam, this tests your understanding of how Multi-AZ abstracts infrastructure changes from the application, and a common trap is thinking you must manually update the endpoint or switch to a different DNS name. Remember the key principle: the endpoint is a static alias that always resolves to the current primary, so your application’s job is to reconnect, not reconfigure. A useful memory tip is “same endpoint, just retry”—the DNS does the heavy lifting, so your code only needs patience.

SOA-C02 Reliability and Business Continuity Practice Question

This SOA-C02 practice question tests your understanding of reliability and business continuity. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 RDS Multi-AZ DB instance fails over to the standby. The application uses the DB instance endpoint. What should the SysOps administrator usually do in the application after failover?

Question 1mediummultiple choice
Full question →

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

Ensure the application retries/reconnects using the same DB endpoint.

When an RDS Multi-AZ DB instance fails over to the standby, the DNS record for the DB instance endpoint is automatically updated to point to the new primary instance. The application should simply retry or reconnect using the same endpoint; no manual changes are needed because the endpoint remains valid. This is the standard behavior for Multi-AZ deployments, ensuring minimal disruption.

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.

  • Ensure the application retries/reconnects using the same DB endpoint.

    Why this is correct

    The endpoint remains the abstraction for the active database instance.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Manually change the application to the standby instance IP address.

    Why it's wrong here

    Applications should not depend on instance IP addresses for RDS Multi-AZ failover.

  • Restore from the latest snapshot before reconnecting.

    Why it's wrong here

    Multi-AZ failover does not normally require restoring from backup.

  • Create a new read replica and promote it immediately.

    Why it's wrong here

    That is not the standard response to a Multi-AZ failover.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates may think they need to manually update the connection string or IP address, but the DNS endpoint automatically resolves to the new primary after failover, so only retry logic is required.

Detailed technical explanation

How to think about this question

Under the hood, RDS Multi-AZ uses synchronous replication to the standby in a different Availability Zone. During failover, the DNS record's TTL (default 30 seconds) means the application must handle transient DNS propagation delays; retry logic with exponential backoff is recommended. In real-world scenarios, applications using connection pooling (e.g., with HikariCP) may need to configure validation queries or connection tests to detect stale connections after failover.

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 practice questions

Related SOA-C02 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free SOA-C02 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this SOA-C02 question test?

Reliability and Business Continuity — This question tests Reliability and Business Continuity — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Ensure the application retries/reconnects using the same DB endpoint. — When an RDS Multi-AZ DB instance fails over to the standby, the DNS record for the DB instance endpoint is automatically updated to point to the new primary instance. The application should simply retry or reconnect using the same endpoint; no manual changes are needed because the endpoint remains valid. This is the standard behavior for Multi-AZ deployments, ensuring minimal disruption.

What should I do if I get this SOA-C02 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

Keep practising

More SOA-C02 practice questions

Last reviewed: Jun 11, 2026

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…

Sign in to join the discussion.

This SOA-C02 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 SOA-C02 exam.