The correct answer is to configure a dead-letter destination for undelivered events and set a retry policy on the Event Grid subscription. These two options work together because Event Grid’s built-in retry mechanism automatically attempts delivery for transient failures, but if all retries are exhausted—based on your configured maximum delivery attempts and time-to-live—the event is sent to the dead-letter destination, such as a storage blob, preventing permanent data loss. On the AZ-204 exam, this scenario tests your understanding of Event Grid’s reliability features, often appearing in questions about handling poison events or ensuring fault-tolerant event processing. A common trap is to assume retries alone guarantee delivery, forgetting that dead-lettering is essential for events that fail permanently. Remember the mnemonic “Retry then Die” — retries handle the transient, dead-letter handles the terminal.
AZ-204 Develop Azure compute solutions Practice Question
This AZ-204 practice question tests your understanding of develop azure compute solutions. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
You are developing a solution that uses Azure Functions to process events from Azure Event Grid. The function must handle events reliably. Which TWO options should you implement?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Enable retry policy on the Event Grid subscription.
Option B is correct because Event Grid subscriptions support automatic retry policies that can be configured to retry event delivery on transient failures, ensuring reliable processing. Option D is correct because a dead-letter destination (e.g., a storage blob) captures events that cannot be delivered after exhausting retries, preventing data loss and enabling later analysis.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Use Durable Functions for orchestration.
Why it's wrong here
Durable Functions add complexity; not required for reliable event handling.
✓
Enable retry policy on the Event Grid subscription.
Why this is correct
Retry policy helps handle transient failures.
Related concept
Read the scenario before looking for a memorised answer.
✗
Implement manual checkpointing in the function code.
Why it's wrong here
Checkpointing is for Event Hubs, not Event Grid.
✓
Configure a dead-letter destination for undelivered events.
Why this is correct
Dead-lettering captures events that cannot be processed after retries.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a queue trigger instead of an Event Grid trigger.
Why it's wrong here
Queue trigger is different; Event Grid is appropriate for event-driven scenarios.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse Event Grid's built-in retry and dead-lettering with Durable Functions or manual checkpointing, assuming they need to implement custom reliability mechanisms when Azure already provides them natively.
Trap categories for this question
Scenario analysis trap
Queue trigger is different; Event Grid is appropriate for event-driven scenarios.
Detailed technical explanation
How to think about this question
Event Grid's retry policy uses exponential backoff with a configurable maximum interval (default 30 seconds) and retry count (default 30), while dead-lettering writes undelivered events to a blob storage container after retries are exhausted. Under the hood, Event Grid uses HTTP 200 OK acknowledgments from the function endpoint to mark delivery success; if the function throws an exception or times out, Event Grid retries based on the subscription's retry policy. A real-world scenario is a payment processing function that must not lose events—dead-lettering ensures failed events are stored for manual reprocessing.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A media company stores terabytes of video archives that are accessed once a year for audit purposes. Moving these objects to a cold storage tier (Azure Archive, S3 Glacier, or Google Nearline) costs a fraction of hot storage. Questions like this test whether you understand storage tiers, access frequency tradeoffs, and retrieval latency requirements.
Related glossary terms
Concepts from this question explained
These glossary pages explain the core terms tested in this AZ-204 question in full detail.
Develop Azure compute solutions — This question tests Develop Azure compute solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Enable retry policy on the Event Grid subscription. — Option B is correct because Event Grid subscriptions support automatic retry policies that can be configured to retry event delivery on transient failures, ensuring reliable processing. Option D is correct because a dead-letter destination (e.g., a storage blob) captures events that cannot be delivered after exhausting retries, preventing data loss and enabling later analysis.
What should I do if I get this AZ-204 question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
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.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.