AZ-200 Azure Messaging & Events 1 — Questions and Answers
Question 1: What is the key difference between Azure Service Bus queues and Azure Storage queues?
- Storage queues support ordering guarantees; Service Bus does not
- Service Bus supports advanced features like sessions, dead-lettering, and duplicate detection; Storage queues are simpler and cheaper (Correct answer)
- Service Bus is free; Storage queues have per-message costs
- Storage queues support larger messages
Correct answer: Service Bus supports advanced features like sessions, dead-lettering, and duplicate detection; Storage queues are simpler and cheaper
Azure Service Bus provides enterprise messaging features like message sessions, dead-letter queues, duplicate detection, and transactions, while Storage queues are simpler and cost-effective.
Question 2: Which Azure Service Bus feature ensures that messages related to the same entity (e.g., same order ID) are processed in order by a single consumer?
- Duplicate detection
- Message deferral
- Message sessions (Correct answer)
- Topic subscriptions
Correct answer: Message sessions
Message sessions in Azure Service Bus group related messages by a session ID and guarantee ordered, exclusive processing by a single receiver.
Question 3: What happens to a Service Bus message that fails processing repeatedly and exceeds the max delivery count?
- The message is permanently deleted
- The message is moved to the dead-letter queue (DLQ) (Correct answer)
- The message is returned to the beginning of the queue
- Processing retries indefinitely
Correct answer: The message is moved to the dead-letter queue (DLQ)
When a message exceeds its maximum delivery count, Service Bus automatically moves it to the dead-letter queue (DLQ) for inspection and manual handling.
Question 4: What is the primary use case for Azure Event Grid?
- High-throughput event streaming for analytics
- Reactive, event-driven routing of discrete events to multiple subscribers (Correct answer)
- Message ordering for financial transactions
- Large message batch processing
Correct answer: Reactive, event-driven routing of discrete events to multiple subscribers
Event Grid excels at routing discrete events from Azure services or custom sources to event handlers, enabling reactive, serverless, event-driven architectures.
Question 5: What is the maximum message size supported by Azure Service Bus in the Premium tier?
- 256 KB
- 1 MB
- 4 MB
- 100 MB (Correct answer)
Correct answer: 100 MB
Azure Service Bus Premium tier supports messages up to 100 MB, while the Standard tier supports up to 256 KB.
Question 6: What is the difference between Azure Event Grid topics and Azure Service Bus topics?
- Event Grid topics are for high-throughput streaming; Service Bus topics are for low-latency messaging
- Event Grid topics route events using filters to push-based subscribers; Service Bus topics use pull-based subscriptions with message locks and acknowledgments (Correct answer)
- They are functionally identical
- Event Grid topics persist messages for 30 days; Service Bus topics do not persist
Correct answer: Event Grid topics route events using filters to push-based subscribers; Service Bus topics use pull-based subscriptions with message locks and acknowledgments
Event Grid topics use a push-based model with event subscriptions and HTTP webhooks, while Service Bus topics use pull-based consumer subscriptions with message locking and settlement.
AZ-200 Azure Messaging & Events 1
What is the key difference between Azure Service Bus queues and Azure Storage queues?