The answer is Azure RBAC roles, ACLs, and SAS tokens. These three methods provide layered security for Azure Data Lake Storage Gen2 by controlling access at the account, container, or file level. RBAC roles manage coarse-grained permissions for Azure resources, ACLs offer fine-grained POSIX-style control over directories and files, and SAS tokens grant time-limited, delegated access without exposing the account key. On the DP-203 exam, this question tests your understanding of how ADLS Gen2 differs from Blob Storage and Azure SQL Database—common traps include confusing connection strings (used for SQL) or managed identities (which are identity types, not direct authorization methods). Remember that managed identities authenticate to RBAC but are not standalone authorization methods. For a quick memory tip: think of the three layers as “Role, Rule, and Token”—RBAC for broad control, ACLs for granular rules, and SAS for temporary tokens.
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 need to secure access to an Azure Data Lake Storage Gen2 account. Which THREE methods can you use to authenticate and authorize access?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Shared access signatures (SAS).
Options A, B, and E are correct. RBAC roles, ACLs, and SAS tokens are all valid methods. Option C is wrong because connection strings are for Azure SQL Database. Option D is wrong because managed identities are identities, not directly authorization methods, but they can be used with RBAC; however, the question asks for methods to authenticate and authorize, and managed identity is an identity type, not a method.
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.
✗
SQL connection strings.
Why it's wrong here
Connection strings are not used for Azure Data Lake Storage Gen2.
✓
Shared access signatures (SAS).
Why this is correct
SAS tokens provide delegated access to resources.
Related concept
Authentication checks who the user is.
✗
Managed identities.
Why it's wrong here
Managed identities are used to authenticate but not a direct authorization method; they must be assigned RBAC roles.
✓
Access control lists (ACLs).
Why this is correct
ACLs provide fine-grained access control at the file and directory level.
Related concept
Authentication checks who the user is.
✓
Azure RBAC roles.
Why this is correct
RBAC roles provide coarse-grained access control.
Related concept
Authentication checks who the user is.
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: Shared access signatures (SAS). — Options A, B, and E are correct. RBAC roles, ACLs, and SAS tokens are all valid methods. Option C is wrong because connection strings are for Azure SQL Database. Option D is wrong because managed identities are identities, not directly authorization methods, but they can be used with RBAC; however, the question asks for methods to authenticate and authorize, and managed identity is an identity type, not a method.
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.