The answer is to use Microsoft Entra ID authentication with the managed identity configured as a contained database user. This is correct because the managed identity acts as an automatically managed service principal in Entra ID, which you map to a contained database user using the T-SQL command `CREATE USER [<identity-name>] FROM EXTERNAL PROVIDER`. This setup enables token-based authentication via OAuth 2.0, allowing the application to connect to Azure SQL Database without any SQL logins or passwords—the managed identity itself provides the secure credential. On the AZ-204 exam, this scenario tests your understanding of passwordless authentication patterns and how to enforce least-privilege access for Azure resources. A common trap is confusing a server-level login with a contained database user; remember that the contained user lives inside the database, not the logical server, which is why no SQL login is needed. Memory tip: think "EXTERNAL PROVIDER equals no password required."
AZ-204 Implement Azure security Practice Question
This AZ-204 practice question tests your understanding of implement azure security. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 company stores customer payment data in an Azure SQL Database. You need to ensure that only the application's managed identity can access the database, and no SQL logins or passwords are used. Which authentication method should you configure?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use Microsoft Entra ID authentication with the managed identity configured as a contained database user
Option B is correct because configuring the managed identity as a contained database user in Azure SQL Database using Microsoft Entra ID authentication allows the application to authenticate without any SQL logins or passwords. The managed identity provides an automatically managed service principal in Entra ID, which can be mapped to a contained database user (CREATE USER [<identity-name>] FROM EXTERNAL PROVIDER). This enables token-based authentication using OAuth 2.0, ensuring that only the application's identity can access the database.
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.
✗
SQL Server authentication with a strong password stored in Key Vault
Why it's wrong here
This still uses SQL authentication, which requires a password and is not managed identity based.
✓
Use Microsoft Entra ID authentication with the managed identity configured as a contained database user
Why this is correct
Managed identity can be granted access to Azure SQL via Microsoft Entra ID authentication without credentials.
Related concept
Read the scenario before looking for a memorised answer.
✗
Enable Transparent Data Encryption (TDE) and use the database's certificate
Why it's wrong here
TDE encrypts data at rest but does not handle authentication.
✗
Configure the Azure SQL firewall to allow only the application's outbound IP
Why it's wrong here
Firewall rules restrict network access but do not authenticate the application's identity.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse network-level security (firewall rules) or data encryption (TDE) with authentication, failing to recognize that only Entra ID authentication with a managed identity eliminates the need for SQL logins and passwords entirely.
Detailed technical explanation
How to think about this question
Under the hood, when using a managed identity with Azure SQL, the application acquires an access token from the Microsoft Entra ID endpoint (https://login.microsoftonline.com/{tenant-id}/oauth2/token) using the managed identity's client ID. This token is then passed to Azure SQL Database via the connection string parameter 'Authentication=Active Directory Managed Identity'. The database validates the token against the contained database user created from the managed identity's service principal, enabling fine-grained permission control at the database level without any stored credentials.
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-204 question in full detail.
Implement Azure security — This question tests Implement Azure security — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use Microsoft Entra ID authentication with the managed identity configured as a contained database user — Option B is correct because configuring the managed identity as a contained database user in Azure SQL Database using Microsoft Entra ID authentication allows the application to authenticate without any SQL logins or passwords. The managed identity provides an automatically managed service principal in Entra ID, which can be mapped to a contained database user (CREATE USER [<identity-name>] FROM EXTERNAL PROVIDER). This enables token-based authentication using OAuth 2.0, ensuring that only the application's identity can access the database.
What should I do if I get this AZ-204 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-204 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-204 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.