Reference:
https://docs.microsoft.com/en-us/sql/relational-databases/system-dynamic-management-views/sys-dm-exec- query-plan-stats-transact-sql?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 C is Correct: Run sys.dm_exec_query_plan_stats. 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. This fits the case because the requested outcome is: You need to gather the last execution of a query plan and its runtime statistics. The selected feature addresses that outcome directly rather than relying on a workaround.
Why A is Wrong: Generate an estimated execution plan. 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 B is Wrong: Generate an actual execution plan. 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 would produce a different operational signal than the one needed to investigate, alert, or tune the workload in this question.
Why D is Wrong: Generate Live Query Statistics. 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.