mediumMultiple SelectObjective-mapped
DP-203 Practice Question: Which TWO actions should you take to ensure that…
Which TWO actions should you take to ensure that only authorized users can access sensitive data in an Azure Synapse Analytics dedicated SQL pool?
⚠ Common exam trap
A common mix-up: candidates confuse 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.
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
✓
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.
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.
- ✓
Implement column-level security
Why this is correct
Column-level security restricts access to specific columns containing sensitive data.
- ✗
Enable transparent data encryption
Why it's wrong here
TDE encrypts data at rest but does not control user access.
Go deeper
Related to this question
Learn chapter
Introduction to Azure Data Engineering
Key term
Column-Level Security
Column-Level Security is a database feature that restricts access to specific columns in a table, allowing only authorized users to see sensitive data within those columns.
Key term
Row-Level Security
Row-Level Security is a database feature that restricts which rows of data a user can see based on their identity or role, acting like a custom filter per person.
About these practice questions
Courseiva writes every DP-203 question from scratch — 760 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.