AZ-204 Practice Question: Connect to and consume Azure services and third-party services
You are using Azure Logic Apps to orchestrate a workflow that calls a third-party API. The API occasionally returns HTTP 429 (Too Many Requests). How should you handle this to ensure the workflow completes successfully without manual intervention?
⚠ Common exam trap
A common mix-up: candidates confuse concurrency control (Option B) with retry logic, mistakenly thinking limiting parallel requests prevents 429 errors, but 429 can still occur from a single request if the API's rate limit is per-request or per-account, not per-concurrent-call.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure a retry policy on the HTTP action with exponential backoff.
Azure Logic Apps supports configuring a retry policy on HTTP actions, and using exponential backoff is the standard approach to handle HTTP 429 responses. The retry policy automatically waits for increasing intervals between attempts, respecting the 'Retry-After' header if present, which allows the third-party API to recover from rate limiting without manual intervention.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Increase the timeout value for the HTTP request.
Why it's wrong here
Increasing the timeout value for an HTTP request only extends the duration a Logic App waits for a response before declaring the single attempt as failed. It does not introduce any mechanism to reattempt the request if it encounters a transient error like an HTTP 429 (Too Many Requests). This action would merely prolong the wait time for a potentially failing request, rather than providing a recovery strategy.
- ✗
Change the concurrency setting to 1 to avoid multiple requests.
Why it's wrong here
Changing the concurrency setting to 1 limits the number of workflow instances that can run in parallel, which might reduce the overall load generated by the Logic App. However, this setting does not implement a retry mechanism for individual HTTP actions that fail with a 429 error. A single request from a non-concurrent workflow could still hit a rate limit and fail permanently without a specific retry policy configured.
- ✗
Use a webhook action instead of HTTP.
Why it's wrong here
Using a webhook action instead of an HTTP action fundamentally changes the interaction pattern; a webhook is primarily designed for receiving callbacks from an external service, making the Logic App a listener. It is not intended for initiating outbound requests to an external API and does not inherently provide retry capabilities for such outbound calls. The core problem of handling a rate-limited outbound request remains unaddressed by this change.
- ✓
Configure a retry policy on the HTTP action with exponential backoff.
Why this is correct
Configuring a retry policy on the HTTP action with exponential backoff is the correct and most robust solution for handling transient errors like HTTP 429 (Too Many Requests). This policy automatically reattempts the failed request after a calculated delay, which increases with each subsequent retry, preventing the Logic App from overwhelming the target service further. Exponential backoff allows the external service time to recover from the high load, significantly improving the workflow's resiliency.
Go deeper
Related to this question
About these practice questions
This AZ-204 question is part of Courseiva's 881-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
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.