AZ-305 Practice Question 69: Long Running Approval Workflow
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 7 · question 9 of 10
An order process runs several steps and then waits up to 14 days for a manager's approval before continuing. It must retry failed steps, be resilient to restarts, and contain custom C# business logic. The developers want the whole workflow written in code, unit tested and kept in source control with the application.
Which service should you recommend for the orchestration?
Show answer and explanation
Answer:
Durable Functions is the code-first extension of Azure Functions for stateful workflows. An orchestrator function written in C# coordinates the steps, its state is checkpointed so it survives restarts, and it can wait for an external event or a durable timer without holding resources. Because the orchestration is ordinary code, it can be unit tested and stored in source control with the rest of the application.
Option A can implement approvals and long waits, but it is designer-first and declarative, while the developers want the workflow expressed in code.
Option B is a hand-built imitation. You would have to write and maintain the state handling, retries and timeouts that the orchestrator provides.
Option C runs compute jobs at scale. Keeping a job asleep for 14 days wastes resources and gives no workflow state or retry model.
Reference: Compare Azure Functions and Azure Logic Apps