Question 346 of 997

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. Match the stated requirement to the specific cloud service, access model, or configuration option — many options are valid in isolation but not for this scenario. A key principle to apply: maxDeliveryCount defines how many times a message can be delivered before dead-lettering.. 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 function consumes messages from Azure Service Bus. Which two settings help handle transient failures safely? The design must avoid adding custom operational scripts.

Question 1hardmulti select
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Configure max delivery count with a dead-letter queue

Option A is correct because configuring a max delivery count with a dead-letter queue allows the system to automatically move a message to the dead-letter queue after a specified number of failed delivery attempts. This prevents poison messages from being retried indefinitely, handling transient failures safely without custom scripts. Option B is correct because idempotent message processing ensures that if a message is processed more than once due to transient failures or retries, the system state remains consistent, avoiding duplicate side effects.

Key principle: MaxDeliveryCount defines how many times a message can be delivered before dead-lettering.

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Configure max delivery count with a dead-letter queue

    Why this is correct

    Dead-lettering isolates messages after repeated delivery failures.

    Related concept

    MaxDeliveryCount defines how many times a message can be delivered before dead-lettering.

  • Make message processing idempotent

    Why this is correct

    Idempotency protects against duplicate delivery or retry side effects.

    Related concept

    MaxDeliveryCount defines how many times a message can be delivered before dead-lettering.

  • Disable lock renewal for long processing

    Why it's wrong here

    Disabling lock renewal can cause duplicate processing for long-running work.

  • Use anonymous sender access

    Why it's wrong here

    Anonymous access is not a safe messaging practice.

Common exam traps

Common exam trap: answer the scenario, not the keyword

The trap here is that candidates often confuse disabling lock renewal as a way to handle long processing times, but it actually causes message abandonment and reprocessing, not safe transient failure handling.

Detailed technical explanation

How to think about this question

Under the hood, Azure Service Bus uses a peek-lock mechanism where a message lock has a default duration of 30 seconds (configurable up to 5 minutes). If processing exceeds the lock duration, the lock must be renewed via the RenewLock operation; disabling renewal leads to lock loss. The max delivery count (default 10) works with the dead-letter queue to quarantine messages after exceeding the limit, and the dead-letter queue stores messages with a dead-letter reason (e.g., MaxDeliveryCountExceeded) and source queue info, enabling manual inspection without custom scripts.

KKey Concepts to Remember

  • MaxDeliveryCount defines how many times a message can be delivered before dead-lettering.
  • Dead-letter queues (DLQs) automatically store messages that fail processing repeatedly.
  • Messages are moved to the DLQ by Service Bus, not by application code.
  • DLQ messages can be inspected, reprocessed, or discarded manually or programmatically.

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

MaxDeliveryCount defines how many times a message can be delivered before dead-lettering.

Real-world example

How this comes up in practice

A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.

What to study next

Got this wrong? Here's your next step.

Review maxDeliveryCount defines how many times a message can be delivered before dead-lettering., then practise related AZ-204 questions on the same topic to reinforce the concept.

Related practice questions

Related AZ-204 practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free AZ-204 practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this AZ-204 question test?

Connect to and consume Azure services and third-party services — This question tests Connect to and consume Azure services and third-party services — MaxDeliveryCount defines how many times a message can be delivered before dead-lettering..

What is the correct answer to this question?

The correct answer is: Configure max delivery count with a dead-letter queue — Option A is correct because configuring a max delivery count with a dead-letter queue allows the system to automatically move a message to the dead-letter queue after a specified number of failed delivery attempts. This prevents poison messages from being retried indefinitely, handling transient failures safely without custom scripts. Option B is correct because idempotent message processing ensures that if a message is processed more than once due to transient failures or retries, the system state remains consistent, avoiding duplicate side effects.

What should I do if I get this AZ-204 question wrong?

Review maxDeliveryCount defines how many times a message can be delivered before dead-lettering., then practise related AZ-204 questions on the same topic to reinforce the concept.

What is the key concept behind this question?

MaxDeliveryCount defines how many times a message can be delivered before dead-lettering.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More AZ-204 practice questions

Last reviewed: Jun 11, 2026

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.

Loading comments…

Sign in to join the discussion.

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.