AZ-204 Develop Azure compute solutions Practice Question
A long-running claims processing function must process thousands of independent files. The developer wants status tracking, checkpoints, and replay-safe orchestration. Which Azure Functions capability should be used?
⚠ Common exam trap
Candidates often confuse a simple timer-triggered function (which can process files on a schedule) with the need for stateful orchestration, overlooking that Durable Functions is the only option that provides built-in checkpointing and replay safety for long-running, fault-tolerant 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 orchestrator
Durable Functions orchestrator is correct because it provides built-in support for status tracking, checkpoints (via event sourcing), and replay-safe orchestration, which are essential for a long-running claims processing function that must handle thousands of independent files reliably. The orchestrator function manages state and execution flow, automatically saving progress and allowing replay from checkpoints in case of failures, ensuring exactly-once processing semantics.
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 orchestrator
Why this is correct
Durable Functions orchestrators are specifically designed for complex, stateful, and long-running workflows, making them ideal for processing thousands of claims reliably. They provide built-in checkpointing and durable execution history, ensuring that the workflow state is preserved even across infrastructure failures or reboots. This allows the claims processing function to pause and resume, managing the progress of each claim without losing context and coordinating multiple steps effectively over extended periods.
- ✗
Timer trigger only
Why it's wrong here
A timer trigger is suitable for initiating functions at predetermined intervals but offers no inherent capabilities for managing the state or progress of a long-running, multi-step workflow. It would simply re-execute the initial processing logic, lacking the ability to track individual claims, handle retries, or coordinate subsequent processing steps if the initial execution fails or needs to pause. Relying solely on a timer would require significant custom state management outside the trigger itself, increasing complexity.
- ✗
Azure Policy remediation
Why it's wrong here
Azure Policy remediation is a governance feature focused on enforcing organizational standards and ensuring compliance for Azure resources, not on executing application-level business logic. Its purpose is to automatically deploy or modify resources to meet defined policies, such as applying specific tags or encryption settings across subscriptions. It operates at the control plane level and cannot orchestrate or manage the execution of a claims processing workflow or any other application function.
- ✗
Blob lifecycle management
Why it's wrong here
Azure Blob Storage lifecycle management rules automate the transition, archiving, or deletion of blobs based on conditions like age or access patterns, primarily for cost optimization and data retention. This feature operates exclusively on the data plane of storage accounts, manipulating blob properties and locations. It lacks any capability to invoke compute functions, manage application state, or coordinate the complex, multi-step processing required for a claims workflow.
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
Courseiva writes every AZ-204 question from scratch — 881 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.