The correct approach is to use Azure RBAC roles and ACLs on directories and files, combined with enabling storage analytics logging. This combination provides the granular, user-level control required for sensitive customer data in ADLS Gen2, where RBAC manages coarse permissions at the storage account level and POSIX-like ACLs handle fine-grained access on specific directories or files, while storage analytics logs capture all read and write operations for auditing. On the DP-203 exam, this scenario tests your understanding of the layered security model in Azure Data Lake Storage Gen2, often appearing in questions that contrast RBAC with shared access signatures or managed identities—a common trap is choosing SAS tokens for user access, but they are designed for delegated, time-limited access, not ongoing user management. Remember the memory tip: "RBAC for the big picture, ACLs for the details, and logs to catch the crooks."
DP-203 Design and implement data storage Practice Question
This DP-203 practice question tests your understanding of design and implement data storage. 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.
Your company stores sensitive customer data in Azure Data Lake Storage Gen2. You need to ensure that only authorized users can access the data, and that access is audited. Which approach should you use to control access to the data lake?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Azure RBAC roles and ACLs on directories/files, and enable storage analytics logging
Option A is correct because RBAC combined with ACLs provides fine-grained access control and Azure Storage analytics logs enable auditing. Option B is wrong because SAS tokens are less granular and harder to manage for many users. Option C is wrong because firewall rules control network access, not user authorization. Option D is wrong because managed identities are for service-to-service authentication, not user access.
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.
✗
Use Azure managed identities for all user access
Why it's wrong here
Managed identities are for Azure resources, not for individual user authentication.
✓
Use Azure RBAC roles and ACLs on directories/files, and enable storage analytics logging
Why this is correct
RBAC provides coarse access, ACLs provide fine-grained, and logging audits access.
Related concept
Authentication checks who the user is.
✗
Use shared access signatures (SAS) with stored access policies
Why it's wrong here
SAS tokens are for delegated access, not suitable for many users with varying permissions.
✗
Configure a virtual network service endpoint and firewall rules
Why it's wrong here
Network controls restrict IP addresses but do not authenticate users.
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.
Design and implement data storage — This question tests Design and implement data storage — Authentication checks who the user is..
What is the correct answer to this question?
The correct answer is: Use Azure RBAC roles and ACLs on directories/files, and enable storage analytics logging — Option A is correct because RBAC combined with ACLs provides fine-grained access control and Azure Storage analytics logs enable auditing. Option B is wrong because SAS tokens are less granular and harder to manage for many users. Option C is wrong because firewall rules control network access, not user authorization. Option D is wrong because managed identities are for service-to-service authentication, not user access.
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.