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.