Durable Functions is the correct choice because it extends Azure Functions to support stateful, long-running orchestration with human approval, exactly what you need for a multi-step workflow that may run for hours and requires waiting for external events like email-based approvals. This feature works by using the Event Orchestration pattern, where your function can pause execution at an approval step, wait for an external HTTP callback or event, and then resume from the exact checkpoint—all while preserving state through automatic checkpointing and replay. On the AZ-204 exam, this scenario tests your understanding of how Durable Functions differ from standard stateless Azure Functions, which cannot natively handle long-running waits or maintain state across steps. A common trap is choosing Logic Apps or regular HTTP-triggered functions, but remember: if the workflow needs to wait for human input and run for hours, Durable Functions is the only Azure Functions feature that provides built-in support for durable timers and external event handling. Memory tip: think “Durable = Delays + Human Approval + Replay.”
AZ-204 Develop Azure compute solutions Practice Question
This AZ-204 practice question tests your understanding of develop azure compute solutions. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. 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 are developing a solution that needs to perform a multi-step workflow. The workflow involves calling several third-party APIs, and some steps may require waiting for a human approval via email. The workflow may run for hours. You want to use Azure Functions to implement this orchestration. Which Azure Functions feature should you use?
Durable Functions is designed for stateful orchestrations, supporting long-running workflows, waiting for external events, and managing multi-step processes.
B
Timer trigger functions
Why wrong: Timer triggers run on a schedule and do not support event-driven multi-step orchestrations with human interaction.
C
Service Bus queue trigger functions
Why wrong: Queue triggers process single messages; they are not suitable for complex, stateful workflows that require waiting for external events.
D
Blob storage trigger functions
Why wrong: Blob triggers respond to blob creation/modification events and cannot orchestrate multi-step workflows with waiting.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Durable Functions
Durable Functions is the correct choice because it is an extension of Azure Functions that enables stateful, long-running orchestration workflows. It supports waiting for external events (like human approval via email), managing multi-step API calls, and handling execution that may run for hours, all while preserving state through checkpoints and replay.
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.
✓
Durable Functions
Why this is correct
Durable Functions is designed for stateful orchestrations, supporting long-running workflows, waiting for external events, and managing multi-step processes.
Related concept
Read the scenario before looking for a memorised answer.
✗
Timer trigger functions
Why it's wrong here
Timer triggers run on a schedule and do not support event-driven multi-step orchestrations with human interaction.
✗
Service Bus queue trigger functions
Why it's wrong here
Queue triggers process single messages; they are not suitable for complex, stateful workflows that require waiting for external events.
✗
Blob storage trigger functions
Why it's wrong here
Blob triggers respond to blob creation/modification events and cannot orchestrate multi-step workflows with waiting.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates may confuse trigger-based functions (like Timer or Queue triggers) with orchestration capabilities, not realizing that Durable Functions is the only Azure Functions feature that provides built-in state management and external event waiting for long-running workflows.
Detailed technical explanation
How to think about this question
Durable Functions uses the Event Sourcing pattern internally, where each function execution is recorded as a series of events in a storage table (Azure Storage). The orchestration is replayed from history on each step, ensuring reliable execution even after long idle periods. In a real-world scenario, you can use the `WaitForExternalEvent` API to pause the orchestration until an approval email callback is received, and the function will automatically resume from the checkpoint.
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: Durable Functions — Durable Functions is the correct choice because it is an extension of Azure Functions that enables stateful, long-running orchestration workflows. It supports waiting for external events (like human approval via email), managing multi-step API calls, and handling execution that may run for hours, all while preserving state through checkpoints and replay.
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 →
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. A long-running webhook processor must process thousands of independent files. The developer wants status tracking, checkpoints, and replay-safe orchestration. Which Azure Functions capability should be used?
medium
A.Blob lifecycle management
B.Timer trigger only
✓ C.Durable Functions orchestrator
D.Azure Policy remediation
Why C: Durable Functions orchestrator is correct because it provides built-in support for status tracking, checkpointing, and replay-safe orchestration via the Event Sourcing pattern. The orchestrator function automatically saves execution history to a storage table, enabling reliable resumption after crashes or restarts, which is essential for processing thousands of independent files with long-running workflows.
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.