Quick Answer
The answer is to implement retry logic with exponential backoff, as this pattern directly addresses transient failures by automatically reattempting failed operations with progressively increasing delays. In Durable Functions, this is built into the CallActivityWithRetryAsync method, which allows you to specify retry count, interval, and backoff coefficient—ensuring that temporary network blips or API throttling don’t derail the entire orchestration. On the AZ-204 exam, this question tests your understanding of how Durable Functions handle fault tolerance within orchestrations, often contrasting retry logic with patterns like circuit breaker (which prevents calls to a downed service but doesn’t retry) or saga (which manages distributed transactions). A common trap is confusing retry with the circuit breaker pattern—remember that retry handles transient faults by trying again, while circuit breaker stops calls to a persistently failing service. Memory tip: think “Backoff and Retry” for temporary glitches, “Break and Stop” for permanent failures.
This AZ-204 practice question tests your understanding of connect to and consume azure services and third-party services. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 uses Azure Functions with a Durable Functions extension to orchestrate a workflow. The workflow calls multiple external APIs. The developer needs to handle transient failures when calling these APIs. Which pattern should the developer implement?
Implement retry logic with exponential backoff
Exponential backoff is a standard approach for handling transient failures.
Use a saga pattern
Why wrong: Saga pattern is for distributed transactions, not for retries.
Use a request-reply pattern
Why wrong: Request-reply is for messaging, not for failure handling.
Use a circuit breaker pattern
Why wrong: Circuit breaker prevents calls but does not retry.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Implement retry logic with exponential backoff
Option A is correct because automatic retry with exponential backoff is a best practice for transient faults. Option B is incorrect because circuit breaker is for preventing repeated calls to a failing service, but it doesn't handle retries. Option C is incorrect because the request-reply pattern is for messaging, not for handling failures. Option D is incorrect because the saga pattern is for distributed transactions, not for retries.
Key principle: NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Implement retry logic with exponential backoff
Why this is correct
Exponential backoff is a standard approach for handling transient failures.
Related concept
Static NAT maps one inside address to one outside address.
Use a saga pattern
Why it's wrong here
Saga pattern is for distributed transactions, not for retries.
Use a request-reply pattern
Why it's wrong here
Request-reply is for messaging, not for failure handling.
Use a circuit breaker pattern
Why it's wrong here
Circuit breaker prevents calls but does not retry.
Common exam traps
NAT is not only about the public address. The inside/outside interface roles and the ACL or rule that matches traffic are just as important.
Detailed technical explanation
NAT questions usually test address translation, overload/PAT behaviour, static mappings and whether the right traffic is being translated. Read the interface direction and address terms carefully.
Key takeaway
NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated.
Real-world example
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. NAT direction and interface roles matter as much as the IP address mapping. Inside/outside designation controls which traffic is translated. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related AZ-204 NAT questions on configuration and troubleshooting.
Connect to and consume Azure services and third-party services — study guide chapter
Learn the concepts, then practise the questions
Connect to and consume Azure services and third-party services practice questions
Targeted practice on this topic area only
All AZ-204 questions
997 questions across all exam domains
Microsoft Azure Developer Associate AZ-204 study guide
Full concept coverage aligned to exam objectives
AZ-204 practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise AZ-204 questions linked to Develop Azure compute solutions.
Practise AZ-204 questions linked to Develop for Azure storage.
Practise AZ-204 questions linked to Implement Azure security.
Practise AZ-204 questions linked to Connect to and consume Azure services and third-party services.
Practise AZ-204 questions linked to Monitor, troubleshoot, and optimize Azure solutions.
Practise AZ-204 questions linked to AZ-204 fundamentals.
Practise AZ-204 questions linked to AZ-204 scenario.
Practise AZ-204 questions linked to AZ-204 troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — Static NAT maps one inside address to one outside address..
The correct answer is: Implement retry logic with exponential backoff — Option A is correct because automatic retry with exponential backoff is a best practice for transient faults. Option B is incorrect because circuit breaker is for preventing repeated calls to a failing service, but it doesn't handle retries. Option C is incorrect because the request-reply pattern is for messaging, not for handling failures. Option D is incorrect because the saga pattern is for distributed transactions, not for retries.
Review the four NAT address types (inside local, inside global, outside local, outside global), PAT port overload, and static vs dynamic NAT use cases. Then practise related AZ-204 NAT questions on configuration and troubleshooting.
Static NAT maps one inside address to one outside address.
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 →
Keep practising
Last reviewed: Jun 20, 2026
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.