AZ-500 · Question #497
You have an Azure subscription that contains an Azure Blob storage account named blob1. You need to configure attribute-based access control (ABAC) for blob1. Which attributes can you use in access…
The correct answer is B. blob index tags and container names only. Azure ABAC Attribute Explanation Option B is correct because Azure ABAC for Blob Storage supports blob index tags and container names as valid attributes in role assignment conditions, allowing fine-grained access control based on these properties. Why the other options are…
Question
Options
- Ablob index tags only
- Bblob index tags and container names only
- Cfile extensions and container names only
- Dblob index tags, file extensions, and container names
How the community answered
(29 responses)- B93% (27)
- C3% (1)
- D3% (1)
Explanation
Azure ABAC Attribute Explanation
Option B is correct because Azure ABAC for Blob Storage supports blob index tags and container names as valid attributes in role assignment conditions, allowing fine-grained access control based on these properties.
Why the other options are wrong:
- Option A is too restrictive - it omits container names, which are a valid and commonly used ABAC attribute
- Option C is incorrect because file extensions are not a supported ABAC attribute in Azure Blob Storage conditions, even though they might seem intuitive
- Option D is incorrect for the same reason - file extensions are not a valid ABAC attribute, making this combination unsupported
Memory Tip: Think "BIC" minus the C - Blob index tags and Container names are your two ABAC tools. File extensions sound useful but Azure doesn't support them as ABAC attributes - if you need extension-based filtering, you'd need a different approach like lifecycle management policies. Remember: "Tags and Containers = ABAC winners."
Topics
Community Discussion
No community discussion yet for this question.