Question 17 — AZ-104 Practice Exam 7
Your project teams need fine-grained access so members can read only the Azure Storage blobs for their own project. You also want the option to hide sensitive attributes (like “HourlySalary”) from non-admins. What approach best satisfies both needs? (Select one answer)
Define and assign custom security attributes to users/resources, and use attribute governance/filters to enforce project-scoped access
Grant all project members Storage Blob Data Contributor at the subscription scope
Create Microsoft 365 groups per project and rely only on mailbox/SharePoint membership
Add a note to user profiles and manually share SAS tokens per request
Correct answers
Define and assign custom security attributes to users/resources, and use attribute governance/filters to enforce project-scoped access
Explanations
Correct:
Define and assign custom security attributes to users/resources, and use attribute governance/filters to enforce project-scoped access Custom security attributes are business-specific key-value pairs you can query/filter against and govern for visibility, enabling fine-grained authorization while keeping sensitive attributes admin-only.
Wrong:
Grant all project members Storage Blob Data Contributor at the subscription scope Over-permissive and not project-scoped.
Create Microsoft 365 groups per project and rely only on mailbox/SharePoint membership Doesn’t control Storage blobs or attribute visibility.
Add a note to user profiles and manually share SAS tokens per request Manual, error-prone, and lacks governance.