- A
Create views in Azure Synapse Serverless SQL with security predicates
Serverless SQL can query ADLS and apply RLS via views.
- B
Assign Azure RBAC roles for each department on the storage account
Why wrong: RBAC roles control access at the storage account/container level, not rows.
- C
Implement Azure Purview data policies for row-level security
Why wrong: Purview does not enforce row-level security.
- D
Use Azure Data Lake Storage Gen2 access control lists (ACLs) at the file level
Why wrong: ACLs work at file/folder level, not row level.
Quick Answer
The correct approach is to create views in Azure Synapse Serverless SQL with security predicates, as this is the only native Azure service that provides declarative row-level filtering directly on data stored in Azure Data Lake Storage Gen2. This works by using the SECURITY_POLICY and FILTER_PREDICATE functions to dynamically filter rows based on the user’s identity, such as department membership, without duplicating data or managing separate files. On the DP-203 exam, this scenario tests your understanding of how to enforce row-level security on ADLS Gen2 data without moving or transforming it, often appearing as a trap where candidates mistakenly choose Azure Purview or RBAC on storage containers. The key distinction is that Synapse Serverless SQL applies filtering at query time, not at the storage layer. Remember: for row-level security on data lake files, think “Synapse Serverless SQL views with predicates” — the mnemonic “RLS = View + Predicate” will help you avoid the common pitfall of selecting storage-level access controls.
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.
A company is designing a data lake on Azure Data Lake Storage Gen2. They need to enforce row-level security on the data for different departments. Which approach should they use?
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
Create views in Azure Synapse Serverless SQL with security predicates
Azure Synapse Serverless SQL supports row-level security (RLS) through the creation of views that use the `SECURITY_POLICY` and `FILTER_PREDICATE` functions. This allows you to filter rows based on the user's identity (e.g., department membership) without duplicating data or managing separate files. It is the only native Azure service that provides declarative row-level filtering directly on data stored in Azure Data Lake Storage Gen2.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Create views in Azure Synapse Serverless SQL with security predicates
Why this is correct
Serverless SQL can query ADLS and apply RLS via views.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Assign Azure RBAC roles for each department on the storage account
Why it's wrong here
RBAC roles control access at the storage account/container level, not rows.
- ✗
Implement Azure Purview data policies for row-level security
Why it's wrong here
Purview does not enforce row-level security.
- ✗
Use Azure Data Lake Storage Gen2 access control lists (ACLs) at the file level
Why it's wrong here
ACLs work at file/folder level, not row level.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Azure RBAC or ACLs (which control access to storage objects) with row-level security (which controls access to rows within a data set), leading them to choose a storage-level permission model instead of a query-level filtering mechanism.
Detailed technical explanation
How to think about this question
Row-level security in Azure Synapse Serverless SQL is implemented by creating a security policy that uses an inline table-valued function as a filter predicate. This predicate is evaluated against the `USER_NAME()` or `SESSION_CONTEXT()` to dynamically restrict rows. Under the hood, the serverless SQL engine pushes the predicate down to the data source (e.g., Parquet files) to minimize data movement, making it efficient for large datasets.
KKey Concepts to Remember
- Read the scenario before looking for a memorised answer.
- Find the constraint that changes the correct option.
- Eliminate answers that are true in general but not in this case.
TExam Day Tips
- Watch for words such as best, first, most likely and least administrative effort.
- Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
- →
Design and implement data storage — study guide chapter
Learn the concepts, then practise the questions
- →
Design and implement data storage practice questions
Targeted practice on this topic area only
- →
All DP-203 questions
846 questions across all exam domains
- →
Microsoft Azure Data Engineer Associate DP-203 study guide
Full concept coverage aligned to exam objectives
- →
DP-203 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related DP-203 practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Secure, monitor, and optimize data storage and data processing practice questions
Practise DP-203 questions linked to Secure, monitor, and optimize data storage and data processing.
Design and develop data processing practice questions
Practise DP-203 questions linked to Design and develop data processing.
Design and implement data security practice questions
Practise DP-203 questions linked to Design and implement data security.
Monitor and optimize data storage and processing practice questions
Practise DP-203 questions linked to Monitor and optimize data storage and processing.
Design and implement data storage practice questions
Practise DP-203 questions linked to Design and implement data storage.
Develop data processing practice questions
Practise DP-203 questions linked to Develop data processing.
DP-203 fundamentals practice questions
Practise DP-203 questions linked to DP-203 fundamentals.
DP-203 scenario practice questions
Practise DP-203 questions linked to DP-203 scenario.
DP-203 troubleshooting practice questions
Practise DP-203 questions linked to DP-203 troubleshooting.
Practice this exam
Start a free DP-203 practice session
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Questions learners often ask
What does this DP-203 question test?
Design and implement data storage — This question tests Design and implement data storage — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create views in Azure Synapse Serverless SQL with security predicates — Azure Synapse Serverless SQL supports row-level security (RLS) through the creation of views that use the `SECURITY_POLICY` and `FILTER_PREDICATE` functions. This allows you to filter rows based on the user's identity (e.g., department membership) without duplicating data or managing separate files. It is the only native Azure service that provides declarative row-level filtering directly on data stored in Azure Data Lake Storage Gen2.
What should I do if I get this DP-203 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
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 →
Last reviewed: Jun 24, 2026
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.