- A
FailoverTime
Why wrong: FailoverTime is not a real CloudWatch metric for RDS. The actual metric is 'Failover' (a count), not a duration metric, so it cannot be used to measure failover time.
- B
WriteLatency
Why wrong: WriteLatency measures the average latency of write operations. While it may spike during a failover, it does not directly indicate the duration of downtime.
- C
DatabaseConnections
DatabaseConnections reflects the number of active connections. During a failover, connections are lost and then re-established. The period of low or zero connections approximates the failover duration, making it the best metric among the options.
- D
ReplicaLag
Why wrong: ReplicaLag is used for read replicas to measure the delay between the primary and a replica. For Multi-AZ, the standby is synchronous and no ReplicaLag metric is available; it is not relevant for failover duration.
DBS-C01 Monitoring and Troubleshooting Practice Question
This DBS-C01 practice question tests your understanding of monitoring and troubleshooting. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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 uses Amazon RDS for SQL Server with Multi-AZ deployment. During a failover test, the application experienced a longer downtime than expected. Which monitoring metric should be reviewed to understand the failover duration?
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
DatabaseConnections
The DatabaseConnections metric in Amazon CloudWatch tracks the number of active database connections. During a Multi-AZ failover, existing connections are dropped and new connections are blocked until the standby becomes the primary. By monitoring the time period when DatabaseConnections drops to zero or a low value, you can estimate the failover duration. Options A (FailoverTime) is not a valid CloudWatch metric for RDS; the actual metric is 'Failover' which is a count, not a duration. WriteLatency may increase during failover but does not directly measure downtime. ReplicaLag applies to read replicas, not Multi-AZ 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.
- ✗
FailoverTime
Why it's wrong here
FailoverTime is not a real CloudWatch metric for RDS. The actual metric is 'Failover' (a count), not a duration metric, so it cannot be used to measure failover time.
- ✗
WriteLatency
Why it's wrong here
WriteLatency measures the average latency of write operations. While it may spike during a failover, it does not directly indicate the duration of downtime.
- ✓
DatabaseConnections
Why this is correct
DatabaseConnections reflects the number of active connections. During a failover, connections are lost and then re-established. The period of low or zero connections approximates the failover duration, making it the best metric among the options.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
ReplicaLag
Why it's wrong here
ReplicaLag is used for read replicas to measure the delay between the primary and a replica. For Multi-AZ, the standby is synchronous and no ReplicaLag metric is available; it is not relevant for failover duration.
Common exam traps
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.
Detailed technical explanation
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.
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 DBS-C01 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
- →
Monitoring and Troubleshooting — study guide chapter
Learn the concepts, then practise the questions
- →
Monitoring and Troubleshooting practice questions
Targeted practice on this topic area only
- →
All DBS-C01 questions
1,730 questions across all exam domains
- →
AWS Certified Database Specialty DBS-C01 study guide
Full concept coverage aligned to exam objectives
- →
DBS-C01 practice test guide
How to use practice tests most effectively before exam day
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.
Workload-Specific Database Design practice questions
Practise DBS-C01 questions linked to Workload-Specific Database Design.
Deployment and Migration practice questions
Practise DBS-C01 questions linked to Deployment and Migration.
Management and Operations practice questions
Practise DBS-C01 questions linked to Management and Operations.
Monitoring and Troubleshooting practice questions
Practise DBS-C01 questions linked to Monitoring and Troubleshooting.
Database Security practice questions
Practise DBS-C01 questions linked to Database Security.
DBS-C01 fundamentals practice questions
Practise DBS-C01 questions linked to DBS-C01 fundamentals.
DBS-C01 scenario practice questions
Practise DBS-C01 questions linked to DBS-C01 scenario.
DBS-C01 troubleshooting practice questions
Practise DBS-C01 questions linked to DBS-C01 troubleshooting.
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?
Monitoring and Troubleshooting — This question tests Monitoring and Troubleshooting — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: DatabaseConnections — The DatabaseConnections metric in Amazon CloudWatch tracks the number of active database connections. During a Multi-AZ failover, existing connections are dropped and new connections are blocked until the standby becomes the primary. By monitoring the time period when DatabaseConnections drops to zero or a low value, you can estimate the failover duration. Options A (FailoverTime) is not a valid CloudWatch metric for RDS; the actual metric is 'Failover' which is a count, not a duration. WriteLatency may increase during failover but does not directly measure downtime. ReplicaLag applies to read replicas, not Multi-AZ failover.
What should I do if I get this DBS-C01 question wrong?
Identify which DBS-C01 exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
Keep practising
More DBS-C01 practice questions
- A company is deploying a new application on Amazon RDS for PostgreSQL. The security policy requires that all data be enc…
- Match each AWS service to its primary purpose.
- A financial services company runs a production Amazon Aurora MySQL database cluster (1 writer, 2 readers) in us-east-1.…
- A company is designing a database for a global e-commerce platform that requires low-latency reads and writes from multi…
- A security auditor reviews the output of a DynamoDB table description command as shown in the exhibit. Which statement a…
- A company is migrating an on-premises Oracle database to Amazon RDS for Oracle. The database contains sensitive data tha…
Last reviewed: Jun 20, 2026
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.
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.
Sign in to join the discussion.