The answer is the HTTP connector. This is the correct choice because the HTTP connector in Azure Logic Apps natively supports the OAuth 2.0 client credentials grant with minimal configuration, allowing you to directly set the authentication type to 'Active Directory OAuth' and provide the tenant ID, client ID, client secret, and audience or resource URI—no custom code or additional connectors are needed. On the Microsoft Azure Developer Associate AZ-204 exam, this scenario tests your understanding of how to securely integrate Logic Apps with external APIs using modern authentication flows, and a common trap is reaching for the Azure AD connector or a managed API connector when the generic HTTP connector is simpler and sufficient. Remember the memory tip: for client credentials in Logic Apps, think "HTTP + AAD OAuth" to avoid overcomplicating the integration.
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. 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 company uses Azure Logic Apps to automate business processes. They need to call an external REST API that requires OAuth 2.0 client credentials grant. Which connector should they use with minimal configuration?
Correct. The HTTP connector can be configured with OAuth 2.0 authentication, including client credentials, with minimal custom setup.
B
HTTP + Swagger connector
Why wrong: Incorrect. This connector is used when the API exposes a Swagger definition to automatically generate triggers and actions; OAuth is still possible but adds unnecessary steps.
C
Azure Functions connector
Why wrong: Incorrect. The Azure Functions connector calls an Azure Function, not an external REST API directly. It adds extra compute overhead.
D
Custom connector
Why wrong: Incorrect. Custom connectors are for wrapping APIs that are not available in the connector gallery; using the HTTP connector is simpler for REST APIs with OAuth.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
HTTP connector
The HTTP connector in Azure Logic Apps supports OAuth 2.0 client credentials grant natively with minimal configuration. You can directly set the authentication type to 'Active Directory OAuth' and provide the tenant ID, client ID, client secret, and audience/resource URI. This avoids the need for custom code or additional connectors.
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 connector
Why this is correct
Correct. The HTTP connector can be configured with OAuth 2.0 authentication, including client credentials, with minimal custom setup.
Related concept
Read the scenario before looking for a memorised answer.
✗
HTTP + Swagger connector
Why it's wrong here
Incorrect. This connector is used when the API exposes a Swagger definition to automatically generate triggers and actions; OAuth is still possible but adds unnecessary steps.
✗
Azure Functions connector
Why it's wrong here
Incorrect. The Azure Functions connector calls an Azure Function, not an external REST API directly. It adds extra compute overhead.
✗
Custom connector
Why it's wrong here
Incorrect. Custom connectors are for wrapping APIs that are not available in the connector gallery; using the HTTP connector is simpler for REST APIs with OAuth.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often overthink and choose a custom connector or Swagger-based option, not realizing the built-in HTTP connector already supports OAuth 2.0 client credentials with minimal setup.
Detailed technical explanation
How to think about this question
The HTTP connector supports the 'Active Directory OAuth' authentication type, which implements the OAuth 2.0 client credentials grant (RFC 6749 section 4.4). Under the hood, Logic Apps automatically obtains an access token from the Azure AD token endpoint using the provided client ID and secret, then attaches it as a Bearer token in the Authorization header. This is ideal for server-to-server scenarios where user interaction is not required.
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: HTTP connector — The HTTP connector in Azure Logic Apps supports OAuth 2.0 client credentials grant natively with minimal configuration. You can directly set the authentication type to 'Active Directory OAuth' and provide the tenant ID, client ID, client secret, and audience/resource URI. This avoids the need for custom code or additional connectors.
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.