Exam DP-300 topic 4 question 17 discussion

When you see "must minimize administrative effort", go to DMVs.

Use Query Store to find wait statistics for each query over time. In Query Store, wait types are combined into wait categories. You can find the mapping of wait categories to wait types in sys.query_store_wait_stats. https://learn.microsoft.com/en-us/azure/azure-sql/database/identify-query-performance-issues?view=azuresql

Chatgpt says: Correct Answer: C. Query Store 📌 Reason: It can detect the problematic query from the past, shows the execution plan and enables analysis with minimum effort.

In my opinion, Query Store requires less administrative effort. You can simply go to Regressed Queries or Top Resource Consuming Queries, view top queries and their execution plans, easily identify "bad" plans, force "good" plans. With DMV queries, often you would need to write or edit them yourself, and know how to interpret results.

It should be DMVs. DMVs have the least overhead administratively.

You can have dozens of databases in managed instance. It takes less effort to check DMV then query store of every single database.

When they say "must minimize administrative effort" you should use a tool to do the work.... DMV is a viable option, but requires operational and administrative work, Query store saves lots of work to do

I believe this is D: Dynamic Management Views, because you need to see the queries causing the performance issues right now, not the past. Whenever I have to handle a performance issue in real time, I'm grabbing the DMVs, not jumping into Query Store.

I'm not sure why people are brining up "null" jobs. The question only says Performance issues...

https://learn.microsoft.com/en-us/azure/azure-sql/managed-instance/monitoring-with-dmvs?view=azuresql

After some further research: Dynamic management views (DMVs) and dynamic management functions (DMFs) return server state information that can be used to monitor the health of a server instance, diagnose problems, and tune performance. https://learn.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/system-dynamic-management-views?view=sql-server-ver16

Status of the request. Can be one of the following values: background rollback running runnable sleeping suspended Not nullable. I believe it is D based on this Microsoft article: https://learn.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-exec-requests-transact-sql?view=sql-server-ver16

Yoy need to enable query store in managed instance so d is close..

on a second thought, it should be DMVs. query store saves information about queries that completed (successfully or timed out), not queries currently running and giving us headaches at the present moment.

Query Store > Regressed Queries.

The solution must minimize administrative effort

C is correct. D is incorrect, as Dynamic Management views does not store Execution Plan