DP-300 Practice Question: Monitor, configure, and optimize database resources
You manage an Azure SQL Database that supports a reporting workload. Users report that a complex aggregation query returns different elapsed times throughout the day, but the logical reads remain consistent. You need to determine whether the query is experiencing CPU pressure or waiting on resources. Which Query Store view should you use to analyze wait statistics for the query?
⚠ Common exam trap
The trap here is assuming that runtime statistics alone can reveal wait types, when in fact wait categories are stored separately in the wait stats view.
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
✓
sys.query_store_wait_stats
To analyze wait statistics for a specific query in Query Store, you must use the sys.query_store_wait_stats view. It aggregates wait times by query and plan, allowing you to see the wait categories and durations. This directly addresses the need to differentiate between CPU pressure and resource waits. The other views provide runtime stats, plan details, or query text, but none include wait information.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
sys.query_store_plan
Why it's wrong here
This view contains information about the execution plans associated with queries, such as the plan handle and whether the plan is forced. It does not include wait statistics or runtime performance metrics. While it is useful for identifying plan changes, it cannot help you analyze wait types or determine if the query is waiting on resources.
- ✗
sys.query_store_runtime_stats
Why it's wrong here
This view provides runtime execution statistics such as duration, CPU time, and logical reads, but it does not include wait categories or wait times. It can indicate that a query is slow, but it cannot tell you whether the query is waiting on CPU, I/O, or locks. Therefore, it cannot directly answer whether the query is experiencing CPU pressure or waiting on resources.
- ✗
sys.query_store_query_text
Why it's wrong here
This view stores the text of queries captured by Query Store. It is used to retrieve the actual T-SQL statements, but it does not contain any performance or wait-related data. It cannot provide insight into whether the query is experiencing CPU pressure or waiting on resources, so it is not the appropriate choice.
- ✓
sys.query_store_wait_stats
Why this is correct
This view captures wait statistics aggregated by query and plan, including wait categories and total wait time. It shows whether the query is waiting on CPU, I/O, locks, or other resources. Since the user needs to distinguish CPU pressure from resource waits, this is the correct source. It provides the necessary wait data to make that determination.
Go deeper
Related to this question
Learn chapter
Optimizing Database Query and Index Performance
Key term
Query Store
Query Store is a built-in SQL Server feature that captures and stores a history of query execution plans and performance data for easy monitoring and troubleshooting.
Key term
Azure SQL Performance Tuning
Azure SQL Performance Tuning is the process of optimizing the speed and efficiency of queries and database operations in Microsoft Azure SQL Database or SQL Managed Instance to reduce latency and improve throughput.
About these practice questions
Courseiva writes every DP-300 question from scratch — 574 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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.