The correct answer is to configure the retry policy in the function’s host.json file. This is because Azure Functions for Event Hubs provides a built-in, declarative retry mechanism that you define in the host.json settings, allowing you to specify a maximum number of retries—such as three—after which the event is automatically routed to a dead-letter queue (DLQ) on the Event Hub. This approach eliminates the need for custom code to handle retries or dead-lettering, as the Azure Functions runtime manages the entire flow. On the AZ-204 exam, this tests your understanding of how to implement resilient event-driven architectures without reinventing the wheel; a common trap is assuming you must write manual retry logic in the function code or use a separate service like Azure Service Bus. Remember the memory tip: “host.json holds the retry throne”—the configuration lives in host.json, not in the function signature or application settings.
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.
Your Azure Function app uses an event-driven architecture with Azure Event Hubs. You need to ensure that if the function fails to process an event, the event is retried up to three times and then sent to a dead-letter queue. What should you configure?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Configure the retry policy in the function's host.json file.
Option C is correct because Azure Functions for Event Hubs supports a built-in retry policy configured in the host.json file. This policy allows you to specify the maximum number of retries (e.g., 3) and, after exhausting those retries, the event is automatically sent to a dead-letter queue (DLQ) configured on the Event Hub. This approach is declarative and requires no custom code for retry or dead-lettering logic.
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 to orchestrate retries and dead-lettering.
Why it's wrong here
Durable Functions add unnecessary complexity for simple retries.
✗
Implement a try-catch block in the function code and manually re-queue the event.
Why it's wrong here
Manual re-queuing is not recommended; built-in retry is simpler.
✓
Configure the retry policy in the function's host.json file.
Why this is correct
The retry policy in host.json allows setting maxRetryCount and dead-lettering.
Related concept
Read the scenario before looking for a memorised answer.
✗
Set the 'enableRetry' property on the Event Hub namespace.
Why it's wrong here
Event Hubs does not have a retry property; retry is handled by the consumer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse the retry policy configuration location (host.json for the function app) with properties on the Event Hubs namespace itself, or they overcomplicate the solution by choosing Durable Functions when a simple declarative setting suffices.
Detailed technical explanation
How to think about this question
Under the hood, the retry policy in host.json for Event Hubs triggers uses the 'maxRetryCount' and 'deadLetteringOnMessageExpiration' settings to control retries and dead-lettering. When a function fails, the Event Hubs trigger automatically retries the event up to the specified count; after exhaustion, the event is moved to the configured dead-letter queue (DLQ) on the Event Hub, which is a separate sub-queue for unprocessable messages. This behavior relies on the Event Hubs client library's checkpointing and retry logic, ensuring no manual intervention is needed.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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: Configure the retry policy in the function's host.json file. — Option C is correct because Azure Functions for Event Hubs supports a built-in retry policy configured in the host.json file. This policy allows you to specify the maximum number of retries (e.g., 3) and, after exhausting those retries, the event is automatically sent to a dead-letter queue (DLQ) configured on the Event Hub. This approach is declarative and requires no custom code for retry or dead-lettering logic.
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.