DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
You are designing a data lake in Azure Data Lake Storage Gen2 for a large enterprise. You need to ensure that only authorized users can access the data, and you must implement the principle of least privilege. Which security mechanism should you use to grant fine-grained access to specific directories and files without modifying the underlying storage account firewall settings?
⚠ Common exam trap
DP-203 often tests the misconception that storage account firewall rules or SAS tokens provide identity-based, fine-grained access control, when in fact only the combination of RBAC and POSIX ACLs delivers directory-level least privilege without network changes.
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
✓
Azure RBAC roles combined with POSIX-like ACLs
Azure RBAC roles combined with POSIX-like ACLs is correct because Azure Data Lake Storage Gen2 supports a hierarchical namespace that enables POSIX-style access control lists (ACLs) at the directory and file level, allowing fine-grained permissions (read, write, execute) for specific Microsoft Entra ID principals. RBAC handles coarse-grained control at the management group, subscription, or storage account scope, while ACLs provide the granular, object-level authorization required for least privilege. This combination does not require altering the storage account firewall, which controls network access rather than identity-based permissions.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Azure RBAC roles combined with POSIX-like ACLs
Why this is correct
Azure RBAC grants coarse access at account, container or folder scope, while POSIX-like ACLs refine permissions down to individual directories and files for specific principals. Combining both enforces least privilege without touching the storage account firewall.
- ✗
Managed identities for Azure resources
Why it's wrong here
Managed identities provide an identity for a resource to authenticate to other services; they grant no directory- or file-level permissions by themselves. They are the correct choice when a service such as Azure Data Factory must authenticate to storage without storing credentials, not when granting users fine-grained POSIX-style access to specific paths.
- ✗
Storage account firewall rules
Why it's wrong here
Storage account firewall rules operate at the account or network boundary, permitting or denying traffic by IP range, virtual network, or public access; they cannot grant per-directory or per-file permissions. They are tempting because they restrict access without touching identity, and would be correct for locking an account to specific networks.
- ✗
Shared access signatures (SAS)
Why it's wrong here
SAS tokens delegate time-limited access to a blob, container, or account, but they are bearer credentials that cannot express per-directory ACLs for many users under least privilege. They are tempting for granting temporary external access, and would be correct for sharing a specific file with a partner for a fixed period.
Visual reference
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Implement Data Lake Storage
Key term
Azure Data Lake Gen2
Azure Data Lake Gen2 is a cloud-based data storage service that combines the scalability and performance of a data lake with the hierarchical file system and security of a data warehouse, designed for big data analytics.
Key term
Azure RBAC for Data
Azure RBAC for Data is a security system that controls who can read, write, or manage data in Azure storage services using role-based permissions.
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 and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Microsoft exam blueprint
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.