Question 340
An Azure SQL operations team investigates: A reporting identity changes session context and unexpectedly sees rows from an unrelated tenant. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A reporting identity changes session context and unexpectedly sees rows from an unrelated tenant.) is: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records. It directly tests whether the remediation (Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A reporting identity changes session context and unexpectedly sees rows from an unrelated tenant. The specific supported administrative response is: Implement row-level security using supported predicate functions and security policies tied to verified tenant or user context. The technical risk is: Filtering tenant data only in application code can leak rows through other SQL query paths or reporting tools. Confirm the correction with: Cross-tenant test queries are filtered at the SQL engine, while each approved tenant sees its own records.
Incorrect Answers
Database object ownership and schema authorization (2.1) addresses another technical failure: Granting broad table permissions for a narrow reporting requirement can expose unrelated sensitive objects. This case instead tests Row-level security with session predicates (2.3); the choice measures or changes another part of the system.
Sensitive data classification and discovery (2.3) addresses another technical failure: Unclassified personal or payment data may be exposed through poorly scoped reporting or overlooked control decisions. The required paired action and test concerns Row-level security with session predicates (2.3); a passing result for this alternative could leave that requirement unresolved.
Least-privilege database roles and grants (2.1) would demonstrate or implement: A permission check proves only the intended schema or table actions succeed for the dedicated workload identity. The paired-answer requirement concerns Row-level security with session predicates (2.3); this alternative does not provide the matching intervention and separate acceptance evidence.