Secure, monitor, and optimize data storage and data processing →mediumMultiple ChoiceObjective-mapped
DP-203 Practice Question: Secure, monitor, and optimize data storage and data processing
You have an Azure Synapse Analytics dedicated SQL pool that stores sensitive customer data. You need to ensure that only users with a specific Microsoft Entra ID role can access the data, and all access must be logged for auditing. What should you implement?
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
✓
Row-level security (RLS) with a security policy
Row-level security (RLS) is the correct choice because it restricts data access at the row level based on user context, such as Microsoft Entra ID role membership, and all access can be logged via auditing. Dynamic data masking (A) obfuscates data but does not restrict access. Azure RBAC (B) controls management plane access, not data access within the SQL pool. Column-level security (D) restricts access to specific columns, not rows.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Dynamic data masking
Why it's wrong here
Dynamic data masking hides data but does not prevent access.
- ✗
Azure RBAC at the SQL pool level
Why it's wrong here
Azure RBAC controls management operations, not data access.
- ✓
Row-level security (RLS) with a security policy
Why this is correct
RLS restricts row access based on user context, and can be tied to Microsoft Entra ID roles.
- ✗
Column-level security
Why it's wrong here
Column-level security restricts access to specific columns, not rows.
Quick reference
Access Control Model Comparison
| Model | Acronym | Who Controls Access? | Best For |
|---|---|---|---|
| Discretionary Access Control | DAC | Resource owner | Small teams, file shares |
| Mandatory Access Control | MAC | System / security labels | Classified govt / military |
| Role-Based Access Control | RBAC | Administrator (via roles) | Enterprise environments |
| Attribute-Based Access Control | ABAC | Policy engine (user + resource attributes) | Fine-grained, dynamic policies |
| Rule-Based Access Control | RuBAC | System rules / ACLs | Firewall rules, network ACLs |
Go deeper
Related to this question
Learn chapter
Introduction to Azure Data Engineering
Key term
Dynamic Data Masking
Dynamic Data Masking is a security feature that automatically hides sensitive data in query results so that unauthorized users see only masked information, while authorized users see the real data.
Key term
Azure Data Masking
Azure Data Masking is a security feature that hides sensitive data in database query results by replacing it with obscured characters, so unauthorized users see a blurred version instead of the real information.
About these practice questions
This DP-203 question is part of Courseiva's 760-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 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.