Question 780
A platform security assessment reveals this issue: An AKS project relies on a deprecated pod-identity approach, and a newer cluster deployment fails to authenticate pods to Azure resources. Which operating control most directly reduces this recurring risk?
Explanation
Correct Answer
This guardrail addresses aks legacy pod identity migration: The workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model. The prevention measure is: Track identity integration feature lifecycle before Kubernetes version upgrades. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
Sensitive values are placed in plain configuration rather than secure parameters or supported protected secret references. “Scan container deployment manifests and logs for accidentally exposed credentials” would address that alternative cause, not the condition in this question: the workload identity integration uses an older unsupported pattern rather than the supported federated workload identity model.
“Review app revision changes for insecure arguments and secret-reference drift” responds to this separate finding: sensitive credentials are stored in ordinary configuration instead of supported Container Apps secrets or identity. This question instead needs “Track identity integration feature lifecycle before Kubernetes version upgrades”, so the alternative does not meet the stated condition.
The container group relies on a long-lived shared credential rather than supported managed identity authorization. “Review environment variables and container logging for unintended credential exposure” applies to that separate problem. The observed case is an AKS project relies on a deprecated pod-identity approach, and a newer cluster deployment fails to authenticate pods to Azure resources; choosing this alternative would address the wrong failure mode.