Question 970
During a cloud security review, the operations team observes: Kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job. Which underlying control gap is responsible for the issue?
Explanation
Correct Answer
The described technical condition is: Cluster authorization is not aligned with identity-based RBAC and separation of duties. The appropriate corrective action is: Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope. Confirm with: Developers perform only authorized namespace tasks and cluster-admin operations require eligible roles.
Incorrect Answers
Backup recovery becomes fragile without appropriate soft delete, immutability and authorization protection in the vault. “Enable supported vault soft delete and enhanced protection settings including immutable backup where required” would address that alternative cause, not the condition in this question: cluster authorization is not aligned with identity-based RBAC and separation of duties.
“Deploy or configure an eligible private AKS cluster and connect operators over approved private network paths” responds to this separate finding: the cluster uses a public API server endpoint rather than a supported private AKS cluster design. This question instead needs “Integrate AKS with Microsoft Entra authentication and configure appropriate Kubernetes or Azure RBAC scope”, so the alternative does not meet the stated condition.
The workload does not use supported AKS workload identity federation or least-privilege managed identity authorization. “Configure workload identity on the service account and scoped access to the target Key Vault” applies to that separate problem. The observed case is kubernetes cluster credentials are shared among administrators, and a developer can change privileged cluster resources beyond their job; choosing this alternative would address the wrong failure mode.