The answer is to enable a system-assigned managed identity on the function app and assign the 'Azure Service Bus Data Receiver' role to that identity. This configuration is essential because managed identity allows the Azure Function to authenticate to Service Bus using Azure AD tokens instead of connection strings or secrets, eliminating credential management overhead. On the AZ-204 exam, this scenario tests your understanding of secretless authentication patterns and Azure RBAC for messaging services—a common trap is confusing the 'Sender' role with 'Receiver' when the function only processes messages. Remember that the managed identity must be system-assigned (not user-assigned) for the simplest setup, and the role must match the operation: Data Receiver for consuming, Data Sender for publishing. A helpful memory tip is "Identity first, role second—Receiver reads the queue."
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.
You are developing an Azure Function that processes messages from an Azure Service Bus queue. The function must use a managed identity to authenticate to the Service Bus to avoid managing secrets. Which configuration step is essential for this setup?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable system-assigned managed identity on the function app and assign the 'Azure Service Bus Data Receiver' role to the identity
Option C is correct because using a managed identity eliminates the need to manage secrets or connection strings. By enabling a system-assigned managed identity on the function app and assigning the 'Azure Service Bus Data Receiver' role to that identity, the function can authenticate to Azure Service Bus via Azure AD (OAuth 2.0) without any stored credentials. This is the recommended approach for secure, secretless authentication in Azure Functions.
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.
✗
Store the Service Bus connection string in the function app settings
Why it's wrong here
Using connection strings defeats the purpose of avoiding secrets.
✗
Create a Key Vault reference to the connection string
Why it's wrong here
Key Vault still involves secrets; managed identity is preferred.
✓
Enable system-assigned managed identity on the function app and assign the 'Azure Service Bus Data Receiver' role to the identity
Why this is correct
This allows the function to authenticate without secrets.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use the Service Bus SDK with a SharedAccessSignatureToken
Why it's wrong here
This requires a SAS token, which is a secret.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often think storing secrets in Key Vault (Option B) is sufficient for secretless authentication, but Key Vault references still involve retrieving a secret at runtime, whereas managed identity completely removes the need for any secret.
Detailed technical explanation
How to think about this question
Under the hood, the managed identity provides an Azure AD token that the Service Bus SDK (Azure.Messaging.ServiceBus) can acquire automatically via DefaultAzureCredential. The 'Azure Service Bus Data Receiver' role grants the identity permission to receive messages from queues or subscriptions, and this role assignment is done at the Service Bus namespace scope. A subtle behavior is that the managed identity must be enabled before the role assignment, and the function app's identity must be the principal in the role assignment; otherwise, authentication will fail with a 401 error.
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: Enable system-assigned managed identity on the function app and assign the 'Azure Service Bus Data Receiver' role to the identity — Option C is correct because using a managed identity eliminates the need to manage secrets or connection strings. By enabling a system-assigned managed identity on the function app and assigning the 'Azure Service Bus Data Receiver' role to that identity, the function can authenticate to Azure Service Bus via Azure AD (OAuth 2.0) without any stored credentials. This is the recommended approach for secure, secretless authentication in Azure Functions.
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.