Home » Microsoft » DP-200 v.2 » How should you monitor SALESDB to meet the technical requirements?
How should you monitor SALESDB to meet the technical requirements?
A. Query the sys.resource_stats dynamic management view.
B. Review the Query Performance Insights for SALESDB.
C. Query the sys.dm_os_wait_stats dynamic management view.
D. Review the auditing information of SALESDB.
Correct Answer: A
Explanation/Reference:
Explanation:
Scenario: Disk IO, CPU, and memory usage must be monitored for SALESDB The sys.resource_stats returns historical data for CPU, IO, DTU consumption. There’s one row every 5 minute for a database in an Azure logical SQL Server if there’s a change in the metrics.
Incorrect Answers:
B: Query Performance Insight helps you to quickly identify what your longest running queries are, how they change over time, and what waits are affecting them.
C: sys.dm_os_wait_stats: specific types of wait times during query execution can indicate bottlenecks or stall points within the query. Similarly, high wait times, or wait counts server wide can indicate bottlenecks or hot spots in interaction query interactions within the server instance. For example, lock waits indicate data contention by queries; page IO latch waits indicate slow IO response times; page latch update waits indicate incorrect file layout.
References:
https://dataplatformlabs.com/monitoring-azure-sql-database-with-sys-resource_stats/
