The answer is that the two required configurations are granting Key Vault permissions to the managed identity and enabling the managed identity on the Azure Function. This works because a managed identity, either system-assigned or user-assigned, provides an Azure AD-authenticated identity for the function app, eliminating the need for client secrets or certificates. The identity obtains an Azure AD access token to authenticate to Key Vault, but without explicit permissions—set via an access policy or RBAC role—the token-based authentication fails with a 403 Forbidden error. On the AZ-500 exam, this scenario tests your understanding of identity-based authentication versus key-based secrets, and a common trap is assuming the function app’s own service principal is automatically authorized. Remember the two-step rule: identity first, then permissions—think “Who am I?” followed by “What can I access?” A useful mnemonic is “MI + KV = Token + Policy,” ensuring you always pair the managed identity with the Key Vault access grant.
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.
A managed identity is used by an Azure Function to access Key Vault. Which two configurations are required?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
A system-assigned or user-assigned managed identity enabled on the function app
Option B is correct because a managed identity (either system-assigned or user-assigned) provides an Azure AD-authenticated identity for the function app, eliminating the need for credentials like client secrets. This identity is used to obtain an Azure AD access token for authenticating to Key Vault. Option D is also required because the managed identity must be granted explicit Key Vault permissions (e.g., via an access policy or RBAC role) to read secrets; without these permissions, token-based authentication will fail with a 403 Forbidden error.
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.
✗
A client secret stored in the function app settings
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
✓
A system-assigned or user-assigned managed identity enabled on the function app
Why this is correct
Correct for the stated requirement.
Related concept
Read the scenario before looking for a memorised answer.
✗
A public IP address on the function app
Why it's wrong here
This does not meet the stated requirement as directly as the correct option.
✓
Key Vault permissions granted to that managed identity
Why this is correct
Correct for the stated requirement.
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 assume a client secret (Option A) is required for any Azure AD authentication, failing to recognize that managed identities provide a passwordless, credential-free authentication mechanism via Azure AD tokens.
Detailed technical explanation
How to think about this question
Under the hood, the Azure Function runtime uses the Azure Instance Metadata Service (IMDS) endpoint at 169.254.169.254 to request an access token for the managed identity's service principal. The token is then presented to Key Vault's OAuth 2.0 endpoint; Key Vault validates the token and checks the associated access policy or RBAC role assignment. A subtle behavior: if the function app uses a user-assigned managed identity, you must explicitly set the 'AZURE_CLIENT_ID' environment variable to the identity's client ID, otherwise the runtime defaults to the system-assigned identity.
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: A system-assigned or user-assigned managed identity enabled on the function app — Option B is correct because a managed identity (either system-assigned or user-assigned) provides an Azure AD-authenticated identity for the function app, eliminating the need for credentials like client secrets. This identity is used to obtain an Azure AD access token for authenticating to Key Vault. Option D is also required because the managed identity must be granted explicit Key Vault permissions (e.g., via an access policy or RBAC role) to read secrets; without these permissions, token-based authentication will fail with a 403 Forbidden error.
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.