Question 320
An Azure SQL operations team investigates: An audit needs consistent data labels before configuring role-based masking and export restrictions. 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: An audit needs consistent data labels before configuring role-based masking and export restrictions. The specific supported administrative response is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners. The technical risk is: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. Confirm the correction with: The classification inventory identifies sensitive columns and its labels match approved data handling requirements.
The acceptance evidence for this incident (An audit needs consistent data labels before configuring role-based masking and export restrictions.) is: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. It directly tests whether the remediation (Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
Azure SQL firewall rule scoping (2.2) would demonstrate or implement: Approved source clients can connect through expected network paths and unauthorized test addresses are rejected. The case states: An audit needs consistent data labels before configuring role-based masking and export restrictions. The most direct paired action and test is: Apply supported sensitivity labels and classifications to SQL columns and review the discovered metadata with data owners.
Always encrypted column confidentiality (2.2) addresses another technical failure: TDE alone leaves values visible to SQL administrators or query-processing paths, whereas client-side column encryption changes query support. This choice can be useful for that problem, but it does not establish the Sensitive data classification and discovery (2.3) control being assessed here.
Row-level security with session predicates (2.3) addresses another technical failure: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. The required paired action and test concerns Sensitive data classification and discovery (2.3); a passing result for this alternative could leave that requirement unresolved.