Question 570
A platform security assessment reveals this issue: An AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current. What is the most appropriate corrective step?
Explanation
Correct Answer
The cause is: Control-plane version compliance is distinct from node OS image and node pool security patch state. The appropriate change is: Schedule supported AKS node image updates and verify rollout health across node pools. Verify it with this outcome: The node pools report patched images and workloads continue meeting availability requirements.
Incorrect Answers
This action concerns container apps secret references, where Sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. The reported incident instead involves Control-plane version compliance is distinct from node OS image and node pool security patch state.
This action concerns azure policy admission for aks, where Cluster admission policies are not aligned with Azure Policy for Kubernetes or an equivalent approved governance control. The corrective response here is “Schedule supported AKS node image updates and verify rollout health across node pools”; this alternative does not provide that response.
This action concerns container apps managed identity auth, where The Container App does not use an attached managed identity with the correct Key Vault data-plane permission. The stem reports an AKS cluster continues running an outdated node OS image with vulnerabilities even though the Kubernetes control plane version is current; this control addresses a different failure condition.