Azure Messaging and Event-Driven Solutions Flashcards

What is the key difference between Azure Service Bus queues and Azure Storage queues?

Answer: Service Bus supports advanced messaging features like dead-lettering, sessions, and transactions

Service Bus provides enterprise messaging with dead-letter queues, message sessions, duplicate detection, and transactions not available in Storage queues.

In Azure Service Bus, what feature ensures that only one consumer processes a related group of messages in order?

Answer: Message sessions

Message sessions (enabled per queue/subscription) group related messages by session ID and guarantee ordered, exclusive processing by one consumer at a time.

What is the default Time-to-Live (TTL) for messages in an Azure Service Bus queue?

Answer: It is set to TimeSpan.MaxValue (no expiry by default)

By default, Service Bus messages have a TTL of `TimeSpan.MaxValue`, meaning they do not expire unless a custom TTL is set on the queue or message.

Which Azure event service is best suited for high-throughput telemetry ingestion from IoT devices?

Answer: Azure Event Hubs

Azure Event Hubs is designed for high-throughput streaming of millions of events per second, making it ideal for telemetry and log ingestion.

What protocol does Azure Event Hubs use that is compatible with Apache Kafka producers and consumers?

Answer: Kafka Protocol (port 9093)

Event Hubs exposes a Kafka-compatible endpoint on port 9093, allowing existing Kafka clients to send and receive events without code changes.

In Azure Event Grid, what resource subscribes to events from a source and routes them to a handler endpoint?

Answer: Event subscription

An event subscription defines the filter criteria and the destination endpoint (e.g., webhook, Function, or queue) that receives matching events.