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

Challenge - 5 Problems

❓ service_behavior

intermediate

Event Grid Event Delivery Behavior

What happens if an Azure Event Grid event subscriber endpoint is temporarily unavailable?

A Event Grid retries delivery for up to 24 hours with exponential backoff.

B Event Grid immediately drops the event and does not retry.

C Event Grid retries delivery indefinitely until the endpoint is available.

D Event Grid queues the event permanently until the subscriber manually acknowledges.

💡 Hint

Think about how cloud services handle temporary failures to avoid losing events.

Azure Event Grid retries event delivery for up to 24 hours using exponential backoff. This ensures temporary issues do not cause event loss.

❓ Architecture

intermediate

Choosing Event Grid for Event Routing

You want to build a system where multiple microservices react to events from blob storage changes. Which feature of Event Grid makes it the best choice?

A Event Grid stores all events permanently for audit purposes.

B Event Grid supports multiple event handlers subscribing to the same event source with low latency.

C Event Grid requires polling to detect new events.

D Event Grid only supports one subscriber per event source.

💡 Hint

Consider how events are delivered to multiple services efficiently.

Event Grid supports multiple subscribers to the same event source and delivers events with low latency, enabling event-driven microservices.

❓ security

advanced

Securing Event Grid Event Subscriptions

Which method provides the strongest security for authenticating Event Grid event delivery to a webhook endpoint?

A Use Azure Active Directory (AAD) token-based authentication for the webhook.

B Use a shared access signature (SAS) token in the webhook URL.

C Use IP filtering on the webhook endpoint only.

D Use HTTP Basic Authentication with a username and password.

💡 Hint

Think about modern, secure token-based authentication methods supported by Azure services.

Azure Active Directory token-based authentication provides strong, managed identity-based security for Event Grid webhook endpoints.

❓ Configuration

advanced

Event Grid Subscription Filtering Configuration

You want to configure an Event Grid subscription to only receive events where the subject starts with 'orders/' and the event type is 'OrderCreated'. Which filter configuration is correct?

A {"subjectBeginsWith": "OrderCreated", "includedEventTypes": ["orders/"]}

B {"subjectEndsWith": "orders/", "includedEventTypes": ["OrderCreated"]}

C {"subjectBeginsWith": "orders/", "includedEventTypes": ["OrderCreated"]}

D {"subjectContains": "orders/", "excludedEventTypes": ["OrderCreated"]}

💡 Hint

Check the filter properties for subject prefix and event types.

The correct filter uses 'subjectBeginsWith' for the prefix and 'includedEventTypes' to specify the event type to receive.

✅ Best Practice

expert

Designing for High Availability with Event Grid

You design an event-driven system using Event Grid with multiple subscribers. To ensure no event loss during regional outages, what is the best architectural practice?

A Use Event Grid with only one subscriber to simplify recovery.

B Use a single Event Grid topic in one region and rely on Event Grid's internal replication.

C Configure subscribers to poll Event Grid for missed events after an outage.

D Deploy Event Grid topics and subscribers in multiple Azure regions and use geo-redundant storage for event data.

💡 Hint

Think about spreading resources across regions to handle failures.

Deploying Event Grid topics and subscribers across multiple regions with geo-redundant storage ensures high availability and no event loss during regional failures.