DP-300 Practice Question: Monitor, configure, and optimize database resources
You manage an Azure SQL Database that is critical for a financial application. The database has a read-heavy workload, and you need to monitor and diagnose performance issues. You want to enable a feature that automatically captures detailed information about query plans and runtime statistics for later analysis. Which feature should you enable?
⚠ Common exam trap
It's easy for candidates to confuse automatic tuning with Query Store; automatic tuning depends on Query Store but does not itself capture the detailed performance data.
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
✓
Query Store
Query Store is the built-in feature that automatically captures query plans and runtime statistics, storing them in the database for historical analysis. It is designed for performance troubleshooting and is a prerequisite for automatic tuning. For a read-heavy workload, it provides the necessary insights to identify and resolve performance regressions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Extended Events
Why it's wrong here
Extended Events is a lightweight tracing system that can capture detailed query execution events, but it requires manual session setup and management. It does not automatically capture and retain query plans and runtime statistics in a queryable format like Query Store does, making it less convenient for ongoing performance monitoring.
- ✓
Query Store
Why this is correct
Query Store captures query plans and runtime execution statistics automatically, persisting them in the user database. It provides historical data on query performance, enabling you to identify regressions, analyze plan changes, and force plans. For a read-heavy workload, Query Store is essential for diagnosing issues without manual tracing.
- ✗
Automatic tuning
Why it's wrong here
Automatic tuning uses Query Store data to create and drop indexes and force plans, but it does not itself capture detailed query plans and runtime statistics. It relies on Query Store to be enabled. Therefore, enabling automatic tuning alone will not provide the raw diagnostic data needed for deep analysis.
- ✗
Dynamic management views (DMVs)
Why it's wrong here
DMVs provide real-time information about current query execution and system health, but they do not persist historical data. Once the query completes or the server restarts, the information is lost. For historical analysis and trend identification, a persistent store like Query Store is required.
Visual reference
Go deeper
Related to this question
Learn chapter
Optimizing Database Query and Index Performance
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.
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.
About these practice questions
This DP-300 question is part of Courseiva's 574-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam 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.