Why messaging services matter in Azure - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a basic Azure Service Bus namespace.

Azure

az servicebus namespace create --resource-group myResourceGroup --name [1] --location eastus

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

AmyResourceGroup

BmyServiceBusNamespace

Ceastus

DmyQueue

Attempts:

3 left

💡 Hint

Common Mistakes

Using the resource group name instead of the namespace name.

The --name parameter specifies the name of the Service Bus namespace to create.

2fill in blank

medium

Complete the code to create a queue inside the Service Bus namespace.

Azure

az servicebus queue create --resource-group myResourceGroup --namespace-name myServiceBusNamespace --name [1]

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

AmyQueue

BmyTopic

CmySubscription

DmyResourceGroup

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing queue name with topic or subscription names.

The --name parameter here specifies the queue name inside the namespace.

3fill in blank

hard

Fix the error in the code to send a message to the queue using Azure CLI.

Azure

az servicebus queue send --resource-group myResourceGroup --namespace-name myServiceBusNamespace --queue-name myQueue --message-body [1]

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

AHello_World

BHello World

C'Hello World'

D"Hello World"

Attempts:

3 left

💡 Hint

Common Mistakes

Not quoting the message body causing syntax errors.

The message body must be passed as a string enclosed in quotes to be valid.

4fill in blank

hard

Fill both blanks to configure a topic and subscription in Azure Service Bus.

Azure

az servicebus topic create --resource-group myResourceGroup --namespace-name myServiceBusNamespace --name [1]
az servicebus subscription create --resource-group myResourceGroup --namespace-name myServiceBusNamespace --topic-name [2] --name mySubscription

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

AmyTopic

BmyQueue

DmySubscription

Attempts:

3 left

💡 Hint

Common Mistakes

Using different names for topic and subscription topic-name parameter.

The topic name must be the same when creating the subscription to link them correctly.

5fill in blank

hard

Fill all three blanks to create a Service Bus namespace, a queue, and send a message.

Azure

az servicebus namespace create --resource-group myResourceGroup --name [1] --location eastus
az servicebus queue create --resource-group myResourceGroup --namespace-name [2] --name myQueue
az servicebus queue send --resource-group myResourceGroup --namespace-name [3] --queue-name myQueue --message-body 'Test Message'

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

AmyNamespace1

DmyNamespace2

Attempts:

3 left

💡 Hint

Common Mistakes

Using different namespace names causing resource not found errors.

All commands must use the same namespace name to work together properly.

Practice

1. What is the main purpose of messaging services in cloud systems?

easy

A. To store large files permanently

B. To speed up the internet connection

C. To allow different parts of a system to communicate smoothly and reliably

D. To replace databases entirely

Solution

1. Step 1: Understand messaging service role

   Messaging services help different parts of a system talk to each other without problems.

2. Step 2: Compare options

   Only To allow different parts of a system to communicate smoothly and reliably describes communication between system parts, which is the main purpose.

3. Final Answer:

   To allow different parts of a system to communicate smoothly and reliably -> Option C

4. Quick Check:

   Messaging services = smooth communication [OK]

Hint: Messaging services connect system parts reliably [OK]

Common Mistakes:

• Confusing messaging with file storage
• Thinking messaging speeds up internet
• Believing messaging replaces databases

2. Which Azure service is used to create message queues for reliable communication?

easy

A. Azure Functions

B. Azure Blob Storage

C. Azure Virtual Machines

D. Azure Service Bus

Solution

1. Step 1: Identify Azure services related to messaging

   Azure Service Bus is designed for messaging and queues.

2. Step 2: Eliminate unrelated services

   Blob Storage stores files, Virtual Machines run servers, Functions run code but don't create queues.

3. Final Answer:

   Azure Service Bus -> Option D

4. Quick Check:

   Queues in Azure = Service Bus [OK]

Hint: Service Bus is Azure's messaging queue service [OK]

Common Mistakes:

• Choosing Blob Storage for messaging
• Confusing Functions with queues
• Selecting Virtual Machines for messaging

3. Given this Azure Service Bus scenario: A sender puts 3 messages in a queue, and a receiver reads 2 messages. How many messages remain in the queue?

medium

A. 1

B. 3

C. 2

D. 0

Solution

1. Step 1: Count messages sent to the queue

   3 messages are added to the queue by the sender.

2. Step 2: Subtract messages read by the receiver

   The receiver reads 2 messages, so 3 - 2 = 1 message remains.

3. Final Answer:

   1 -> Option A

4. Quick Check:

   3 sent - 2 read = 1 left [OK]

Hint: Messages left = sent minus read [OK]

Common Mistakes:

• Assuming all messages are removed after reading
• Counting read messages as remaining
• Confusing total messages with unread

4. You wrote code to send messages to an Azure Service Bus queue but messages are not received. What is a common mistake to check?

medium

A. Using the wrong queue name in the code

B. Sending messages without a network connection

C. Using Azure Blob Storage instead of Service Bus

D. Running code on a virtual machine

Solution

1. Step 1: Identify common errors in messaging code

   Using the wrong queue name means messages go to a non-existent or different queue.

2. Step 2: Evaluate other options

   Network issues prevent sending but are less common; Blob Storage is unrelated; running on VM is normal.

3. Final Answer:

   Using the wrong queue name in the code -> Option A

4. Quick Check:

   Wrong queue name blocks message delivery [OK]

Hint: Check queue name matches exactly in code [OK]

Common Mistakes:

• Ignoring queue name typos
• Confusing storage services with messaging
• Assuming VM causes message loss

5. How does using Azure Service Bus topics improve system scalability compared to queues?

hard

A. Topics speed up message delivery by skipping validation

B. Topics allow multiple subscribers to receive messages independently

C. Topics store messages permanently without deletion

D. Topics replace the need for databases in applications

Solution

1. Step 1: Understand difference between queues and topics

   Queues deliver messages to one receiver; topics allow many subscribers to get messages separately.

2. Step 2: Analyze options

   Only Topics allow multiple subscribers to receive messages independently correctly describes how topics improve scalability by supporting multiple subscribers.

3. Final Answer:

   Topics allow multiple subscribers to receive messages independently -> Option B

4. Quick Check:

   Topics = multiple subscribers = better scalability [OK]

Hint: Topics support many subscribers, queues do not [OK]

Common Mistakes:

• Thinking topics store messages forever
• Believing topics skip message checks
• Confusing topics with databases