The answer is to create a contained database user for the managed identity in the SQL database and assign it the appropriate database role, such as db_datareader. This is required because Azure SQL Database uses Azure AD authentication at the server level, but individual database access is governed by contained database users that map an Azure AD identity—like a system-assigned managed identity—to a database principal. Without this contained user, the managed identity cannot authenticate to the database, even if it has server-level permissions. On the AZ-500 exam, this scenario tests your understanding of the two-step process: first, enabling Azure AD authentication on the SQL server, then creating the contained user and granting roles within the database itself. A common trap is thinking that assigning the managed identity a role at the server level (like SQL Contributor) is sufficient, but database-level permissions require the contained user. Remember the mnemonic: “Server for sign-in, database for permissions”—the managed identity must be mapped inside the database to actually read or write data.
AZ-500 Secure compute, storage, and databases Practice Question
This AZ-500 practice question tests your understanding of secure compute, storage, and databases. 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.
A company has an Azure SQL Database server. They want to allow an Azure Function with a system-assigned managed identity to access the database by using Azure Active Directory (Azure AD) authentication. Which two configurations are required to grant this access? (Choose two.)
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Assign the managed identity the 'db_datareader' role in the database.
Option A is correct because assigning the managed identity the 'db_datareader' role in the database grants it read permissions on all tables and views, which is a common requirement for an Azure Function accessing data. Option B is correct because a contained database user must be created for the managed identity in the SQL database, mapping the Azure AD identity to a database principal that can be granted permissions. Without this contained user, the managed identity cannot authenticate to the database via Azure AD.
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.
✓
Assign the managed identity the 'db_datareader' role in the database.
Why this is correct
This grants the necessary read permissions to the managed identity within the database.
Related concept
Read the scenario before looking for a memorised answer.
✓
Create a contained database user for the managed identity in the SQL database.
Why this is correct
A contained database user mapped to the managed identity is required to authenticate via Azure AD.
Related concept
Read the scenario before looking for a memorised answer.
✗
Add the managed identity as an Azure AD admin for the SQL server.
Why it's wrong here
Adding the managed identity as an Azure AD admin grants server-level admin privileges, which is not required and is overly permissive.
✗
Enable Azure AD-only authentication on the SQL server.
Why it's wrong here
Azure AD-only authentication is an optional setting that restricts SQL authentication, but it is not required for managed identity access.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse server-level Azure AD admin assignment (Option C) with the necessary database-level contained user creation, assuming admin rights are required for any Azure AD authentication, when in fact a contained user with minimal roles is sufficient and more secure.
Detailed technical explanation
How to think about this question
Under the hood, Azure SQL Database uses a two-step process for managed identity access: first, the managed identity must be represented as a contained database user (created via the CREATE USER statement with the FROM EXTERNAL PROVIDER clause), and second, that user must be granted specific database-level permissions (e.g., db_datareader) via role membership. The authentication flow uses the OAuth 2.0 token exchange, where the managed identity obtains an access token from Azure AD (via the instance metadata service endpoint at 169.254.169.254) and presents it to SQL Database, which validates the token against the contained user mapping.
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 AZ-500 question in full detail.
Secure compute, storage, and databases — This question tests Secure compute, storage, and databases — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Assign the managed identity the 'db_datareader' role in the database. — Option A is correct because assigning the managed identity the 'db_datareader' role in the database grants it read permissions on all tables and views, which is a common requirement for an Azure Function accessing data. Option B is correct because a contained database user must be created for the managed identity in the SQL database, mapping the Azure AD identity to a database principal that can be granted permissions. Without this contained user, the managed identity cannot authenticate to the database via Azure AD.
What should I do if I get this AZ-500 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 AZ-500 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 AZ-500 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.