DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
Your team is using Azure Synapse Analytics to process sensitive customer data. You need to ensure that column-level security is applied to a specific table so that only users with a certain role can view certain columns. Which feature should you use?
⚠ Common exam trap
DP-203 often tests the confusion between column-level security and dynamic data masking, where candidates might think DDM restricts access, but it only masks data and does not prevent retrieval of the actual values.
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
✓
Column-level security (CLS)
Column-level security (CLS) in Azure Synapse Analytics allows you to restrict access to specific columns in a table based on the user's role or permissions. It is implemented using GRANT and DENY statements on individual columns, ensuring that only authorized users can view sensitive columns. This directly addresses the requirement to apply column-level security to a specific table.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✓
Column-level security (CLS)
Why this is correct
Column-level security uses GRANT and DENY statements on individual columns, restricting which roles can read specified fields within the table. This directly enforces the requirement that only users holding a certain role view particular columns.
- ✗
Row-level security (RLS)
Why it's wrong here
Row-level security filters which rows a query returns via a predicate function; it cannot restrict individual columns. It is the right choice when users must see only their own region's or tenant's rows within a shared table. Restricting specific columns to a role needs column-level GRANT/DENY.
- ✗
Azure Purview data policies
Why it's wrong here
Azure Purview data policies govern access across catalogued sources at a governance layer, not the column GRANT/DENY enforced inside a Synapse dedicated SQL pool table. Purview suits centralised, cross-platform access governance. Enforcing role-based column visibility on one table requires native column-level security.
- ✗
Dynamic data masking (DDM)
Why it's wrong here
Dynamic data masking obscures column values in query output for non-privileged users, but the underlying data remains readable and users with UNMASK permission see everything. It suits reducing accidental exposure in ad-hoc queries. The scenario requires outright denial of column access, which masking does not enforce.
Go deeper
Related to this question
Learn chapter
Implement Azure Synapse Analytics
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
Azure Synapse Analytics
Azure Synapse Analytics is a cloud-based data integration, warehousing, and analytics service that brings together big data and data warehouse capabilities under one platform.
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.