Practice Exam

Explanations for each answer:

• Query activity is correct. Query activity provides a one-stop view of all running and historical T-SQL queries without requiring you to write any T-SQL code. It shows query runs from the past 30 days and includes the username of users who submitted queries, query statements, execution status (running, succeeded, canceled, failed), and timing information. You can access Query activity by selecting the warehouse's More Options (...) menu or from the query editor ribbon. Note that you must be an admin in your workspace to access Query activity.
• The Microsoft Fabric Capacity Metrics app is incorrect. The Microsoft Fabric Capacity Metrics app monitors capacity consumption, throttling, and resource utilization across Fabric workloads at the capacity level. It focuses on Capacity Unit (CU) consumption and performance metrics, not individual query details like usernames and query statements. It doesn't provide query-level monitoring with user information.
• The sys.dm_exec_requests dynamic management view is incorrect. The sys.dm_exec_requests DMV shows information about currently running requests in real-time, but it doesn't maintain a historical record of queries from the past 60 minutes. It only shows active queries that are currently executing. Additionally, while it can show session information, you would need to join it with sys.dm_exec_sessions to get usernames, making it more complex than Query activity.
• Views from the queryinsights schema is incorrect. While the queryinsights schema views (like exec_requests_history) do contain historical query information including usernames and query text, they require writing T-SQL queries to retrieve and filter the data. Query activity provides the same information through a graphical interface without requiring code, making it more efficient for this monitoring task.