Quick Answer
The correct answer is column-level security because it is the only Azure Synapse dedicated SQL pool feature that directly restricts access to specific columns, such as credit card numbers, for unauthorized users while allowing authorized roles to view them. This works by applying a GRANT or DENY permission on individual columns within a table, effectively hiding sensitive data at the schema level rather than merely obfuscating it. On the DP-203 exam, this scenario tests your understanding of granular access controls for GDPR compliance, and a common trap is confusing column-level security with dynamic data masking, which only hides data from query results but does not prevent users from reading the underlying values. Another frequent pitfall is selecting row-level security, which filters rows based on user context but leaves all columns visible. Remember the memory tip: columns are vertical, so column-level security controls what you see up and down; masking only blurs the view but still lets data through.
This DP-203 practice question tests your understanding of develop data processing. 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.
You are designing a data processing solution for a financial services company. The solution must process sensitive customer data and comply with GDPR. The data will be stored in Azure Synapse Analytics. You need to ensure that only authorized users can view specific columns (e.g., credit card numbers). Which security feature should you implement?
Row-level security (RLS)
Why wrong: RLS restricts rows, not columns.
Column-level security
Column-level security restricts access to specific columns.
Dynamic data masking
Why wrong: Masking obfuscates but does not prevent access.
Microsoft Defender for Cloud
Why wrong: Defender is for security monitoring, not column access control.
Answer choices
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
Option C is correct because Column-level security in Azure Synapse allows you to restrict access to specific columns for specific users or roles. Option A is wrong because Row-level security restricts rows, not columns. Option B is wrong because Dynamic data masking obfuscates data but does not prevent access entirely. Option D is wrong because Microsoft Defender for Cloud is a security monitoring tool, not for column-level access control.
Key principle: Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Answer analysis
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 rows, not columns.
Column-level security
Why this is correct
Column-level security restricts access to specific columns.
Related concept
CIDR notation defines the prefix length.
Dynamic data masking
Why it's wrong here
Masking obfuscates but does not prevent access.
Microsoft Defender for Cloud
Why it's wrong here
Defender is for security monitoring, not column access control.
Common exam traps
Subnetting questions often tempt you into counting all addresses. In normal IPv4 subnets, the network and broadcast addresses are not usable host addresses.
Detailed technical explanation
Subnetting questions test whether you can identify the network, broadcast address, usable range, mask and correct subnet. Slow down enough to calculate the block size correctly.
Key takeaway
Count usable hosts — not total addresses — and remember that the network and broadcast addresses are not available to hosts in standard IPv4 subnets.
Real-world example
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.
What to study next
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related DP-203 subnetting questions on CIDR, address ranges, and subnet selection.
Develop data processing — study guide chapter
Learn the concepts, then practise the questions
Develop data processing 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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise DP-203 questions linked to Secure, monitor, and optimize data storage and data processing.
Practise DP-203 questions linked to Design and develop data processing.
Practise DP-203 questions linked to Design and implement data security.
Practise DP-203 questions linked to Monitor and optimize data storage and processing.
Practise DP-203 questions linked to Design and implement data storage.
Practise DP-203 questions linked to Develop data processing.
Practise DP-203 questions linked to DP-203 fundamentals.
Practise DP-203 questions linked to DP-203 scenario.
Practise DP-203 questions linked to DP-203 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Develop data processing — This question tests Develop data processing — CIDR notation defines the prefix length..
The correct answer is: Column-level security — Option C is correct because Column-level security in Azure Synapse allows you to restrict access to specific columns for specific users or roles. Option A is wrong because Row-level security restricts rows, not columns. Option B is wrong because Dynamic data masking obfuscates data but does not prevent access entirely. Option D is wrong because Microsoft Defender for Cloud is a security monitoring tool, not for column-level access control.
Review block sizes, usable host formulas (2^n − 2), and how to find network and broadcast addresses for /24 through /30. Then practise related DP-203 subnetting questions on CIDR, address ranges, and subnet selection.
CIDR notation defines the prefix length.
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 21, 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.