Question 840
The cloud operations team reviews the following risk: A team assigns the same Azure resource role individually to dozens of analysts, then former team members retain access when the department changes. Which explanation fits the observed symptoms most closely?
Explanation
Correct Answer
The described technical condition is: Direct per-user role assignments can persist after personnel changes without a managed membership lifecycle. The appropriate corrective action is: Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls. Confirm with: Removing a user from the group removes inherited resource access after propagation, without changing role assignments.
Incorrect Answers
The multi-tenant application needs a service principal representation in the consuming tenant for assignments and policy. “Provision or consent the enterprise application service principal and configure appropriate access and controls” would address that alternative cause, not the condition in this question: direct per-user role assignments can persist after personnel changes without a managed membership lifecycle.
“Configure the PIM role activation requirements to demand the approved strong authentication method” responds to this separate finding: pIM role settings have not required the intended multifactor or authentication-strength control at activation. This question instead needs “Assign the correct Azure RBAC role to a governed Entra security group and manage group membership through joiner-leaver controls”, so the alternative does not meet the stated condition.
A broad blob data role without a suitable Azure RBAC condition can grant more write scope than the application requires. “Apply an appropriate supported Azure role assignment condition or narrower scope to restrict eligible blob operations” applies to that separate problem. The observed case is a team assigns the same Azure resource role individually to dozens of analysts, then former team members retain access when the department changes; choosing this alternative would address the wrong failure mode.