Durable Functions for Human Approval Orchestration
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?
Quick Answer
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.”
⚠ Common exam trap
Candidates often 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.
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
✓
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.
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.
- ✗
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.
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Azure Functions Development
Key term
Durable Functions
Durable Functions is an extension of Azure Functions that lets you write stateful workflows in code, managing complex sequences of tasks, retries, and delays automatically.
Key term
Azure Functions Bindings
Azure Functions Bindings are declarative connections that link your serverless function code to Azure services or external resources, handling input and output data automatically without writing extra networking or authentication code.
About these practice questions
One of 881 original AZ-204 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on AZ-204
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.
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.