Quick Answer
The correct answer is row-level security (RLS), which is the feature in Azure SQL Database that restricts data access at the row level based on the user executing the query. RLS works by applying a security policy with a predicate function that filters rows according to attributes like a sales manager’s assigned region, ensuring they only see their own data. On the Microsoft Azure Data Fundamentals DP-900 exam, this scenario tests your understanding of how RLS differs from other access controls, such as column-level security or dynamic data masking—a common trap is confusing RLS with masking, which hides data values rather than filtering rows. Remember that RLS is about row visibility, not data obfuscation. A simple memory tip: think of RLS as a “bouncer at the row door” who checks your ID (region) before letting you see each row.
This DP-900 practice question tests your understanding of describe core data concepts. 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 company uses Azure SQL Database and wants to implement row-level security so that sales managers can only see data for their own region. Which feature should they use?
Dynamic Data Masking
Why wrong: Dynamic Data Masking hides sensitive data in query results but does not restrict row access.
Row-level security (RLS)
RLS restricts which rows users can see based on group membership or context.
Transparent Data Encryption (TDE)
Why wrong: TDE encrypts the entire database at rest, not row-level access.
Microsoft Purview
Why wrong: Microsoft Purview is a data governance service, not a database security feature.
Answer choices
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 the correct feature because it allows you to control access to rows in a database table based on the characteristics of the user executing a query. In this scenario, RLS can be implemented using a security policy and a predicate function that filters rows based on the sales manager's region, ensuring they only see data for their own region.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
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 sensitive data in query results but does not restrict row access.
Row-level security (RLS)
Why this is correct
RLS restricts which rows users can see based on group membership or context.
Related concept
Read the scenario before looking for a memorised answer.
Transparent Data Encryption (TDE)
Why it's wrong here
TDE encrypts the entire database at rest, not row-level access.
Microsoft Purview
Why it's wrong here
Microsoft Purview is a data governance service, not a database security feature.
Common exam traps
The trap here is that candidates often confuse Dynamic Data Masking (which hides data in results) with Row-level security (which filters rows), leading them to choose option A when the requirement is about restricting row visibility, not masking column values.
Detailed technical explanation
RLS in Azure SQL Database is implemented using CREATE SECURITY POLICY with a predicate function that returns a bit value (0 or 1) to determine row visibility. The predicate function typically uses the SESSION_CONTEXT or USER_NAME() to map the user to a region, and the security policy applies the filter transparently to all SELECT, UPDATE, and DELETE operations. A common subtlety is that RLS predicates are evaluated per row, which can impact performance on large tables if not indexed properly.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
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
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Describe core data concepts — study guide chapter
Learn the concepts, then practise the questions
Describe core data concepts practice questions
Targeted practice on this topic area only
All DP-900 questions
982 questions across all exam domains
Microsoft Azure Data Fundamentals DP-900 study guide
Full concept coverage aligned to exam objectives
DP-900 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-900 questions linked to Describe core data concepts.
Practise DP-900 questions linked to Describe an analytics workload on Azure.
Practise DP-900 questions linked to Identify considerations for relational data on Azure.
Practise DP-900 questions linked to Describe considerations for working with non-relational data on Azure.
Practise DP-900 questions linked to DP-900 fundamentals.
Practise DP-900 questions linked to DP-900 scenario.
Practise DP-900 questions linked to DP-900 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Describe core data concepts — This question tests Describe core data concepts — Read the scenario before looking for a memorised answer..
The correct answer is: Row-level security (RLS) — Row-level security (RLS) is the correct feature because it allows you to control access to rows in a database table based on the characteristics of the user executing a query. In this scenario, RLS can be implemented using a security policy and a predicate function that filters rows based on the sales manager's region, ensuring they only see data for their own region.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 →
Keep practising
Last reviewed: Jun 24, 2026
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.