Question 150
The cloud operations team reviews the following risk: A pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure. Which configuration change most directly resolves this problem?
Explanation
Correct Answer
The cause is: The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. The appropriate change is: Configure workload identity on the service account and scoped access to the target Key Vault. Verify it with this outcome: The pod obtains a short-lived token and reads only the approved secret without stored client secrets.
Incorrect Answers
This action concerns aks microsoft entra and kubernetes rbac, where Cluster authorization is not aligned with identity-based RBAC and separation of duties. The reported incident instead involves The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization.
This action concerns aks pod network policy isolation, where Namespace boundaries alone do not enforce pod network isolation without a supported policy engine and rules. The corrective response here is “Configure workload identity on the service account and scoped access to the target Key Vault”; this alternative does not provide that response.
This action concerns ephemeral disk data handling, where Ephemeral operating system disks and temporary storage are not designed as durable protected secret repositories. The stem reports a pod must read a Key Vault secret but uses a copied service principal secret in a Kubernetes Secret, increasing credential exposure; this control addresses a different failure condition.