Plan and configure a high availability and disaster recovery environment →hardMultiple ChoiceObjective-mapped
DP-300 Practice Question: Plan and configure a high availability and disaster recovery environment
Exhibit
Refer to the exhibit. The following is a Kusto query from Azure Monitor analyzing failover events: AzureDiagnostics | where ResourceProvider == "MICROSOFT.SQL" | where Category == "DatabaseWaitStatistics" | where wait_type == "FAILOVER_GROUP_WAIT" | summarize TotalWait = sum(wait_time_ms) by DatabaseName, bin(TimeGenerated, 1h) | where TotalWait > 100000 | project DatabaseName, TimeGenerated, TotalWait
You run the above Kusto query and see that a database named 'OrdersDB' has high wait times for 'FAILOVER_GROUP_WAIT' every hour. What does this indicate?
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
✓
Replication lag between primary and secondary is high
High wait times for 'FAILOVER_GROUP_WAIT' indicate significant replication lag between the primary and secondary databases, as this wait type measures the time the primary spends waiting for the secondary to apply changes. Option A is incorrect because the query does not measure connection requests. Option B is incorrect because write transactions may still occur; the wait is about replication, not transaction absence. Option C is incorrect because frequent automatic failovers are not indicated by this wait stat; it measures replication lag, not failover frequency.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
The secondary database is experiencing high connection requests
Why it's wrong here
This wait type is for replication, not for connections.
- ✗
The primary database is not receiving any write transactions
Why it's wrong here
High wait indicates replication is struggling, not that there are no writes.
- ✗
The failover group is experiencing frequent automatic failovers
Why it's wrong here
The wait type is for replication, not for failover itself.
- ✓
Replication lag between primary and secondary is high
Why this is correct
FAILOVER_GROUP_WAIT measures time spent waiting for replication to complete.
Go deeper
Related to this question
About these practice questions
Courseiva writes every DP-300 question from scratch — 906 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-300 practice question is part of Courseiva's free Microsoft 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 DP-300 exam.