The answer is to use sys.dm_exec_query_stats to identify queries with high wait statistics. This dynamic management view aggregates query performance data with minimal overhead, making it the ideal first step when you need to troubleshoot intermittent query timeouts in Azure SQL Database without impacting production workloads. High wait statistics directly reveal resource contention—such as CPU, I/O, or blocking—that often causes sporadic timeouts, whereas other diagnostic tools like Query Store require prior configuration or add unnecessary load. On the Microsoft Azure Database Administrator Associate DP-300 exam, this question tests your ability to choose the least intrusive diagnostic method first; a common trap is jumping to scaling up the General Purpose tier or enabling automatic tuning, which are reactive fixes rather than root-cause analysis. Remember the memory tip: “Stats first, scale last”—always check wait stats before changing resources.
DP-300 Practice Question: Monitor, configure, and optimize database resources
This DP-300 practice question tests your understanding of monitor, configure, and optimize database resources. 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.
You are monitoring a critical production Azure SQL Database that is experiencing intermittent query timeouts. The database is configured with the General Purpose service tier. You need to identify the root cause of the timeouts with minimal overhead. What should you review first?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "first"
Why it matters: Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use sys.dm_exec_query_stats to identify queries with high wait statistics.
Option A is correct because sys.dm_exec_query_stats provides aggregated query performance data without adding significant overhead, and high wait stats often point to resource contention. Option B is wrong because Query Store insights require Query Store to be enabled and may not be the first step. Option C is wrong because automatic tuning recommendations are for optimization, not troubleshooting. Option D is wrong because scaling up is a reactive measure, not a diagnostic step.
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.
✗
Implement automatic tuning to force plan regression fixes.
Why it's wrong here
Automatic tuning optimizes performance but does not diagnose root cause.
✗
Increase the database service tier to Business Critical.
Why it's wrong here
Scaling up is a costly reactive step, not a diagnostic action.
✓
Use sys.dm_exec_query_stats to identify queries with high wait statistics.
Why this is correct
Low-overhead way to find problematic queries and their wait types.
Clue confirmation
The clue word "first" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Enable Query Store and review the Regressed Queries report.
Why it's wrong here
Query Store is useful but requires prior enablement; not the first step with minimal overhead.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Identify which DP-300 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.
Monitor, configure, and optimize database resources — This question tests Monitor, configure, and optimize database resources — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use sys.dm_exec_query_stats to identify queries with high wait statistics. — Option A is correct because sys.dm_exec_query_stats provides aggregated query performance data without adding significant overhead, and high wait stats often point to resource contention. Option B is wrong because Query Store insights require Query Store to be enabled and may not be the first step. Option C is wrong because automatic tuning recommendations are for optimization, not troubleshooting. Option D is wrong because scaling up is a reactive measure, not a diagnostic step.
What should I do if I get this DP-300 question wrong?
Identify which DP-300 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.
Are there clue words in this question I should notice?
Yes — watch for: "first". Order matters here. You are being tested on which action comes before the others — not which action is generally useful.
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 →
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.
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.
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.