Question 390
An Azure SQL operations team investigates: A preview-feature governance policy must be checked before installing a watcher in production. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The reported Azure SQL or SQL Server condition is: A preview-feature governance policy must be checked before installing a watcher in production. The specific supported administrative response is: Evaluate database watcher where available for supported detailed monitoring of Azure SQL databases, pools or managed instances, acknowledging its documented preview status. The technical risk is: Assuming a preview monitoring feature is generally available in every region or requires no permissions can break operational rollout. Confirm the correction with: A supported watcher collects expected SQL target telemetry into its configured store and the deployment is explicitly approved for preview use.
The acceptance evidence for this incident (A preview-feature governance policy must be checked before installing a watcher in production.) is: A supported watcher collects expected SQL target telemetry into its configured store and the deployment is explicitly approved for preview use. It directly tests whether the remediation (Evaluate database watcher where available for supported detailed monitoring of Azure SQL databases, pools or managed instances, acknowledging its documented preview status.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Deadlock detection and remediation (3.2) would demonstrate or implement: A concurrency test no longer produces the captured deadlock cycle and database correctness is preserved. The case states: A preview-feature governance policy must be checked before installing a watcher in production. The most direct paired action and test is: Evaluate database watcher where available for supported detailed monitoring of Azure SQL databases, pools or managed instances, acknowledging its documented preview status.
Database-scoped configuration controls (3.3) addresses another technical failure: Applying server-wide settings for one database's issue can unintentionally affect unrelated workloads. This choice can be useful for that problem, but it does not establish the Database watcher monitoring and preview status (3.1) control being assessed here.
SQL workload performance baselining (3.1) addresses another technical failure: Without a baseline, a slow-query complaint cannot be separated reliably from normal variability or a new regression. The paired-answer requirement concerns Database watcher monitoring and preview status (3.1); this alternative does not provide the matching intervention and separate acceptance evidence.