The answer is to implement both row-level security and column-level security. These two actions are correct because they provide granular, native data access controls within an Azure Synapse Analytics dedicated SQL pool, directly restricting sensitive data at the row and column level. Row-level security uses security predicates to transparently filter which rows a user can query based on their identity or group membership, while column-level security denies read access to specific columns for unauthorized principals, effectively hiding sensitive fields like Social Security numbers or financial data. On the Microsoft Azure Data Engineer Associate DP-203 exam, this concept tests your understanding of data plane authorization versus authentication; a common trap is to confuse these with encryption or masking, which protect data at rest or obfuscate it rather than restrict access. Remember the mnemonic “Rows filter, columns block” to recall that RLS filters rows dynamically, whereas column-level security statically denies column access.
DP-203 Design and implement data security Practice Question
This DP-203 practice question tests your understanding of design and implement data security. 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.
Which TWO actions should you take to ensure that only authorized users can access sensitive data in an Azure Synapse Analytics dedicated SQL pool?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement row-level security
Row-level security (RLS) and column-level security are the two correct actions because they directly restrict data access at the row and column granularity within a dedicated SQL pool. RLS uses security predicates to filter which rows a user can query, while column-level security denies access to specific columns for unauthorized principals. Both are native features of Azure Synapse dedicated SQL pools that enforce authorization on the data plane.
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.
✗
Configure Azure Active Directory authentication
Why it's wrong here
Azure AD authentication controls who can connect, not what they can access.
✗
Enable dynamic data masking on all columns
Why it's wrong here
Dynamic data masking does not prevent access; it only masks data for non-privileged users.
✓
Implement row-level security
Why this is correct
Row-level security filters rows based on user identity to prevent unauthorized access.
Related concept
Read the scenario before looking for a memorised answer.
✓
Implement column-level security
Why this is correct
Column-level security restricts access to specific columns containing sensitive data.
Related concept
Read the scenario before looking for a memorised answer.
✗
Enable transparent data encryption
Why it's wrong here
TDE encrypts data at rest but does not control user access.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is confusing data protection features (masking, encryption) with access control features (RLS, column-level security), leading candidates to select dynamic data masking or TDE instead of the correct granular authorization mechanisms.
Detailed technical explanation
How to think about this question
Row-level security in Azure Synapse dedicated SQL pools is implemented via inline table-valued functions that define a security predicate, which is then bound to a security policy. Column-level security uses GRANT/DENY permissions on specific columns, and both features are enforced at the query engine level before any data is returned. A real-world scenario is a healthcare application where a doctor should only see rows for their own patients (RLS) and must not see the 'salary' column (column-level security), even if they have SELECT on the table.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-203 question in full detail.
Design and implement data security — This question tests Design and implement data security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Implement row-level security — Row-level security (RLS) and column-level security are the two correct actions because they directly restrict data access at the row and column granularity within a dedicated SQL pool. RLS uses security predicates to filter which rows a user can query, while column-level security denies access to specific columns for unauthorized principals. Both are native features of Azure Synapse dedicated SQL pools that enforce authorization on the data plane.
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 →
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.