Service Bus queues concept in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Message Delivery Behavior in Azure Service Bus Queues

What happens when a message is sent to an Azure Service Bus queue and there is no active receiver?

A The message is stored in the queue until a receiver connects or the message expires.

B The message is delivered to a dead-letter queue automatically.

C The message is sent back to the sender as undeliverable.

D The message is lost immediately because no receiver is available.

💡 Hint

Think about how queues work as buffers for messages.

Azure Service Bus queues store messages until a receiver is available or the message expires. This ensures reliable delivery.

❓ Architecture

intermediate

Choosing Between Queues and Topics in Azure Service Bus

You want to send messages to multiple independent receivers that each need to get all messages. Which Azure Service Bus feature should you use?

A Use a Service Bus topic with subscriptions to allow multiple receivers to get all messages.

B Use a Service Bus queue because it supports multiple receivers getting all messages.

C Use multiple queues, one per receiver, and send messages to each queue separately.

D Use a Service Bus relay to broadcast messages to multiple receivers.

💡 Hint

Think about publish-subscribe patterns.

Service Bus topics with subscriptions allow multiple receivers to get copies of each message, unlike queues which deliver each message to only one receiver.

❓ security

advanced

Securing Access to Azure Service Bus Queues

Which method provides the most secure way to grant an application access to send messages to a Service Bus queue without sharing the primary key?

A Share the primary connection string with the application.

B Create a shared access signature (SAS) token with send permissions and share it.

C Use Azure Active Directory (Azure AD) role-based access control (RBAC) to assign send permissions.

D Use a public endpoint with IP filtering to restrict access.

💡 Hint

Consider modern identity and access management best practices.

Using Azure AD RBAC avoids sharing keys and allows fine-grained, auditable access control.

❓ Configuration

advanced

Configuring Message Lock Duration in Service Bus Queues

You want to ensure that when a receiver reads a message from a Service Bus queue, the message is locked for 2 minutes to prevent other receivers from processing it simultaneously. Which configuration should you set?

A Set the queue's DefaultMessageTimeToLive property to '00:02:00'.

B Set the queue's LockDuration property to '00:02:00'.

C Set the queue's MaxDeliveryCount property to 2.

D Set the queue's AutoDeleteOnIdle property to '00:02:00'.

💡 Hint

Think about how message locks prevent duplicate processing.

The LockDuration property controls how long a message is locked for a receiver before it becomes available to others.

✅ Best Practice

expert

Handling Poison Messages in Azure Service Bus Queues

What is the recommended approach to handle messages that repeatedly fail processing (poison messages) in an Azure Service Bus queue?

A Delete the message immediately upon first failure to avoid blocking the queue.

B Increase the MaxDeliveryCount property to allow more retries indefinitely.

C Disable message locking to allow multiple receivers to process the message simultaneously.

D Configure a dead-letter queue and move poison messages there after MaxDeliveryCount is exceeded.

💡 Hint

Consider how to isolate problematic messages without losing them.

Dead-letter queues isolate poison messages for later inspection and prevent them from blocking normal processing.

Practice

1. What is the main purpose of an Azure Service Bus queue?

easy

A. To store files and documents

B. To host websites and web applications

C. To run virtual machines

D. To store messages until a receiver processes them

Solution

1. Step 1: Understand the role of Service Bus queues

   Service Bus queues are designed to hold messages temporarily until a receiver is ready to process them.

2. Step 2: Compare with other Azure services

   Hosting websites, storing files, or running virtual machines are tasks for other Azure services, not Service Bus queues.

3. Final Answer:

   To store messages until a receiver processes them -> Option D

4. Quick Check:

   Service Bus queues store messages = C [OK]

Hint: Queues hold messages until processed by receivers [OK]

Common Mistakes:

• Confusing queues with storage accounts
• Thinking queues run applications
• Mixing queues with virtual machines

2. Which of the following is the correct way to create a Service Bus queue using Azure CLI?

easy

A. az servicebus queue create --resource-group MyGroup --namespace-name MyNamespace --name MyQueue

B. az storage queue create --resource-group MyGroup --name MyQueue

C. az vm create --resource-group MyGroup --name MyQueue

D. az webapp create --resource-group MyGroup --name MyQueue

Solution

1. Step 1: Identify the correct Azure CLI command for Service Bus queue

   The command to create a Service Bus queue uses 'az servicebus queue create' with resource group, namespace, and queue name.

2. Step 2: Eliminate other commands

   Other commands relate to storage queues, virtual machines, or web apps, which are not Service Bus queues.

3. Final Answer:

   az servicebus queue create --resource-group MyGroup --namespace-name MyNamespace --name MyQueue -> Option A

4. Quick Check:

   Service Bus queue creation uses 'az servicebus queue create' = D [OK]

Hint: Use 'az servicebus queue create' for queues [OK]

Common Mistakes:

• Using storage queue commands for Service Bus
• Confusing VM or web app commands with queues
• Omitting namespace name in command

3. Given this code snippet using Azure SDK for Python, what will be the output if the queue is empty?

from azure.servicebus import ServiceBusClient
connection_str = "Endpoint=sb://example.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=key"
queue_name = "testqueue"

with ServiceBusClient.from_connection_string(connection_str) as client:
    receiver = client.get_queue_receiver(queue_name=queue_name)
    with receiver:
        messages = receiver.receive_messages(max_message_count=1, max_wait_time=5)
        print(len(messages))

medium

A. 1

B. 0

C. None

D. Error

Solution

1. Step 1: Understand receive_messages behavior on empty queue

   If the queue is empty, receive_messages returns an empty list after waiting max_wait_time seconds.

2. Step 2: Check the printed output

   Printing the length of the messages list will print 0 because no messages were received.

3. Final Answer:

   0 -> Option B

4. Quick Check:

   Empty queue returns empty list, length = 0 [OK]

Hint: Empty queue returns empty list, length zero [OK]

Common Mistakes:

• Expecting None instead of empty list
• Assuming an error occurs on empty queue
• Thinking it returns one message by default

4. You wrote this code to receive messages from a Service Bus queue but it throws an error:

receiver = client.get_queue_receiver(queue_name="myqueue")
messages = receiver.receive_messages(max_message_count=5)
for msg in messages:
    print(msg.body)
    receiver.complete_message(msg)

What is the likely cause of the error?

medium

A. Receiver was not used as a context manager or opened before receiving messages

B. max_message_count must be 1

C. You cannot complete messages in Service Bus

D. Queue name must be 'default'

Solution

1. Step 1: Check how receiver is used

   The receiver must be opened before receiving messages, usually by using 'with' statement or calling 'receiver.open()'.

2. Step 2: Identify missing context management

   In the code, receiver is not opened or used as a context manager, causing an error when calling receive_messages.

3. Final Answer:

   Receiver was not used as a context manager or opened before receiving messages -> Option A

4. Quick Check:

   Receiver must be opened before use = B [OK]

Hint: Always open receiver with 'with' or open() before receiving [OK]

Common Mistakes:

• Not opening receiver before receiving messages
• Thinking max_message_count must be 1
• Believing message completion is not allowed

5. You want to ensure that messages that cannot be processed after multiple attempts are not lost but moved for later inspection. Which Service Bus queue feature should you use?

hard

A. Duplicate detection

B. Auto-delete on idle

C. Dead-letter queue

D. Partitioning

Solution

1. Step 1: Understand message failure handling

   Messages that fail processing multiple times should be moved to a special queue to avoid loss and allow inspection.

2. Step 2: Identify the dead-letter queue feature

   Service Bus provides a dead-letter queue for this purpose, storing messages that cannot be delivered or processed.

3. Final Answer:

   Dead-letter queue -> Option C

4. Quick Check:

   Dead-letter queue stores failed messages = A [OK]

Hint: Use dead-letter queue for failed message handling [OK]

Common Mistakes:

• Confusing dead-letter with auto-delete
• Thinking duplicate detection handles failures
• Assuming partitioning manages failed messages