Question 470
A regulated Azure tenant has this security condition: A security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events. What governance practice would best prevent the same failure?
Explanation
Correct Answer
This guardrail addresses azure sql auditing destination configuration: Azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination. The prevention measure is: Test audit data delivery and access controls after SQL platform and diagnostic changes. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
TLS encrypts data in transit and does not replace database storage encryption provided by Transparent Data Encryption. “Audit TDE status and key rotation separately from transport TLS compliance” would address that alternative cause, not the condition in this question: azure SQL auditing has not been enabled or delivered to an appropriate storage or Log Analytics destination.
“Review client-driver support, key custody and query limitations before Always Encrypted rollout” responds to this separate finding: tDE protects at-rest data, but it does not keep selected columns secret from privileged database query processing. This question instead needs “Test audit data delivery and access controls after SQL platform and diagnostic changes”, so the alternative does not meet the stated condition.
The SQL service lacks the intended Private Endpoint/DNS configuration and public network access restriction. “Validate SQL private connectivity and public network restrictions during application onboarding” applies to that separate problem. The observed case is a security team needs to investigate who changed a sensitive database table last week but finds SQL auditing never exported any relevant events; choosing this alternative would address the wrong failure mode.