Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/performance/monitoring-performance-by-using-the- query-store?view=sql-server-ver15 Basic Concept: This question tests performance optimization for SQL workloads, including Query Store, automatic tuning, index/statistics maintenance, and engine-level resource behavior.
Why D is Correct: dynamic management views matches the expected DP-300 administration action. dynamic management views is related to operational monitoring or tuning, but it must match the exact signal needed:
query history, resource utilization, wait/blocking detail, or automatic remediation. The question is not asking for a general Azure capability; it is asking for the feature that produces this result: You need to identify which query is causing the issue and retrieve the execution plan for the query.
Why A is Wrong: the Azure portal is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It does not expose the required metric, query history, wait/blocking signal, or tuning mechanism; using it would not give the administrator the evidence requested.
Why B is Wrong: Extended Events is related to operational monitoring or tuning, but it must match the exact signal needed: query history, resource utilization, wait/blocking detail, or automatic remediation. It is useful in other troubleshooting paths, but this scenario requires a more specific monitoring or optimization feature.
Why C is Wrong: Query Store captures query text, plans, and runtime statistics, making it central for reviewing query history and troubleshooting plan regressions. It would produce a different operational signal than the one needed to investigate, alert, or tune the workload in this question.