Question 210
In this retired AZ-500 educational case, An AKS workload relies on a node-wide managed identity even though each namespace requires distinct Key Vault access. Which security principle BEST explains the appropriate response?
Explanation
Correct Answer
The relevant security principle is: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. That is why the action is: Configure a supported workload identity or appropriately scoped identity model for the pod's resource needs. The directly relevant confirmation is: A test pod retrieves only its designated vault secret and another namespace is denied.
Incorrect Answers
The offered principle describes: PIM eligibility separates just-in-time activation from long-lived active privileges. The situation in this question instead depends on: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. These are different technical conditions.
“RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs” reflects the mechanism: RBAC role permissions inherit through scope and Owner can delegate access beyond deployment needs. The actual reported symptoms are better explained by: Shared host-level identity can overgrant workloads that should have separate authorization boundaries.
The offered principle describes: PIM role settings can enforce approval and other activation requirements per scope. The situation in this question instead depends on: Shared host-level identity can overgrant workloads that should have separate authorization boundaries. These are different technical conditions.