The answer is a system-assigned managed identity with Key Vault access granted by RBAC or an access policy. This pattern is correct because it allows the Azure VM to authenticate to Azure Key Vault without storing any credentials in code or configuration, using the Azure Instance Metadata Service (IMDS) endpoint at 169.254.169.254 to obtain an access token. Azure automatically creates a service principal for the VM in Azure AD, and access to secrets is controlled by assigning the Key Vault Secrets User RBAC role or configuring a Key Vault access policy for that identity. On the AZ-500 exam, this scenario tests your understanding of identity-based authentication for Azure resources, often appearing as a trap where candidates might incorrectly suggest using service principals with client secrets or certificates. The key memory tip is "no stored secrets, just system-assigned tokens"—if the question emphasizes eliminating credentials from code, always default to a managed identity.
AZ-500 Manage identity and access Practice Question
This AZ-500 practice question tests your understanding of manage identity and access. 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.
An application hosted on an Azure VM needs to read secrets from Key Vault without storing credentials. Which identity pattern should be used?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
System-assigned managed identity with Key Vault access granted by RBAC or access policy
A system-assigned managed identity enables an Azure VM to authenticate to Azure Key Vault without storing any credentials in code or configuration. Azure automatically creates a service principal for the VM in Azure AD, and the VM can obtain an access token from the Azure Instance Metadata Service (IMDS) endpoint (169.254.169.254) to authenticate to Key Vault. Access to secrets is then controlled by assigning RBAC roles (e.g., Key Vault Secrets User) or configuring a Key Vault access policy for that identity, eliminating the need for any stored secrets.
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.
✓
System-assigned managed identity with Key Vault access granted by RBAC or access policy
Why this is correct
Correct for the stated requirement.
Related concept
Read the scenario before looking for a memorised answer.
✗
Client secret stored in appsettings.json
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
✗
Shared access signature stored as an environment variable
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
✗
A user account excluded from MFA
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse managed identities with other credential-based patterns (like client secrets or SAS tokens) and fail to recognize that the question explicitly requires 'without storing credentials,' which only a managed identity satisfies.
Detailed technical explanation
How to think about this question
Under the hood, the Azure Instance Metadata Service (IMDS) endpoint at 169.254.169.254 provides an OAuth 2.0 token for the managed identity when the VM requests one with the resource parameter set to 'https://vault.azure.net'. The token is signed by Azure AD and includes the managed identity's service principal object ID, which Key Vault validates against its access policies or RBAC assignments. A subtle behavior is that the token is cached by the Azure SDK and automatically refreshed, but if the VM is moved to a different resource group or subscription, the managed identity must be re-enabled to update the service principal.
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.
Manage identity and access — This question tests Manage identity and access — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: System-assigned managed identity with Key Vault access granted by RBAC or access policy — A system-assigned managed identity enables an Azure VM to authenticate to Azure Key Vault without storing any credentials in code or configuration. Azure automatically creates a service principal for the VM in Azure AD, and the VM can obtain an access token from the Azure Instance Metadata Service (IMDS) endpoint (169.254.169.254) to authenticate to Key Vault. Access to secrets is then controlled by assigning RBAC roles (e.g., Key Vault Secrets User) or configuring a Key Vault access policy for that identity, eliminating the need for any stored secrets.
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.