The answer is enabling duplicate detection on the Azure Service Bus queue or topic. This feature is correct because it uses a user-defined MessageId to identify and discard duplicate messages within a configurable time window, defaulting to 10 minutes and extendable up to 7 days. When your order processing system fails and retries, duplicate detection ensures exactly-once processing by preventing the same financial transaction message from being consumed multiple times, which is critical for idempotent handling. On the Microsoft Azure Developer Associate AZ-204 exam, this scenario tests your understanding of messaging reliability patterns, often appearing as a distractor against competing features like sessions or dead-lettering. A common trap is confusing duplicate detection with at-least-once delivery guarantees—remember that duplicate detection is the mechanism that upgrades at-least-once to exactly-once within the time window. Memory tip: think "MessageId = unique fingerprint" to recall that the feature relies on a stable, application-defined identifier to spot and drop repeats.
AZ-204 Practice Question: Connect to and consume Azure services and third-party services
This AZ-204 practice question tests your understanding of connect to and consume azure services and third-party services. 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.
A company uses Azure Service Bus to receive order messages. Each order message must be processed exactly once, and duplicate messages are not tolerated due to financial transactions. However, the order processing system sometimes fails and retries, leading to potential duplicates. What Service Bus feature should be enabled on the message to support idempotent processing?
Why wrong: Scheduled delivery allows sending a message at a later time but does not prevent duplicates.
B
Duplicate detection
Duplicate detection uses the MessageId property to identify and discard duplicate messages sent within the detection window, ensuring exactly-once processing.
C
Message sessions
Why wrong: Sessions provide ordered and atomic handling of related messages but do not inherently detect duplicates.
D
Auto-forwarding
Why wrong: Auto-forwarding automatically moves messages from one queue or subscription to another but does not handle duplicate detection.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Duplicate detection
B is correct because Azure Service Bus's duplicate detection feature uses a user-defined MessageId to identify and discard duplicate messages within a specified time window (default 10 minutes, configurable up to 7 days). This ensures exactly-once processing by preventing the same order message from being processed multiple times, even if the sender retries due to failures.
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.
✗
Scheduled delivery
Why it's wrong here
Scheduled delivery allows sending a message at a later time but does not prevent duplicates.
✓
Duplicate detection
Why this is correct
Duplicate detection uses the MessageId property to identify and discard duplicate messages sent within the detection window, ensuring exactly-once processing.
Related concept
Read the scenario before looking for a memorised answer.
✗
Message sessions
Why it's wrong here
Sessions provide ordered and atomic handling of related messages but do not inherently detect duplicates.
✗
Auto-forwarding
Why it's wrong here
Auto-forwarding automatically moves messages from one queue or subscription to another but does not handle duplicate detection.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse message sessions (which guarantee order and grouping) with duplicate detection, but sessions do not prevent duplicates—they only ensure FIFO delivery within a session.
Detailed technical explanation
How to think about this question
Under the hood, Service Bus duplicate detection relies on the MessageId property; when a message with a previously seen MessageId arrives within the detection window, it is silently accepted but not delivered to the consumer. This is implemented via a hash-based lookup in the broker's internal store, and the window is tracked using the TimeSpan property on the queue or topic. In real-world scenarios, setting a unique MessageId (e.g., a GUID or a hash of the order payload) is critical, as duplicate detection will not work if the MessageId is null or empty.
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.
Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Duplicate detection — B is correct because Azure Service Bus's duplicate detection feature uses a user-defined MessageId to identify and discard duplicate messages within a specified time window (default 10 minutes, configurable up to 7 days). This ensures exactly-once processing by preventing the same order message from being processed multiple times, even if the sender retries due to failures.
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.