Question 140
While validating an Azure workload, the security team finds: A security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions. Which condition most directly explains the failure?
Explanation
Correct Answer
The described technical condition is: Per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used. The appropriate corrective action is: Assign the approved read-only role at a suitable management group with the intended child subscription coverage. Confirm with: The operator views security inventory in both existing and newly attached eligible subscriptions.
Incorrect Answers
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” would address that alternative cause, not the condition in this question: per-subscription assignments do not automatically cover future subscriptions unless an appropriate inherited scope is used.
“Correct the custom role Actions and NotActions for the required supported power operation, then save and test the assignment” responds to this separate finding: notActions subtracts permissions from the custom role definition and should not be confused with a globally enforced deny rule. This question instead needs “Assign the approved read-only role at a suitable management group with the intended child subscription coverage”, so the alternative does not meet the stated condition.
Azure resource management Actions do not necessarily include Blob Storage data-plane DataActions needed for OAuth blob access. “Assign Storage Blob Data Reader or another appropriate data role at the least required scope” applies to that separate problem. The observed case is a security reader needs consistent visibility across many subscriptions but receives separate assignments to each current subscription, missing newly created subscriptions; choosing this alternative would address the wrong failure mode.