Correct Answer: Consumption Plan with a Service Bus trigger and Cosmos DB output binding
The Consumption Plan auto-scales based on load, and the Service Bus trigger natively integrates with Azure Service Bus queues so that the function is invoked per message. Using the...
Correct Answer
Consumption Plan with a Service Bus trigger and Cosmos DB output binding
Why This Answer Is Correct
The Consumption Plan auto-scales based on load, and the Service Bus trigger natively integrates with Azure Service Bus queues so that the function is invoked per message. Using the Cosmos DB output binding eliminates the need for SDK plumbing code.
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 designing an Azure Function workflow that coordinates a complex, long-running order processing system. The workflow must execute three tasks in sequence (Validate Order, Charge Card, Ship Item). If the 'Charge Card' step fails, it must execute a compensating transaction to void the order. The orchestrator must be able to pause its execution without consuming billing resources while waiting for tasks to complete. Which feature should you use?