Question 420
The cloud operations team reviews the following risk: An automated report job has Storage Account Contributor but HTTP blob reads fail with authorization errors under Microsoft Entra tokens. What governance practice would best prevent the same failure?
Explanation
Correct Answer
This guardrail addresses blob storage data rbac: Management-plane storage Contributor does not necessarily include blob data read DataActions. The prevention measure is: Review data-plane RBAC separately from account administration roles for every application. A control in another subsystem would not prevent this specific recurrence.
Incorrect Answers
Data protection needs supported immutable blob retention or legal hold controls rather than role restrictions alone. “Test WORM retention enforcement and approved release procedures before storing regulated records” would address that alternative cause, not the condition in this question: management-plane storage Contributor does not necessarily include blob data read DataActions.
“Test customer-managed key rotation and access recovery before changing storage encryption configuration” responds to this separate finding: storage CMK encryption requires a supported Key Vault key and managed identity authorization for the account. This question instead needs “Review data-plane RBAC separately from account administration roles for every application”, so the alternative does not meet the stated condition.
Account-key-signed SAS tokens do not meet the intended user-delegation and identity-based security model. “Prefer user-delegation SAS for supported blob workflows and minimize delegation expiry” applies to that separate problem. The observed case is an automated report job has Storage Account Contributor but HTTP blob reads fail with authorization errors under Microsoft Entra tokens; choosing this alternative would address the wrong failure mode.