Quick Answer
The answer is security. Row-level security in Azure SQL Database primarily addresses the security characteristic of a data workload because it enforces data access control directly at the database engine level, using a security predicate to filter rows based on user attributes like region. This means users see only the data they are authorized to view, without relying on application-level logic, which keeps the restriction consistent and tamper-proof. On the Microsoft Azure Data Fundamentals DP-900 exam, this concept tests your understanding of how Azure SQL Database implements granular access control as part of workload security, often appearing in questions about data protection versus performance or scalability. A common trap is confusing RLS with data masking or partitioning—remember that RLS is about who sees which rows, not about hiding or splitting data. Memory tip: think “RLS = Row Lockdown for Security,” where the predicate acts like a bouncer checking IDs at the row level.
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.
Your team uses Azure SQL Database and wants to implement row-level security (RLS) to restrict access to sales data by region. Which type of data workload characteristic does RLS primarily address?
Concurrency
Why wrong: RLS does not control concurrency; it controls access.
Consistency
Why wrong: Consistency is about data integrity, not access control.
Security
RLS is a security feature that restricts data access based on user identity.
Durability
Why wrong: Durability refers to data persistence after transactions.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Security
Row-level security (RLS) in Azure SQL Database restricts data access at the database engine level by applying a security predicate that filters rows based on user attributes, such as region. This directly addresses the security characteristic of a data workload by ensuring that users can only see data they are authorized to view, without requiring application-level changes.
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.
Concurrency
Why it's wrong here
RLS does not control concurrency; it controls access.
Consistency
Why it's wrong here
Consistency is about data integrity, not access control.
Security
Why this is correct
RLS is a security feature that restricts data access based on user identity.
Related concept
Read the scenario before looking for a memorised answer.
Durability
Why it's wrong here
Durability refers to data persistence after transactions.
Common exam traps
The trap here is that candidates confuse security (access control) with concurrency (multi-user access) or consistency (data integrity), because RLS involves filtering rows during queries, which might superficially resemble managing concurrent access or ensuring data correctness.
Detailed technical explanation
RLS in Azure SQL Database uses a security policy that applies a predicate function (e.g., a table-valued function) to filter rows based on the SESSION_CONTEXT or USER_NAME() of the connecting user. The predicate is evaluated for every query on the table, ensuring that unauthorized rows are never returned, even if the query is executed via a direct SELECT or through a stored procedure. A real-world scenario is a multinational company where sales managers in Europe should only see European sales data, while managers in Asia see only Asian data, without duplicating tables or views.
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: Security — Row-level security (RLS) in Azure SQL Database restricts data access at the database engine level by applying a security predicate that filters rows based on user attributes, such as region. This directly addresses the security characteristic of a data workload by ensuring that users can only see data they are authorized to view, without requiring application-level changes.
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.