The answer is built-in retry policies in Durable Functions. This feature is correct because it allows you to declaratively configure retry behavior directly on activity function calls within the orchestrator function, specifying parameters like max retry count, backoff interval, and retry timeout to handle transient errors automatically without writing custom retry logic. On the Microsoft Azure Developer Associate AZ-204 exam, this concept tests your understanding of how Durable Functions manage fault tolerance in long-running orchestrations, often appearing in scenario-based questions where you must choose between custom retry code, external queues, or the built-in policy. A common trap is assuming you need to implement retry manually with try-catch blocks, but the built-in policy handles it seamlessly. Memory tip: think of the acronym “BRT” for Built-in Retry on Transient errors—it’s the native, no-code way to keep your orchestrations resilient.
AZ-204 Develop Azure compute solutions Practice Question
This AZ-204 practice question tests your understanding of develop azure compute solutions. 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.
You develop an Azure Durable Functions application that orchestrates a series of activities. The orchestrator function calls activity functions that perform long-running tasks. You need to ensure that the orchestrator function can handle transient errors and retry failed activity functions. Which feature 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
✓
Built-in retry policies in Durable Functions
Durable Functions provides built-in retry policies that can be configured directly on activity function calls within orchestrator functions. This allows you to specify parameters such as max retry count, backoff interval, and retry timeout, enabling the orchestrator to automatically retry failed activities without custom code or external dependencies.
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.
✗
Polly library for retry logic
Why it's wrong here
Polly can be used, but it is not a built-in feature of Durable Functions and requires additional code.
✓
Built-in retry policies in Durable Functions
Why this is correct
Durable Functions allows you to specify retry options for activity function calls, including max retry count and backoff.
Related concept
Read the scenario before looking for a memorised answer.
✗
Application Insights alerts
Why it's wrong here
Alerts notify but do not automatically retry failed activities.
✗
Azure Storage queue message retries
Why it's wrong here
Durable Functions uses storage queues internally, but retry logic is managed at the orchestration level.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may assume any retry mechanism (like Polly or queue retries) works equally well, but they fail to recognize that Durable Functions' built-in retry policies are the only option that integrates seamlessly with the orchestrator's deterministic replay and state management.
Detailed technical explanation
How to think about this question
Under the hood, Durable Functions' built-in retry policies work by storing retry state in the orchestration history table, ensuring that retries are replayed deterministically even after function app restarts. The retry policy uses exponential backoff with optional jitter, and the max retry interval can be capped to prevent excessive delays. In a real-world scenario, if an activity function calls an external API that throttles requests, you can configure a retry policy with a 5-second backoff and a maximum of 3 retries, allowing the orchestrator to gracefully recover without manual intervention.
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 media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Develop Azure compute solutions — This question tests Develop Azure compute solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Built-in retry policies in Durable Functions — Durable Functions provides built-in retry policies that can be configured directly on activity function calls within orchestrator functions. This allows you to specify parameters such as max retry count, backoff interval, and retry timeout, enabling the orchestrator to automatically retry failed activities without custom code or external dependencies.
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.