mediumMultiple Choice
DP-203 Practice Question: Refer to the exhibit
Network Topology
Refer to the exhibit. A user with Storage Blob Data Reader role on the container rawdata cannot list files under /2023/07/. What is the most likely reason?
⚠ Common exam trap
Candidates often assume the Storage Blob Data Reader role is sufficient for all read operations, but Azure Data Lake Storage Gen2 requires explicit ACL execute permission on directories for listing and traversal, which is a common point of confusion between flat blob storage and hierarchical namespace storage.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The directory ACL does not grant 'execute' permission to the user
In Azure Data Lake Storage Gen2, listing files in a directory requires both read (r) and execute (x) permissions on the directory itself. The Storage Blob Data Reader role grants read access to blob data but does not automatically grant the execute permission on directory ACLs. Without execute permission on the /2023/07/ directory, the user cannot traverse or list its contents, even though they can read blobs they know the path to.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
The directory ACL does not grant 'execute' permission to the user
Why this is correct
Listing a directory requires execute permission on every parent path, not just read on the blobs. Without execute on the directory ACL, the user cannot traverse /2023/07/, so enumeration fails even though Storage Blob Data Reader grants read access to blob data.
- ✗
The user does not have Storage Blob Data Contributor role
Why it's wrong here
Storage Blob Data Reader already grants list and read access, so Contributor adds write permissions that listing does not require. Contributor is needed when the user must upload, overwrite or delete blobs; the listing failure instead points to a missing permission at the folder or container scope.
- ✗
The user is not the owner of the directory
Why it's wrong here
Blob storage has no directory ownership concept; listing depends solely on data-plane RBAC. Storage Blob Data Reader already grants list permission at container scope, so ownership is irrelevant. This option tempts those carrying over POSIX filesystem assumptions, where directory ownership and execute bits govern listing.
- ✗
The container name is misspelled
Why it's wrong here
A misspelled container name would prevent the user reaching the container at all, yet the stem states the role is assigned on rawdata, implying the container exists. The failure is scoped to the /2023/07/ prefix. Misspelling is tempting because typos do break access, but they produce container-not-found, not partial listing failures.
Go deeper
Related to this question
About these practice questions
This DP-203 question is part of Courseiva's 509-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This DP-203 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 DP-203 exam.