Question 560
Following the issue — A confidential VM workload requires protected disk key handling but engineers enable only ordinary Azure Disk Encryption. — the team takes this action: Select supported confidential VM disk encryption settings and required trusted-platform prerequisites. Which continuing safeguard BEST prevents the same control weakness from returning?
Explanation
Correct Answer
The recurring safeguard is: Review confidential compute compatibility whenever altering security type or disk images. This mitigates the control weakness because: Confidential computing offers specialized guest and disk protections beyond generic encryption modes. Keep the intervention, Select supported confidential VM disk encryption settings and required trusted-platform prerequisites., in the approved deployment, monitoring and change governance process.
Incorrect Answers
That review protects the control associated with: Dynamic data masking alters certain query results for nonprivileged users but does not encrypt underlying data. It does not directly prevent the stated recurrence, which concerns: Confidential computing offers specialized guest and disk protections beyond generic encryption modes. The appropriate guardrail is “Review confidential compute compatibility whenever altering security type or disk images”.
This safeguard is for the dependency described by: Application database reachability does not guarantee every telemetry or audit egress path. The continuing risk here is determined by: Confidential computing offers specialized guest and disk protections beyond generic encryption modes. The targeted safeguard is “Review confidential compute compatibility whenever altering security type or disk images”.
That review protects the control associated with: Azure Storage uses encryption at rest even when an organization has not configured its own CMK. It does not directly prevent the stated recurrence, which concerns: Confidential computing offers specialized guest and disk protections beyond generic encryption modes. The appropriate guardrail is “Review confidential compute compatibility whenever altering security type or disk images”.