The answer is column-level security. This feature is the correct choice because it allows you to restrict access to PII columns in Azure Synapse serverless SQL pool by granting or denying SELECT permissions on individual columns based on a user’s role or identity, ensuring that unauthorized users see NULL or an error instead of sensitive data. On the Microsoft Azure Data Fundamentals DP-900 exam, this scenario tests your understanding of data protection features within Azure Synapse Analytics, often appearing as a trap where candidates might confuse column-level security with row-level security or dynamic data masking—remember that CLS controls *which columns* are visible, not how data is masked or which rows are returned. A helpful memory tip: think of CLS as a “vertical blind” that blocks entire columns from view, while row-level security is a “horizontal filter” that limits rows.
DP-900 Describe an analytics workload on Azure Practice Question
This DP-900 practice question tests your understanding of describe an analytics workload on azure. 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 multinational corporation uses Azure Synapse Analytics serverless SQL pool to query data in Azure Data Lake Storage. The security team requires that access to specific columns containing personally identifiable information (PII) be restricted based on the user's role. Which feature should be implemented?
Why wrong: RLS restricts which rows a user can access, not columns.
B
Column-level security
Column-level security allows granting or denying access to specific columns, preventing unauthorized users from querying PII columns.
C
Azure Purview data classification
Why wrong: Azure Purview is used for data discovery and classification, not for enforcing access control.
D
Dynamic data masking
Why wrong: Dynamic data masking hides sensitive data from non-privileged users but does not prevent them from seeing the columns; it only masks the values.
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
Column-level security (CLS) in Azure Synapse Analytics serverless SQL pool allows you to restrict access to specific columns containing PII based on the user's role or identity. By granting or denying SELECT permissions on individual columns, you can ensure that only authorized users see sensitive data while others see NULL or an error. This directly meets the requirement to restrict column access by role.
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.
✗
Row-level security (RLS)
Why it's wrong here
RLS restricts which rows a user can access, not columns.
✓
Column-level security
Why this is correct
Column-level security allows granting or denying access to specific columns, preventing unauthorized users from querying PII columns.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Purview data classification
Why it's wrong here
Azure Purview is used for data discovery and classification, not for enforcing access control.
✗
Dynamic data masking
Why it's wrong here
Dynamic data masking hides sensitive data from non-privileged users but does not prevent them from seeing the columns; it only masks the values.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Dynamic data masking with column-level security, but DDM only masks data at the presentation layer and does not prevent access to the underlying column, whereas CLS actually denies permission to read the column.
Detailed technical explanation
How to think about this question
Column-level security in Azure Synapse works by applying a GRANT or DENY statement on specific columns within a table, using the standard T-SQL syntax (e.g., DENY SELECT ON dbo.Employees (SSN) TO UnauthorizedRole). Under the hood, the SQL engine rewrites the query plan to block column access at the metadata level, returning an error or NULL depending on the permission. A real-world scenario is a healthcare analytics workload where a serverless SQL pool querying Parquet files in ADLS must hide patient diagnosis columns from data scientists while allowing them to see demographic data.
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-900 question in full detail.
Describe an analytics workload on Azure — This question tests Describe an analytics workload on Azure — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Column-level security — Column-level security (CLS) in Azure Synapse Analytics serverless SQL pool allows you to restrict access to specific columns containing PII based on the user's role or identity. By granting or denying SELECT permissions on individual columns, you can ensure that only authorized users see sensitive data while others see NULL or an error. This directly meets the requirement to restrict column access by role.
What should I do if I get this DP-900 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-900 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-900 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.