Quick Answer
The answer is USER_NAME(). This function is the correct predicate function for row-level security with Azure AD authentication because it returns the database principal name derived from the Azure AD token, which directly maps to the authenticated user’s identity within Azure SQL Database. In an RLS security policy, the predicate must evaluate to a Boolean value that filters rows based on this user identity, and USER_NAME() reliably captures the actual Azure AD user, unlike SUSER_NAME() or SESSION_USER, which may return the login or context user rather than the database-level principal. On the Microsoft Azure Database Administrator Associate DP-300 exam, this question tests your understanding of how RLS integrates with Azure AD authentication—a common trap is confusing USER_NAME() with SUSER_SNAME(), but remember that RLS predicates operate at the database principal level, not the server login level. A helpful memory tip: think “User = Database User” for RLS, so USER_NAME() is your go-to function when filtering by Azure AD identity.
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 implementing row-level security (RLS) in Azure SQL Database to restrict access to sales data based on the user's Azure AD identity. Which function should you use in the security policy?
USER_NAME()
Correct: Returns the database user name, which can be an Azure AD user.
SESSION_USER()
Why wrong: Incorrect: Returns the current session's user name.
SUSER_SNAME()
Why wrong: Incorrect: Returns the login name, not the database user.
CURRENT_USER()
Why wrong: Incorrect: Returns the current context user.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
USER_NAME()
In Azure SQL Database, row-level security (RLS) predicates must evaluate to a Boolean value based on the current user's identity. USER_NAME() returns the database principal name derived from the Azure AD token, which is the correct function to use when filtering rows by the user's Azure AD identity. The other functions either return the login name, the session user, or the current context user, which may not reflect the actual Azure AD user in an RLS predicate.
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.
USER_NAME()
Why this is correct
Correct: Returns the database user name, which can be an Azure AD user.
Related concept
Read the scenario before looking for a memorised answer.
SESSION_USER()
Why it's wrong here
Incorrect: Returns the current session's user name.
SUSER_SNAME()
Why it's wrong here
Incorrect: Returns the login name, not the database user.
CURRENT_USER()
Why it's wrong here
Incorrect: Returns the current context user.
Common exam traps
The trap here is that candidates often confuse USER_NAME() with SUSER_SNAME() or CURRENT_USER(), mistakenly thinking that the server-level login name or the current context user is the correct identity for row-level filtering, when in fact RLS in Azure SQL Database requires the database-level user name returned by USER_NAME().
Detailed technical explanation
Under the hood, Azure SQL Database maps Azure AD tokens to database users via contained database authentication. The USER_NAME() function returns the name of the database principal that was resolved from the token, which is exactly what the RLS predicate needs to compare against a user column. A subtle behavior is that if the Azure AD user is a member of an Azure AD group that has been mapped to a database role, USER_NAME() returns the individual user name, not the group name, so the RLS predicate must be designed to handle group membership if needed.
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.
Implement a secure environment — study guide chapter
Learn the concepts, then practise the questions
Implement a secure environment practice questions
Targeted practice on this topic area only
All DP-300 questions
953 questions across all exam domains
Microsoft Azure Database Administrator Associate DP-300 study guide
Full concept coverage aligned to exam objectives
DP-300 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-300 questions linked to Plan and configure a high availability and disaster recovery environment.
Practise DP-300 questions linked to Plan and implement data platform resources.
Practise DP-300 questions linked to Monitor, configure, and optimize database resources.
Practise DP-300 questions linked to Configure and manage automation of tasks.
Practise DP-300 questions linked to Plan and configure high availability and disaster recovery.
Practise DP-300 questions linked to Implement a secure environment.
Practise DP-300 questions linked to DP-300 fundamentals.
Practise DP-300 questions linked to DP-300 scenario.
Practise DP-300 questions linked to DP-300 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Implement a secure environment — This question tests Implement a secure environment — Read the scenario before looking for a memorised answer..
The correct answer is: USER_NAME() — In Azure SQL Database, row-level security (RLS) predicates must evaluate to a Boolean value based on the current user's identity. USER_NAME() returns the database principal name derived from the Azure AD token, which is the correct function to use when filtering rows by the user's Azure AD identity. The other functions either return the login name, the session user, or the current context user, which may not reflect the actual Azure AD user in an RLS predicate.
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 11, 2026
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.