The correct answer is to implement row-level security (RLS) with a security policy that filters rows by tenant ID. RLS enforces multi-tenant data isolation directly at the database engine level, using a predicate function that automatically appends a WHERE clause based on the tenant’s SESSION_CONTEXT or USER_NAME. This means that even if a SQL injection vulnerability compromises the application layer, the attacker’s query can only return rows matching their own tenant ID, preventing any cross-tenant data access. On the DP-300 exam, this scenario tests your understanding of defense-in-depth: RLS works regardless of application flaws, unlike application-level filtering which can be bypassed. A common trap is choosing Transparent Data Encryption or Always Encrypted, which protect data at rest or in transit but do not restrict row-level visibility. Memory tip: think “RLS = Row-Level Shield” — it shields each tenant’s rows from every other tenant, even under injection attacks.
DP-300 Implement a secure environment Practice Question
This DP-300 practice question tests your understanding of implement a secure environment. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 deploying Azure SQL Database for a multi-tenant application. Each tenant's data must be isolated. You need to ensure that tenants cannot access each other's data even if there is a SQL injection vulnerability. Which security feature should you implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Implement row-level security (RLS) with a security policy that filters rows by tenant ID.
Row-level security (RLS) is the correct choice because it enforces data isolation at the database engine level by filtering rows based on a tenant ID predicate. Even if a SQL injection vulnerability allows an attacker to execute arbitrary queries, RLS ensures that only rows belonging to the attacker's tenant are returned, preventing cross-tenant data access. This is a defense-in-depth measure that works regardless of application-layer flaws.
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.
✗
Use Always Encrypted to encrypt sensitive columns.
Why it's wrong here
Always Encrypted protects column data but does not prevent access to other rows.
✗
Configure Azure SQL Database auditing to monitor cross-tenant access.
Why it's wrong here
Auditing is detective, not preventive.
✗
Enable Transparent Data Encryption (TDE) on the database.
Why it's wrong here
TDE encrypts the entire database at rest but does not control row access.
✓
Implement row-level security (RLS) with a security policy that filters rows by tenant ID.
Why this is correct
RLS provides row-level isolation.
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-at-rest encryption (TDE or Always Encrypted) with access control, mistakenly believing encryption alone can prevent unauthorized row access during a SQL injection attack.
Detailed technical explanation
How to think about this question
Row-level security in Azure SQL Database uses a security predicate defined as an inline table-valued function (TVF) that is bound to a security policy. The predicate is evaluated for every row returned by a query, and the filter predicate silently suppresses rows that do not satisfy the condition (e.g., TenantID = USER_NAME() or SESSION_CONTEXT(N'TenantId')). This works even if the query is dynamically constructed via SQL injection because the predicate is applied after query parsing but before result set generation, making it immune to direct manipulation by the injected code.
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: Implement row-level security (RLS) with a security policy that filters rows by tenant ID. — Row-level security (RLS) is the correct choice because it enforces data isolation at the database engine level by filtering rows based on a tenant ID predicate. Even if a SQL injection vulnerability allows an attacker to execute arbitrary queries, RLS ensures that only rows belonging to the attacker's tenant are returned, preventing cross-tenant data access. This is a defense-in-depth measure that works regardless of application-layer flaws.
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.