Question 750
The cloud operations team reviews the following risk: A highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption. Which configuration change most directly resolves this problem?
Explanation
Correct Answer
The cause is: Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory. The appropriate change is: Choose supported confidential VM features and configure the correct security type and encryption settings. Verify it with this outcome: A test VM reports the intended confidential security posture and protected boot chain.
Incorrect Answers
This action concerns azure disk encryption key vault dependency, where Azure Disk Encryption relies on accessible encryption artifacts and authorized Key Vault configuration for the protected disk. The reported incident instead involves Disk encryption at rest does not itself provide confidential-computing protection for in-use guest memory.
This action concerns azure bastion without public vm ip, where Direct public VM management endpoints expand attack surface when Azure Bastion can broker protected administrative connections. The corrective response here is “Choose supported confidential VM features and configure the correct security type and encryption settings”; this alternative does not provide that response.
This action concerns disk customer managed key disk encryption set, where Azure managed disk customer-managed encryption requires a supported Disk Encryption Set with a key and proper identity access. The stem reports a highly sensitive VM workload requires protecting guest memory and boot state, but the design uses only ordinary managed disk encryption; this control addresses a different failure condition.