Microsoft Certified: Azure Developer Associate (AZ-204)Connect to and consume Azure services and third-party servicesMedium
A client is developing a serverless application that needs to perform a long-running, multi-step business process. Each step of the process might take several minutes to complete, and the overall process needs to maintain state across these steps, handling potential failures and retries. The client wants to use Azure Functions. Which Azure Functions capability is best suited for this scenario?
- ATimer-triggered Functions
- BRegular HTTP-triggered Functions
- CDurable Functions Orchestration
- DEvent Grid-triggered Functions
Show answer & explanationAnswer & explanation
Correct answer: C. Durable Functions Orchestration
Durable Functions orchestrations are specifically designed for long-running, stateful workflows in a serverless environment. They automatically manage state, checkpoints, and retries, making them ideal for complex multi-step business processes that require reliability and fault tolerance.
Why the other options are wrong
- A. Timer-triggered Functions run on a schedule and are not designed for stateful, multi-step business processes.
- B. Regular HTTP-triggered Functions are stateless and not suitable for long-running, multi-step processes with state management.
- D. Event Grid-triggered Functions respond to events but don't inherently manage state across multiple long-running steps.
Azure Durable Functions Orchestration
An extension of Azure Functions that enables writing stateful workflows in a serverless compute environment.
- Manages state, checkpoints, and restarts automatically.
- Supports long-running workflows with fan-out/fan-in patterns.
- Provides reliable execution and fault tolerance.
Memory trick: When long and complex, Durable Functions orchestrate the dance.