The correct choice is exponential backoff with jitter and a maximum retry limit because it progressively increases the delay between HTTP retries, preventing the client from overwhelming a third-party shipping API during partial outages. Jitter randomizes those delays to avoid the thundering herd problem, where multiple clients retry simultaneously and amplify server strain, while the maximum retry limit ensures the system stops retrying after a set number of attempts, preserving resources and enabling graceful degradation. On the Microsoft Azure Developer Associate AZ-204 exam, this pattern tests your understanding of resilient HTTP communication and transient fault handling, often appearing in scenarios involving external API calls or Azure services like Azure Functions and Logic Apps. A common trap is choosing simple fixed-interval retries, which ignore server recovery time and cause congestion. Memory tip: think “Back off, shake it off, then stop”—exponential backoff, jitter, and a max limit.
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. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. 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.
An application calls a third-party shipping API through HTTP. The developer must implement retries without overwhelming the remote system during partial outages. Which retry pattern is best?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Exponential backoff with jitter and a maximum retry limit
Exponential backoff with jitter and a maximum retry limit is the best pattern because it progressively increases the delay between retries, preventing the client from overwhelming the third-party shipping API during partial outages. Jitter randomizes the delay to avoid thundering herd problems where multiple clients retry simultaneously, and the maximum retry limit ensures the system does not retry indefinitely, preserving resources and allowing for graceful degradation.
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.
✗
Immediate infinite retries
Why it's wrong here
Infinite tight retries can amplify outages.
✗
Retry only after restarting the application
Why it's wrong here
Restarts are not a controlled resilience pattern.
✓
Exponential backoff with jitter and a maximum retry limit
Why this is correct
Backoff with jitter reduces retry storms and gives the remote service time to recover.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Disable all timeout settings
Why it's wrong here
Missing timeouts can cause thread starvation and cascading failures.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may choose immediate infinite retries (Option A) thinking it ensures delivery, but they overlook the risk of overwhelming the remote system and violating rate limits, which is explicitly tested in the context of third-party API consumption.
Detailed technical explanation
How to think about this question
Exponential backoff typically uses a formula like delay = base_delay * (2^attempt) + jitter, where base_delay might be 1 second and jitter is a random value up to a certain range (e.g., ±500ms). The maximum retry limit (commonly 3-5 attempts) prevents infinite loops and aligns with the 'Circuit Breaker' pattern to stop calls when the failure rate exceeds a threshold. In Azure, the Polly library or built-in retry policies in HttpClientFactory (e.g., AddPolicyHandler) implement this pattern, and the jitter is critical to avoid the 'thundering herd' problem when many instances retry after a transient outage.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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: Exponential backoff with jitter and a maximum retry limit — Exponential backoff with jitter and a maximum retry limit is the best pattern because it progressively increases the delay between retries, preventing the client from overwhelming the third-party shipping API during partial outages. Jitter randomizes the delay to avoid thundering herd problems where multiple clients retry simultaneously, and the maximum retry limit ensures the system does not retry indefinitely, preserving resources and allowing for graceful degradation.
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.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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 →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. An application calls a Service Bus topic through HTTP. The developer must implement retries without overwhelming the remote system during partial outages. Which retry pattern is best?
medium
A.Disable all timeout settings
B.Immediate infinite retries
C.Retry only after restarting the application
✓ D.Exponential backoff with jitter and a maximum retry limit
Why D: Exponential backoff with jitter and a maximum retry limit is the best pattern because it progressively increases the delay between retries, preventing the client from overwhelming the Service Bus topic during partial outages. The jitter randomizes the delay to avoid thundering herd problems, while the maximum retry limit ensures the system doesn't retry indefinitely, aligning with Azure's recommended retry guidance for HTTP-based calls to Service Bus.
Variation 2. An application calls a Event Grid event stream through HTTP. The developer must implement retries without overwhelming the remote system during partial outages. Which retry pattern is best?
medium
A.Immediate infinite retries
B.Retry only after restarting the application
C.Disable all timeout settings
✓ D.Exponential backoff with jitter and a maximum retry limit
Why D: Exponential backoff with jitter and a maximum retry limit is the best pattern because it prevents overwhelming the Event Grid endpoint during partial outages by progressively increasing wait times between retries, while jitter randomizes those intervals to avoid thundering herd problems. The maximum retry limit ensures the system does not retry indefinitely, aligning with Event Grid's own retry policy (which uses exponential backoff up to 30 minutes and a max of 30 retries for HTTP 5xx errors). This balances resilience with resource protection.
Last reviewed: Jun 11, 2026
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.
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.