The answer is a view with a WHERE clause filtering by tenant ID, Row-Level Security (RLS) with a security policy, and SESSION_CONTEXT to set the tenant context. These three features achieve multi-tenant row-level security in Azure SQL Database by isolating each tenant’s data at the database layer without requiring application changes. RLS uses a predicate function—often leveraging SESSION_CONTEXT or USER_NAME()—to automatically filter rows based on the tenant’s identity, while a parameterized view provides an additional, explicit isolation layer. On the DP-300 exam, this scenario tests your understanding of tenant isolation features and how they differ from application-level filtering; a common trap is assuming that a simple WHERE clause in application code alone is sufficient, but the exam emphasizes database-enforced security. Remember the mnemonic “V-R-S” for View, RLS, and SESSION_CONTEXT to recall the three required features for tenant isolation.
DP-300 Implement a secure environment Practice Question
This DP-300 practice question tests your understanding of implement a secure environment. 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 configuring a new Azure SQL Database for a multi-tenant SaaS application. You need to ensure that each tenant can only access their own rows. Which THREE features can be used to achieve this?
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 predicate function.
Row-Level Security (RLS) allows you to control access to rows in a database table based on the characteristics of the user executing a query. By creating a security policy with a predicate function that filters rows by tenant ID (e.g., using SESSION_CONTEXT or USER_NAME()), you can ensure each tenant only sees their own data without changing the application's query logic.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Always Encrypted with deterministic encryption.
Why it's wrong here
Encryption does not filter rows.
✓
Row-Level Security (RLS) with a predicate function.
Why this is correct
RLS filters rows based on the user's context.
Related concept
Read the scenario before looking for a memorised answer.
✓
Application logic that filters queries by tenant ID.
Why this is correct
The application can enforce tenant isolation.
Related concept
Read the scenario before looking for a memorised answer.
✗
Dynamic Data Masking for the tenant ID column.
Why it's wrong here
Masking hides data but does not prevent access.
✓
A view that includes a WHERE clause filtering by tenant ID.
Why this is correct
Views can restrict access to specific rows.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse data masking (which only hides column values) with row-level access control, or assume that encryption alone can enforce row filtering, when in fact RLS, application logic, or views with WHERE clauses are the correct mechanisms for multi-tenant row isolation.
Detailed technical explanation
How to think about this question
RLS in Azure SQL Database uses a security policy that applies a predicate function (inline table-valued function) to filter rows at query execution time, leveraging the query processor to inject the predicate into the query plan. The predicate can use SESSION_CONTEXT(N'TenantId') to retrieve the tenant ID set by the application, ensuring that even if a user tries to join or subquery across tenants, the filter is enforced. This approach is transparent to the application and can be combined with application logic (Option C) or views (Option E) for defense in depth.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
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.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this DP-300 question in full detail.
Implement a secure environment — This question tests Implement a secure environment — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Row-Level Security (RLS) with a predicate function. — Row-Level Security (RLS) allows you to control access to rows in a database table based on the characteristics of the user executing a query. By creating a security policy with a predicate function that filters rows by tenant ID (e.g., using SESSION_CONTEXT or USER_NAME()), you can ensure each tenant only sees their own data without changing the application's query logic.
What should I do if I get this DP-300 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
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 →
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.
This DP-300 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-300 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.