Event Grid vs Service Bus decision in Azure - Practice Questions

Challenge - 5 Problems

🧠 Conceptual

intermediate

When to choose Event Grid over Service Bus?

You want to build a system that reacts instantly to changes in storage blobs and routes these events to multiple independent services. Which service is best suited for this scenario?

A Use Service Bus because it supports complex message workflows and sessions.

B Use Event Grid because it is designed for event routing and supports multiple subscribers.

C Use Event Grid because it stores messages for long periods for batch processing.

D Use Service Bus because it guarantees ordered message delivery.

💡 Hint

Think about which service is optimized for event distribution to many listeners.

Event Grid is designed for reactive event routing to multiple subscribers with low latency. Service Bus is better for complex messaging patterns and guaranteed delivery.

❓ Architecture

intermediate

Designing a decoupled system with guaranteed message processing

You need to build a system where messages must be processed exactly once and in order, even if the consumer is temporarily offline. Which Azure service should you use?

A Event Grid, because it supports event replay and dead-lettering.

B Event Grid with multiple event subscriptions for redundancy.

C Service Bus without sessions because it is simpler to configure.

D Service Bus with sessions enabled to guarantee ordered, exactly-once processing.

💡 Hint

Consider which service supports message ordering and exactly-once delivery.

Service Bus with sessions supports ordered and exactly-once message processing, even if consumers are offline. Event Grid does not guarantee ordering or exactly-once delivery.

❓ service_behavior

advanced

Event Grid event delivery behavior under high load

What happens when Event Grid receives more events than it can deliver to subscribers within the retry period?

A Event Grid retries delivery for up to 24 hours and then sends undeliverable events to a dead-letter destination if configured.

B Event Grid drops the events silently without notification.

C Event Grid queues the events indefinitely until subscribers are available.

D Event Grid automatically scales subscribers to handle the load.

💡 Hint

Think about how Event Grid handles retries and failures.

Event Grid retries event delivery for up to 24 hours. If delivery still fails, events are sent to a dead-letter destination if configured, otherwise they are dropped.

❓ security

advanced

Securing message access in Service Bus vs Event Grid

You want to restrict who can send messages to your messaging system and who can receive them. Which statement is true about access control in Service Bus and Event Grid?

A Service Bus supports role-based access control (RBAC) for send and receive permissions; Event Grid only supports RBAC for event publishing.

B Event Grid supports fine-grained access control for both publishing and subscribing; Service Bus does not support RBAC.

C Both Service Bus and Event Grid only support shared access keys without RBAC.

D Service Bus does not support authentication; Event Grid uses OAuth tokens for all access.

💡 Hint

Consider which service supports RBAC for both sending and receiving messages.

Service Bus supports RBAC for controlling send and receive permissions. Event Grid supports RBAC mainly for event publishing, while subscriptions are controlled differently.

✅ Best Practice

expert

Choosing between Event Grid and Service Bus for a large-scale microservices system

You are designing a large microservices system that requires event-driven communication with low latency, high throughput, and the ability to handle millions of events per day. The system also needs to support complex workflows with message sessions and dead-lettering. Which approach is best?

A Use Service Bus exclusively because it supports message sessions and dead-lettering but may have higher latency.

B Use Event Grid exclusively because it handles millions of events with low latency and supports complex workflows.

C Use Event Grid for event routing and Service Bus for complex workflows requiring sessions and guaranteed delivery.

D Use neither; build a custom messaging system to meet all requirements.

💡 Hint

Think about combining services to leverage their strengths.

Event Grid is ideal for high-throughput, low-latency event routing. Service Bus is better for complex workflows needing sessions and guaranteed delivery. Combining both leverages their strengths.

Practice

1. Which Azure service is best suited for lightweight, event-driven notifications that require minimal setup?

easy

A. Service Bus

B. Azure Functions

C. Event Grid

D. Azure Logic Apps

Solution

1. Step 1: Understand the purpose of Event Grid

   Event Grid is designed for lightweight, event-driven notifications with simple event routing.

2. Step 2: Compare with Service Bus

   Service Bus is more complex and used for reliable, ordered messaging, not just simple notifications.

3. Final Answer:

   Event Grid -> Option C

4. Quick Check:

   Lightweight event notifications = Event Grid [OK]

Hint: Lightweight events? Think Event Grid first. [OK]

Common Mistakes:

• Confusing Service Bus with Event Grid for simple notifications
• Choosing Azure Functions or Logic Apps as messaging services

2. Which of the following is the correct way to create a Service Bus queue using Azure CLI?

easy

A. az servicebus queue create --resource-group MyGroup --namespace-name MyNamespace --name MyQueue

B. az eventgrid queue create --resource-group MyGroup --name MyQueue

C. az servicebus topic create --resource-group MyGroup --name MyQueue

D. az storage queue create --resource-group MyGroup --name MyQueue

Solution

1. Step 1: Identify the correct Azure CLI command for Service Bus queue

   The command to create a Service Bus queue includes 'az servicebus queue create' with resource group, namespace, and queue name.

2. Step 2: Eliminate incorrect commands

   Options B and D refer to Event Grid and Storage queues, not Service Bus. az servicebus topic create --resource-group MyGroup --name MyQueue creates a topic, not a queue.

3. Final Answer:

   az servicebus queue create --resource-group MyGroup --namespace-name MyNamespace --name MyQueue -> Option A

4. Quick Check:

   Service Bus queue creation uses 'az servicebus queue create' [OK]

Hint: Service Bus queue uses 'az servicebus queue create' command. [OK]

Common Mistakes:

• Using Event Grid or Storage queue commands for Service Bus
• Confusing topics with queues in Service Bus

3. Given the following scenario: An application needs to process messages in order and guarantee delivery even if the receiver is temporarily offline. Which Azure service behavior matches this requirement?

medium

A. Service Bus queues guarantee ordered delivery and support message retries.

B. Service Bus does not support message ordering.

C. Event Grid stores messages until the receiver is online.

D. Event Grid delivers events immediately but does not guarantee order or retries.

Solution

1. Step 1: Analyze delivery guarantees needed

   The app needs ordered delivery and guaranteed processing even if offline, which requires message durability and retries.

2. Step 2: Match with service features

   Service Bus queues support ordered delivery and message retries, ensuring reliable processing.

3. Final Answer:

   Service Bus queues guarantee ordered delivery and support message retries. -> Option A

4. Quick Check:

   Ordered, reliable delivery = Service Bus queues [OK]

Hint: Ordered, reliable messages? Choose Service Bus queues. [OK]

Common Mistakes:

• Assuming Event Grid guarantees order and retries
• Believing Service Bus lacks ordering support

4. You have an Event Grid subscription that is not receiving events as expected. Which of the following is the most likely cause?

medium

A. The Service Bus topic is not configured with sessions.

B. The Service Bus queue is full and blocking events.

C. The Event Grid topic does not support message ordering.

D. The Event Grid subscription endpoint URL is incorrect or unreachable.

Solution

1. Step 1: Identify common Event Grid delivery issues

   Event Grid requires a valid, reachable endpoint URL for subscriptions to receive events.

2. Step 2: Eliminate unrelated causes

   Service Bus queue full or topic session settings do not affect Event Grid subscriptions directly.

3. Final Answer:

   The Event Grid subscription endpoint URL is incorrect or unreachable. -> Option D

4. Quick Check:

   Event Grid needs reachable endpoint URL [OK]

Hint: Check endpoint URL if Event Grid events don't arrive. [OK]

Common Mistakes:

• Blaming Service Bus settings for Event Grid issues
• Ignoring endpoint URL correctness

5. A company wants to build a system that processes thousands of events per second with minimal latency, but also requires guaranteed message delivery and ordering for critical workflows. Which combination of Azure services should they use?

hard

A. Use Event Grid for all events because it is fast and supports guaranteed ordering.

B. Use Event Grid for high-volume lightweight events and Service Bus for critical ordered workflows.

C. Use Service Bus for all events because it supports ordering but may have higher latency.

D. Use Azure Storage Queues for all messaging needs.

Solution

1. Step 1: Analyze requirements for speed and reliability

   The system needs both high throughput with low latency and guaranteed delivery with ordering for some workflows.

2. Step 2: Match services to needs

   Event Grid handles high-volume, lightweight events quickly but lacks ordering guarantees. Service Bus supports ordering and reliability but with some latency.

3. Step 3: Combine services for best fit

   Using Event Grid for fast, lightweight events and Service Bus for critical ordered workflows balances speed and reliability.

4. Final Answer:

   Use Event Grid for high-volume lightweight events and Service Bus for critical ordered workflows. -> Option B

5. Quick Check:

   Mix Event Grid speed + Service Bus reliability [OK]

Hint: Combine Event Grid speed with Service Bus reliability. [OK]

Common Mistakes:

• Expecting Event Grid to guarantee ordering
• Using only Service Bus and ignoring latency needs
• Choosing Storage Queues which lack advanced features