Question 210
A Microsoft Azure administrator receives this requirement: An audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions. What observation is the strongest validation evidence?
Explanation
Correct Answer
This validates the specific control for reader role versus resource modification: The Reader built-in role grants view operations but not Azure Resource Manager write operations on resources. The associated corrective action is: Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized. Testing a different component would not establish this result.
Incorrect Answers
PIM role settings have not required the intended multifactor or authentication-strength control at activation. “Configure the PIM role activation requirements to demand the approved strong authentication method” would address that alternative cause, not the condition in this question: the Reader built-in role grants view operations but not Azure Resource Manager write operations on resources.
“Assign the approved read-only role at a suitable management group with the intended child subscription coverage” responds to this separate finding: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. This question instead needs “Grant an appropriately scoped Contributor or narrower custom role when write tasks are actually authorized”, so the alternative does not meet the stated condition.
Azure RBAC assignments at a parent management group are inherited by resources at descendant scopes unless restricted. “Remove the broad inherited role assignment and grant the data role only at the intended container or storage scope” applies to that separate problem. The observed case is an audit operator can view a virtual machine but cannot change its tags after receiving the Reader built-in role at resource group scope, and the team assumes Reader includes write permissions; choosing this alternative would address the wrong failure mode.