Question 850
While validating an Azure workload, the security team finds: A team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged. Which outcome most clearly verifies that the issue is resolved?
Explanation
Correct Answer
This validates the specific control for ephemeral disk data handling: Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The associated corrective action is: Move credentials into a managed secrets service and use approved persistent data storage where needed. Testing a different component would not establish this result.
Incorrect Answers
Shared password authentication lacks the intended identity and cryptographic protections for privileged SSH management. “Use controlled SSH public-key authentication and restrict access through Bastion or approved private management” would address that alternative cause, not the condition in this question: ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories.
“Enable appropriate Defender or approved image scanning and enforce risk-based vulnerable-image remediation” responds to this separate finding: authentication to a container registry does not establish that deployed images meet vulnerability security requirements. This question instead needs “Move credentials into a managed secrets service and use approved persistent data storage where needed”, so the alternative does not meet the stated condition.
Cluster authorization is not aligned with identity-based RBAC and separation of duties. “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope” applies to that separate problem. The observed case is a team stores long-lived secrets on a VM's temporary OS disk, then assumes the data will survive reimaging and migrate unchanged; choosing this alternative would address the wrong failure mode.