The correct answer is the Service Bus connector with managed identity authentication. This is the right choice because it enables your Logic App to authenticate to Azure Service Bus using an Azure AD managed identity, completely removing the need to manage secrets, connection strings, or SAS tokens. By leveraging Azure RBAC, this approach grants fine-grained, least-privilege access directly to the Service Bus queue, which is exactly what the scenario demands when the queue is secured using managed identity. On the AZ-204 exam, this question tests your understanding of modern, secure authentication patterns for Azure integrations—a common trap is choosing a connector that uses a connection string or SAS token, which would violate the managed identity requirement. Remember the memory tip: “No keys, just identity—RBAC sets you free.” This reinforces that managed identity paired with Azure RBAC is the secure, exam-approved path for Logic App to Service Bus communication.
AZ-204 Practice Question: Connect to and consume Azure services and third-party services
This AZ-204 practice question tests your understanding of connect to and consume azure services and third-party services. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 building an Azure Logic App that processes orders. When an order is placed, the Logic App must send a message to an Azure Service Bus queue. The queue is secured using managed identity. Which connector action should you use?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Service Bus connector with managed identity authentication
The Service Bus connector with managed identity authentication is correct because it allows the Logic App to authenticate to the Azure Service Bus queue using an Azure AD managed identity, eliminating the need for secrets or SAS tokens. This is the recommended approach for securing Service Bus resources when using Azure services, as it leverages Azure RBAC for fine-grained access control and aligns with the principle of least privilege.
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.
✗
HTTP action with SAS token
Why it's wrong here
Incorrect. Using an HTTP action with a SAS token requires managing the token and is less secure than using a managed identity.
✓
Service Bus connector with managed identity authentication
Why this is correct
Correct. The Service Bus connector has built-in support for managed identity, allowing secure authentication without secrets.
Related concept
Read the scenario before looking for a memorised answer.
✗
Azure Functions connector
Why it's wrong here
Incorrect. The Azure Functions connector is used to invoke a function, not to send a message to Service Bus directly.
✗
Event Grid connector
Why it's wrong here
Incorrect. Event Grid connector is for publishing events to Event Grid, not for sending messages to Service Bus.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse the HTTP action with SAS token as a valid way to use managed identity, but managed identity requires Azure AD authentication, not SAS, and the Service Bus connector explicitly supports this authentication type.
Detailed technical explanation
How to think about this question
Under the hood, the Service Bus connector with managed identity authentication uses OAuth 2.0 token exchange via Azure AD, where the Logic App's system-assigned or user-assigned managed identity requests an access token for the 'https://servicebus.azure.net' audience. This token is then presented to the Service Bus endpoint, which validates it against Azure RBAC roles like 'Azure Service Bus Data Sender' to authorize the send operation. In a real-world scenario, this approach simplifies compliance by avoiding key rotation and enabling centralized access policies across multiple Logic Apps.
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.
Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Service Bus connector with managed identity authentication — The Service Bus connector with managed identity authentication is correct because it allows the Logic App to authenticate to the Azure Service Bus queue using an Azure AD managed identity, eliminating the need for secrets or SAS tokens. This is the recommended approach for securing Service Bus resources when using Azure services, as it leverages Azure RBAC for fine-grained access control and aligns with the principle of least privilege.
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.