DP-700 Implement and Manage an Analytics Solution Practice Question
You are implementing a security model where users should only see rows matching their assigned department. Which Fabric feature enables this?
⚠ Common exam trap
Candidates often suggest workspace access roles or folder permissions, which restrict entire containers rather than filtering specific rows of data.
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)
Row-Level Security (RLS) is essential for ensuring data compliance, especially when sharing reports across different organizational departments. By defining security predicates, data engineers can control access at the record level. This ensures that sensitive data is only accessible to authorized users, which is a fundamental requirement for secure data sharing and analytics governance in Microsoft Fabric.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Object-Level Security (OLS)
Why it's wrong here
OLS restricts access to entire tables or columns rather than specific rows. If the requirement is to restrict access based on department while keeping the schema consistent, OLS is the wrong tool. OLS is used for hiding sensitive columns, not for filtering records based on user attributes.
- ✓
Row-Level Security (RLS)
Why this is correct
RLS allows you to define filters on the data model that restrict access based on the user's identity. By applying security predicates, you ensure that users only see the data relevant to their department, maintaining strict data privacy while allowing a single report to serve multiple user groups.
- ✗
Workspace Permissions
Why it's wrong here
Workspace permissions govern access to the artifact, not the content within the data. Giving someone access to the workspace grants them full access to the underlying data. It is a coarse-grained control method that does not provide the granularity required to perform row-level filtering based on user department.
- ✗
Data Masking
Why it's wrong here
Data Masking obscures sensitive information within a column, like hiding part of an email address or credit card number. It does not filter rows out of a result set. For department-based row filtering, Data Masking would be ineffective and inappropriate, as it doesn't remove the unauthorized data records.
About these practice questions
One of 152 original DP-700 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. 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-700 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-700 exam.