The answer is to assign the Storage Blob Data Contributor role at the container level and then use ACLs to deny delete on the directory. This works because Azure RBAC roles like Storage Blob Data Contributor inherently grant read, write, and delete permissions as a combined set, so you cannot selectively remove delete while keeping write using RBAC alone. ACLs, however, operate at a finer granularity on directories and files, allowing you to explicitly set read and write permissions while omitting the delete permission, effectively denying it. On the DP-203 exam, this scenario tests your understanding of the layered security model in ADLS Gen2, where RBAC controls broad container-level access and ACLs refine permissions on specific paths. A common trap is assuming a custom RBAC role can separate write from delete, but Azure does not offer a built-in role for write-without-delete. Memory tip: think of RBAC as the bouncer at the door (container) and ACLs as the room-specific rules inside—you can enter and rearrange furniture (write) but not throw anything away (delete).
DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
This DP-203 practice question tests your understanding of secure, monitor, and optimize data storage and data processing. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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.
You are designing access control for Azure Data Lake Storage Gen2. You need to allow a group of data scientists to read and write files in the 'processed' directory but prevent them from deleting files. Which authorization method should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Assign the Storage Blob Data Contributor role at the container level and use ACLs to deny delete on the directory
Azure RBAC roles like Storage Blob Data Contributor grant read/write/delete permissions. To differentiate write and delete, you need ACLs that allow read/execute on the container and read/write on the directory, but not delete. Option A (Storage Blob Data Contributor) includes delete. Option B (Storage Blob Data Reader) is read-only. Option D (Storage Blob Delegator) is not a built-in role.
Key principle: Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
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 the Storage Blob Data Contributor role at the container level
Why it's wrong here
This role allows delete.
✗
Assign the Storage Blob Delegator role at the container level
Why it's wrong here
No such built-in role.
✓
Assign the Storage Blob Data Contributor role at the container level and use ACLs to deny delete on the directory
Why this is correct
ACLs can override RBAC permissions to deny delete.
Related concept
Authentication checks who the user is.
✗
Assign the Storage Blob Data Reader role and use ACLs to grant write
Why it's wrong here
Reader role cannot write.
Common exam traps
Common exam trap: authentication is not authorization
Logging in proves the user can authenticate. It does not automatically mean the user is allowed to enter privileged or configuration mode. Watch for AAA authorization, privilege level and command authorization details.
Detailed technical explanation
How to think about this question
This kind of question is testing the difference between identity and permission. A user may successfully log in to a router because authentication is working, but still fail to enter configuration mode because authorization is missing, misconfigured or mapped to a lower privilege level.
KKey Concepts to Remember
Authentication checks who the user is.
Authorization controls what the user is allowed to do after login.
Privilege levels affect access to EXEC and configuration commands.
AAA, TACACS+ and RADIUS can separate login success from command access.
TExam Day Tips
→Do not assume successful login means full administrative access.
→Look for words such as cannot enter configuration mode, privilege level, authorization or command access.
→Separate login problems from permission problems before choosing the answer.
Key takeaway
Authentication proves identity; authorization controls what that identity can do after login. Both must work for full privileged access.
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 DP-203 question in full detail.
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related DP-203 questions on access control and AAA configuration.
Secure, monitor, and optimize data storage and data processing — This question tests Secure, monitor, and optimize data storage and data processing — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Assign the Storage Blob Data Contributor role at the container level and use ACLs to deny delete on the directory — Azure RBAC roles like Storage Blob Data Contributor grant read/write/delete permissions. To differentiate write and delete, you need ACLs that allow read/execute on the container and read/write on the directory, but not delete. Option A (Storage Blob Data Contributor) includes delete. Option B (Storage Blob Data Reader) is read-only. Option D (Storage Blob Delegator) is not a built-in role.
What should I do if I get this DP-203 question wrong?
Review Cisco AAA concepts — authentication, authorization, and accounting. Study privilege levels (0–15), command authorization under TACACS+, and how RADIUS differs. Then practise related DP-203 questions on access control and AAA configuration.
What is the key concept behind this question?
Authentication checks who the user is.
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 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.
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.