Correct Answer: Use Durable Functions (orchestrator and activity functions) to manage the state, sequencing, and error handling of the workflow.
Durable Functions is an extension of Azure Functions that allows you to write stateful workflows in code. The orchestrator function handles sequencing, checkpoints, and error handl...
Correct Answer
Use Durable Functions (orchestrator and activity functions) to manage the state, sequencing, and error handling of the workflow.
Why This Answer Is Correct
Durable Functions is an extension of Azure Functions that allows you to write stateful workflows in code. The orchestrator function handles sequencing, checkpoints, and error handling (such as executing a compensating transaction inside a try-catch block). Durable Functions automatically checkpoints progress, allowing the orchestrator to sleep and free up CPU resources while waiting for activity functions, incurring zero runtime billing during idle states.
This question evaluates your knowledge of Azure Functions — a core concept tested in Microsoft Certified: Azure Developer Associate (AZ-204). Understanding Azure Functions is essential for designing scalable, secure, and cost-effective cloud architectures. Mastery of this topic will help you answer scenario-based questions confidently on exam day.
You are building an Azure Function that processes orders from an Azure Service Bus queue. The function must ensure that each order is processed exactly once, even if the function crashes mid-processing. Which Service Bus feature guarantees this behavior?
Your Azure Function app needs to store temporary state between multiple function executions as part of a long-running workflow. The workflow includes human approval steps that can pause for days. Which solution should you implement?
You have an Azure Function triggered by a Timer. During load testing you notice that multiple instances of the function run simultaneously, causing duplicate processing. How do you prevent concurrent executions of a timer-triggered function?
You are building an event-driven microservice using Azure Functions. The function must process messages from an Azure Service Bus queue and write results to Azure Cosmos DB. To minimize cold-start latency and ensure the function scales with message volume, which hosting plan and trigger combination is most appropriate?