Event Grid for event routing in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Event Grid subscription filtering behavior

You have an Azure Event Grid topic with multiple event subscriptions. One subscription uses a filter to only receive events where the eventType is Contoso.Items.Created. What happens when an event with eventType Contoso.Items.Updated is published?

A The subscription does not receive the event because the event type does not match the filter.

B The event is rejected by Event Grid and not delivered to any subscription.

C The subscription receives the event but with a warning.

D The subscription receives the event because it matches the topic.

💡 Hint

Think about how filters work in Event Grid subscriptions.

Event Grid delivers events only to subscriptions whose filters match the event properties. If the event type does not match the filter, the event is not delivered to that subscription.

❓ Architecture

intermediate

Choosing Event Grid for event routing

You want to build a system where multiple services react to events from various sources in near real-time. Which feature of Azure Event Grid makes it suitable for this scenario?

A Event Grid only supports events from Azure Blob Storage.

B Event Grid provides push-based event delivery with low latency and supports multiple subscribers.

C Event Grid requires polling to receive events.

D Event Grid supports direct database queries for event storage.

💡 Hint

Consider how Event Grid delivers events to subscribers.

Event Grid uses push-based delivery to send events to multiple subscribers quickly and supports many event sources, making it ideal for near real-time event routing.

❓ security

advanced

Securing Event Grid event subscriptions

You want to ensure that only authorized services can subscribe to your Event Grid topic. Which method provides the best security for event subscription authentication?

A Use Azure Active Directory (AAD) authentication with managed identities for the subscription endpoint.

B Use a shared access key in the subscription endpoint URL.

C Use IP filtering on the Event Grid topic to allow all IPs.

D No authentication is needed because Event Grid is secure by default.

💡 Hint

Think about modern Azure security best practices.

Using Azure Active Directory authentication with managed identities ensures secure, token-based authentication for event subscriptions, which is more secure than shared keys or IP filtering alone.

❓ Configuration

advanced

Event Grid dead-letter destination configuration

You want to configure an Event Grid subscription to send undeliverable events to a dead-letter destination. Which of the following is a valid dead-letter destination for Event Grid?

A Azure SQL Database table

B Azure Virtual Machine disk

C Azure Blob Storage container

D Azure Cosmos DB container

💡 Hint

Dead-letter destinations must be storage services that can hold event data.

Event Grid supports Azure Blob Storage containers as dead-letter destinations to store undeliverable events for later inspection or replay.

✅ Best Practice

expert

Optimizing Event Grid event routing for high scale

You have an Event Grid topic receiving thousands of events per second. To optimize event routing and reduce latency, which approach is best?

A Create a single subscription with no filters to receive all events and process filtering in the subscriber.

B Use polling on the Event Grid topic to batch events before processing.

C Disable retry policies to avoid duplicate events.

D Create multiple subscriptions with filters to route only relevant events to each subscriber.

💡 Hint

Think about how filtering affects event delivery and processing load.

Using multiple subscriptions with filters reduces unnecessary event delivery and processing, improving performance and reducing latency at scale.