Question 1,728 of 1,730
Management and OperationsmediumMultiple ChoiceObjective-mapped

DBS-C01 Management and Operations Practice Question

This DBS-C01 practice question tests your understanding of management and operations. 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.

A company is using Amazon RDS for MySQL with Multi-AZ deployment. The database experiences a failover event, and after failover, the application reports increased latency. Which action should the database specialist take to diagnose the issue?

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

Check Amazon CloudWatch metrics for Database Connections and Latency, and verify DNS resolution.

After a Multi-AZ failover, the DNS record for the RDS endpoint is updated to point to the new primary in a different Availability Zone. If the application's DNS cache still resolves to the old IP (which is now unreachable or in a different AZ), connections may time out or route suboptimally, increasing latency. Checking CloudWatch metrics for Database Connections and Latency helps isolate whether the issue is due to connection churn, resource contention, or DNS caching, while verifying DNS resolution confirms the application is connecting to the correct endpoint.

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.

  • Check Amazon CloudWatch metrics for Database Connections and Latency, and verify DNS resolution.

    Why this is correct

    Monitoring metrics and DNS can pinpoint the cause of increased latency.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Promote the secondary instance to primary manually.

    Why it's wrong here

    Multi-AZ failover is automatic; manual promotion is not needed.

  • Create a new read replica and redirect traffic.

    Why it's wrong here

    A read replica does not resolve the latency issue from DNS caching.

  • Force a reboot of the DB instance to reset connections.

    Why it's wrong here

    A reboot does not address DNS caching issues.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates assume increased latency after failover is always due to resource exhaustion or a need to reset connections, overlooking the common root cause of DNS caching and stale client connections routing to the wrong AZ.

Detailed technical explanation

How to think about this question

During a Multi-AZ failover, the standby instance is promoted to primary, but its buffer pool is initially cold, leading to increased read latency until the working set is cached. Additionally, the DNS TTL for the RDS endpoint is typically set to 30 seconds, but client-side DNS caching may exceed this, causing connections to the old IP to fail or be redirected across AZs, increasing network latency. CloudWatch's 'Database Connections' metric can reveal a spike in new connections as clients reconnect, while 'Read Latency' and 'Write Latency' metrics help differentiate between a cold buffer pool and network-induced delays.

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

An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.

Visual reference

Client Recursive Resolver Root DNS (13 root servers) TLD DNS (.com, .org, …) Authoritative example.com query IP addr answer

Quick reference

Common DNS Record Types

RecordPurposeExample
AIPv4 address mappingexample.com → 93.184.216.34
AAAAIPv6 address mappingexample.com → 2606:2800::1
CNAMEAlias to another hostnamewww → example.com
MXMail server for domainexample.com → mail.example.com (priority 10)
TXTText data (SPF, DKIM, verification)v=spf1 include:_spf.example.com ~all
NSAuthoritative name serversexample.com NS ns1.example.com
PTRReverse DNS (IP → hostname)34.216.184.93.in-addr.arpa → example.com
SOAZone authority recordPrimary NS, admin email, serial, TTL defaults

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 DBS-C01 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 DBS-C01 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 DBS-C01 question test?

Management and Operations — This question tests Management and Operations — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Check Amazon CloudWatch metrics for Database Connections and Latency, and verify DNS resolution. — After a Multi-AZ failover, the DNS record for the RDS endpoint is updated to point to the new primary in a different Availability Zone. If the application's DNS cache still resolves to the old IP (which is now unreachable or in a different AZ), connections may time out or route suboptimally, increasing latency. Checking CloudWatch metrics for Database Connections and Latency helps isolate whether the issue is due to connection churn, resource contention, or DNS caching, while verifying DNS resolution confirms the application is connecting to the correct endpoint.

What should I do if I get this DBS-C01 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 DBS-C01 practice questions

Last reviewed: Jul 4, 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 DBS-C01 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 DBS-C01 exam.