The correct answer is to assign the Storage Blob Data Reader role at the invoices container scope. This is because Azure RBAC allows you to grant granular, least-privilege access by scoping a role to a specific resource, such as a container, rather than the entire storage account. The Storage Blob Data Reader role provides read-only access to blob data, which is exactly what John needs to download blobs, while scoping it to the invoices container prevents him from accessing any other containers in the account. On the AZ-104 exam, this scenario tests your understanding of Azure RBAC scope levels—management group, subscription, resource group, and resource—and the principle of least privilege. A common trap is choosing a broader scope like the storage account or assigning a role with write permissions, such as Storage Blob Data Contributor. Remember the memory tip: "Scope it to the container, keep it a reader" to avoid granting unnecessary access.
AZ-104 Implement and Manage Storage Practice Question
This AZ-104 practice question tests your understanding of implement and manage storage. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
Exhibit
Azure portal role assignments for storage account appdata01:
- John Doe: Contributor at storage account scope
- Data access test from portal: You do not have permissions to list containers.
- Requirement: John must read and download blobs from container invoices and nothing else.
Based on the exhibit, what is the best access change to let John download blobs from only the invoices container?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Azure portal role assignments for storage account appdata01:
- John Doe: Contributor at storage account scope
- Data access test from portal: You do not have permissions to list containers.
- Requirement: John must read and download blobs from container invoices and nothing else.
A
Assign Reader at the storage account scope so John can view the storage account and its data.
Why wrong: Reader grants management-plane visibility only. It does not allow blob data access, so John still would not be able to download blobs from the container.
B
Assign Storage Blob Data Reader at the invoices container scope.
Blob downloads require a data-plane role, not the Contributor role on the storage account. Assigning Storage Blob Data Reader at the container scope gives John only the read permissions needed for invoices and avoids granting access to other containers or management operations.
C
Assign Storage Account Contributor at the resource group scope.
Why wrong: This broadens administrative permissions but still does not automatically grant the specific blob data-plane access needed to read container contents.
D
Make the invoices container public and keep John's existing Contributor role.
Why wrong: Public access would expose the container more broadly than required and would remove least-privilege control. The scenario asks for a restricted, authenticated solution.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Assign Storage Blob Data Reader at the invoices container scope.
Option B is correct because assigning the Storage Blob Data Reader role at the invoices container scope grants John the minimum permissions needed to download blobs from that specific container. This role provides read access to blob data without allowing any write or management operations, and scoping it to the container ensures John cannot access other containers in the storage account.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Assign Reader at the storage account scope so John can view the storage account and its data.
Why it's wrong here
Reader grants management-plane visibility only. It does not allow blob data access, so John still would not be able to download blobs from the container.
✓
Assign Storage Blob Data Reader at the invoices container scope.
Why this is correct
Blob downloads require a data-plane role, not the Contributor role on the storage account. Assigning Storage Blob Data Reader at the container scope gives John only the read permissions needed for invoices and avoids granting access to other containers or management operations.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Assign Storage Account Contributor at the resource group scope.
Why it's wrong here
This broadens administrative permissions but still does not automatically grant the specific blob data-plane access needed to read container contents.
✗
Make the invoices container public and keep John's existing Contributor role.
Why it's wrong here
Public access would expose the container more broadly than required and would remove least-privilege control. The scenario asks for a restricted, authenticated solution.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse management-plane roles (like Reader or Contributor) with data-plane roles, assuming that any role with 'read' or 'contributor' in the name grants access to blob data, when in fact only specific data-plane roles (e.g., Storage Blob Data Reader) provide the necessary permissions for blob operations.
Trap categories for this question
Scenario analysis trap
Public access would expose the container more broadly than required and would remove least-privilege control. The scenario asks for a restricted, authenticated solution.
Detailed technical explanation
How to think about this question
Azure RBAC for blob data uses separate data-plane roles (e.g., Storage Blob Data Reader) that are distinct from management-plane roles (e.g., Reader, Contributor). The Storage Blob Data Reader role includes the Microsoft.Storage/storageAccounts/blobServices/containers/blobs/read action, which is required for downloading blobs via the Azure portal, SDKs, or REST API. Scoping the role to a container leverages Azure's hierarchical namespace support, allowing fine-grained access control without affecting other containers.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-104 question in full detail.
Implement and Manage Storage — This question tests Implement and Manage Storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Assign Storage Blob Data Reader at the invoices container scope. — Option B is correct because assigning the Storage Blob Data Reader role at the invoices container scope grants John the minimum permissions needed to download blobs from that specific container. This role provides read access to blob data without allowing any write or management operations, and scoping it to the container ensures John cannot access other containers in the storage account.
What should I do if I get this AZ-104 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This AZ-104 practice question is part of Courseiva's free Microsoft certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the AZ-104 exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.