Question 250
An Azure SQL operations team investigates: An auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility. 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 auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility. The specific supported administrative response is: Configure supported customer-managed TDE protector keys in Azure Key Vault or Managed HSM with required identity permissions and key availability safeguards. The technical risk is: Key deletion or disabled access can render encrypted databases unavailable despite healthy compute and storage. Confirm the correction with: A rotation rehearsal validates the supported key version and the SQL resource retains access after planned key changes.
The acceptance evidence for this incident (An auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility.) is: A rotation rehearsal validates the supported key version and the SQL resource retains access after planned key changes. It directly tests whether the remediation (Configure supported customer-managed TDE protector keys in Azure Key Vault or Managed HSM with required identity permissions and key availability safeguards.) solves the specified issue, instead of proving an unrelated database control works.
Incorrect Answers
SQL authentication management on SQL server vms (2.1) addresses another technical failure: Poorly governed shared SQL logins are hard to rotate and can bypass centralized identity lifecycle management. The case states: An auditor wants evidence that a customer-managed encryption key can be rotated without losing database accessibility. The most direct paired action and test is: Configure supported customer-managed TDE protector keys in Azure Key Vault or Managed HSM with required identity permissions and key availability safeguards.
Azure SQL private endpoints and public exposure (2.2) addresses another technical failure: A created private endpoint without correct DNS resolution or network controls can still leave clients using public endpoints or unable to connect. This choice can be useful for that problem, but it does not establish the Customer-managed tde keys in azure key vault (2.2) control being assessed here.
Dynamic data masking limitations (2.3) would demonstrate or implement: Authorized privileged users see expected values and restricted users receive masked output under tested permissions. This case instead tests Customer-managed tde keys in azure key vault (2.2); the choice measures or changes another part of the system.