Sample questions
Azure Messaging EventingDifficulty 1
What is the main structural difference between an Azure Service Bus queue and a Service Bus topic?
- aA queue can only hold text messages, a topic can only hold binary messages
- bA queue delivers each message to a single consumer, while a topic can distribute the same message to multiple independent subscriptions.✓
- cA topic is only available in the Premium tier, a queue is available in all tiers
- dA queue requires a session ID on every message and rejects any message that omits one, while a topic never requires session IDs at all
Explanation:A queue is a point-to-point construct — one message is consumed by one receiver. A topic adds a publish/subscribe layer: each subscription attached to the topic gets its own copy of every matching message, enabling fan-out to multiple independent consumers.
Azure Messaging EventingDifficulty 1
What is the purpose of a Service Bus dead-letter queue (DLQ)?
- aIt stores a backup copy of every message that was ever successfully processed
- bIt automatically retries failed messages forever until they succeed
- cIt holds messages that could not be delivered or processed successfully, so they can be inspected separately.✓
- dIt is a separate Service Bus namespace that administrators provision exclusively for running load and performance tests
Explanation:The DLQ is a sub-queue attached to every queue and subscription where messages land when they expire, exceed the max delivery count, or are explicitly dead-lettered by the receiver — keeping problem messages isolated from the main flow for later inspection.
Azure Messaging EventingDifficulty 2
In Service Bus, a receiver uses PeekLock mode instead of ReceiveAndDelete. What does this change about message delivery?
- aPeekLock messages are delivered to every subscriber at once, ReceiveAndDelete only to one
- bPeekLock locks the message and waits for explicit completion.✓
- cPeekLock never removes the message from the queue, so it can be read unlimited times
- dReceiveAndDelete is the only mode that supports dead-lettering
Explanation:PeekLock hides the message from other receivers for a lock duration and requires an explicit Complete call; if that never happens (crash, unhandled exception), the lock expires and the message reappears — this is what makes Service Bus at-least-once rather than at-most-once. ReceiveAndDelete removes the message immediately on receipt, so a crash after receipt loses the message.
Azure Messaging EventingDifficulty 2
What is a Service Bus session used for?
- aAuthenticating a client connection against the Service Bus namespace itself before any messaging occurs
- bLimiting how many messages a single consumer instance can receive per second
- cGrouping related messages (sharing the same SessionId) so a single receiver processes them in order✓
- dEncrypting message bodies in transit between the sender and the receiver at the transport layer
Explanation:Sessions let you tag messages with a SessionId; Service Bus guarantees that all messages sharing a SessionId are handled by the same receiver in FIFO order for that session, which is essential for workflows that need ordered, related message processing (e.g. per-customer order events).
Azure Messaging EventingDifficulty 1
What kind of delivery model does Azure Event Grid primarily use to notify subscribers of an event?
- aA push model — Event Grid actively delivers the event to the subscriber's registered endpoint✓
- bA pull model — subscribers must poll Event Grid on a fixed interval to check for new events
- cA batch model — events are only delivered once a day in a single bulk file
- dA broadcast-only model with no retry or delivery guarantee at all
Explanation:Event Grid is push-based: when an event occurs, it invokes the subscriber's endpoint (webhook, Azure Function, Service Bus, Event Hubs, etc.) directly, rather than requiring the subscriber to poll for new events.
Azure Messaging EventingDifficulty 2
What is an Event Grid custom topic?
- aA predefined topic that only Azure system services (like Storage or Resource Groups) can publish to
- bA topic you create for your own application's events, to which your own code publishes custom event data✓
- cA topic that automatically merges events from every Azure resource in a subscription
- dA topic type used exclusively for Kafka-compatible streaming workloads
Explanation:Custom topics are endpoints you create specifically for your own application/business events — your code publishes events to them, unlike system topics, which are built-in endpoints exposed automatically by Azure services (Blob Storage, Resource Groups, etc.) for their own lifecycle events.