Service Bus queues concept in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Service Bus queue client.

Azure

from azure.servicebus import ServiceBusClient

connection_str = "Endpoint=sb://example.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=key"
queue_name = "myqueue"

client = ServiceBusClient.from_connection_string([1])
receiver = client.get_queue_receiver(queue_name=queue_name)

Drag options to blanks, or click blank then click option'

Aconnection_str

Bqueue_name

Cclient

Dreceiver

Attempts:

3 left

💡 Hint

Common Mistakes

Using the queue name instead of the connection string.

Trying to use the client or receiver variables before they are defined.

The ServiceBusClient is created using the connection string to connect to the Azure Service Bus namespace.

2fill in blank

medium

Complete the code to send a message to the Service Bus queue.

Azure

from azure.servicebus import ServiceBusMessage

with client.get_queue_sender(queue_name=queue_name) as sender:
    message = ServiceBusMessage("Hello, Service Bus!")
    sender.[1]([message])

Drag options to blanks, or click blank then click option'

Areceive_messages

Bdelete_message

Ccreate_message

Dsend_messages

Attempts:

3 left

💡 Hint

Common Mistakes

Using receive_messages instead of send_messages.

Trying to create or delete messages directly.

The method send_messages is used to send messages to the queue.

3fill in blank

hard

Fix the error in receiving messages from the queue by completing the method name.

Azure

with client.get_queue_receiver(queue_name=queue_name) as receiver:
    messages = receiver.[1](max_message_count=5, max_wait_time=10)
    for msg in messages:
        print(str(msg))
        receiver.complete_message(msg)

Drag options to blanks, or click blank then click option'

Asend_messages

Breceive_messages

Cget_messages

Dfetch_messages

Attempts:

3 left

💡 Hint

Common Mistakes

Using send_messages on the receiver object.

Using non-existent methods like get_messages or fetch_messages.

The receive_messages method is used to get messages from the queue.

4fill in blank

hard

Fill both blanks to create a dictionary of message bodies and complete messages.

Azure

with client.get_queue_receiver(queue_name=queue_name) as receiver:
    messages = list(receiver.[1](max_message_count=3))
    results = {msg.[2]: msg for msg in messages}
    for msg in messages:
        receiver.complete_message(msg)

Drag options to blanks, or click blank then click option'

Areceive_messages

Bbody

Cmessage_id

Dsend_messages

Attempts:

3 left

💡 Hint

Common Mistakes

Using send_messages instead of receive_messages.

Using body instead of message_id as dictionary key.

We receive messages with receive_messages and use message_id as the dictionary key.

5fill in blank

hard

Fill all three blanks to send a batch of messages with custom content.

Azure

from azure.servicebus import ServiceBusMessage

messages = [ServiceBusMessage([1]) for i in range(3)]
with client.get_queue_sender(queue_name=queue_name) as sender:
    sender.[2](messages)

with client.get_queue_receiver(queue_name=queue_name) as receiver:
    received = receiver.[3](max_message_count=3)
    for msg in received:
        print(str(msg))
        receiver.complete_message(msg)

Drag options to blanks, or click blank then click option'

A"Message " + str(i)

Bsend_messages

Creceive_messages

D"Hello"

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to concatenate strings inside the list comprehension incorrectly.

Using send_messages on the receiver or receive_messages on the sender.

Each message is created with the content "Message " plus the index. We send messages with send_messages and receive them with receive_messages.

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