Question 210
An Azure SQL operations team investigates: A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities. Select TWO complementary answers: the targeted corrective action AND the evidence that verifies it.
Explanation
Correct Answers
The acceptance evidence for this incident (A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities.) is: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source. It directly tests whether the remediation (Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions.) solves the specified issue, instead of proving an unrelated database control works.
The reported Azure SQL or SQL Server condition is: A platform team rotates a shared SQL credential and inadvertently breaks dozens of instances that could use managed identities. The specific supported administrative response is: Use a supported managed identity or Entra-based service principal for application authentication to Azure SQL with database-level permissions. The technical risk is: Embedded long-lived SQL passwords in configuration files are easily copied and difficult to rotate safely. Confirm the correction with: The workload obtains a supported short-lived token and accesses only allowed SQL objects with no reusable password in source.
Incorrect Answers
Sensitive data classification and discovery (2.3) would demonstrate or implement: The classification inventory identifies sensitive columns and its labels match approved data handling requirements. This case instead tests Managed identity database access (2.1); the choice measures or changes another part of the system.
Microsoft entra administrator for azure SQL (2.1) addresses another technical failure: Without correct tenant mapping and directory administration, intended Entra accounts cannot be provisioned for database access. The required paired action and test concerns Managed identity database access (2.1); a passing result for this alternative could leave that requirement unresolved.
SQL encrypted connections and TLS verification (2.2) addresses another technical failure: Unvalidated or unencrypted database transport can expose credentials or data to interception and server impersonation. The paired-answer requirement concerns Managed identity database access (2.1); this alternative does not provide the matching intervention and separate acceptance evidence.