Service Bus topics and subscriptions in Azure - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Service Bus topic using Azure CLI.

Azure

az servicebus topic create --resource-group myResourceGroup --namespace-name myNamespace --name [1]

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

AmySubscription

BmyQueue

CmyTopic

DmyNamespace

Attempts:

3 left

💡 Hint

Common Mistakes

Using subscription or namespace names instead of the topic name.

Confusing topic with queue names.

The topic name is required to create a Service Bus topic. Here, myTopic is the correct name for the topic.

2fill in blank

medium

Complete the code to create a subscription for a Service Bus topic.

Azure

az servicebus topic subscription create --resource-group myResourceGroup --namespace-name myNamespace --topic-name myTopic --name [1]

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

AmySubscription

BmyQueue

CmyTopic

DmyNamespace

Attempts:

3 left

💡 Hint

Common Mistakes

Using topic or namespace names instead of subscription name.

Confusing subscription with queue or topic names.

The subscription name is required to create a subscription under a topic. Here, mySubscription is the correct subscription name.

3fill in blank

hard

Fix the error in the code to send a message to a Service Bus topic using Azure SDK for Python.

Azure

from azure.servicebus import ServiceBusClient, ServiceBusMessage

connection_str = 'Endpoint=sb://myNamespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=key'

with ServiceBusClient.from_connection_string(connection_str) as client:
    sender = client.get_topic_sender(topic_name=[1])
    message = ServiceBusMessage('Hello World')
    sender.send_messages(message)

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

A'mySubscription'

B'myTopic'

C'myQueue'

D'myNamespace'

Attempts:

3 left

💡 Hint

Common Mistakes

Passing subscription or queue names instead of topic name.

Not using quotes around the topic name string.

The get_topic_sender method requires the topic name as a string. Here, 'myTopic' is the correct topic name to send messages to.

4fill in blank

hard

Fill both blanks to create a subscription with a filter rule to only receive messages with label 'important'.

Azure

az servicebus topic subscription rule create --resource-group myResourceGroup --namespace-name myNamespace --topic-name myTopic --subscription-name mySubscription --name [1] --filter-sql-expression [2]

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

AImportantRule

B'sys.Label = ''important'''

C'sys.Label = important'

DDefaultRule

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect quotes in the filter expression.

Using default rule name when a custom name is expected.

The rule name can be any valid string, here ImportantRule is used. The filter expression must be a valid SQL expression as a string, so 'sys.Label = ''important''' is correct with proper quotes.

5fill in blank

hard

Fill all three blanks to receive messages from a subscription using Azure SDK for Python and complete the message processing.

Azure

from azure.servicebus import ServiceBusClient

connection_str = 'Endpoint=sb://myNamespace.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=key'

with ServiceBusClient.from_connection_string(connection_str) as client:
    receiver = client.get_subscription_receiver(topic_name=[1], subscription_name=[2])
    with receiver:
        messages = receiver.receive_messages(max_message_count=1, max_wait_time=5)
        for msg in messages:
            print(msg.body.decode())
            receiver.[3](msg)

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

A'myTopic'

B'mySubscription'

Ccomplete_message

Dabandon_message

Attempts:

3 left

💡 Hint

Common Mistakes

Using queue or namespace names instead of topic or subscription names.

Calling wrong method to complete message processing.

The get_subscription_receiver method requires the topic and subscription names as strings. After processing, complete_message is called to mark the message as processed.