Correct Answer: Peek-Lock message settlement with manual completion
Peek-Lock mode locks the message during processing and only removes it from the queue when explicitly completed. If the function crashes before completing, the lock expires and the...
Correct Answer
Peek-Lock message settlement with manual completion
Why This Answer Is Correct
Peek-Lock mode locks the message during processing and only removes it from the queue when explicitly completed. If the function crashes before completing, the lock expires and the message becomes available again, guaranteeing at-least-once delivery with idempotent processing.
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.
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?
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?