Azure Event Grid

Question 1

What is Azure Event Grid and what does it do?

Answer 1

Azure Event Grid is a fully managed event routing service that simplifies event-based communication and supports a publish-subscribe model.

Question 2

What are some common use cases for Azure Event Grid?

Answer 2

Azure Event Grid is commonly used for event-driven applications, serverless architecture, real-time notifications, and integrating services like Azure Functions.

Question 3

How does Event Grid handle message delivery?

Answer 3

Event Grid guarantees at least once delivery and offers dead-lettering to ensure no messages are lost.

Question 4

What are Event Grid topics?

Answer 4

Topics are channels that event sources can use to send their events.

Question 5

What are Event Grid subscriptions?

Answer 5

Subscriptions define which events a subscriber wants to receive from an event source.

Question 6

How do custom topics work in Event Grid?

Answer 6

Custom topics are user-defined topics that can be used to publish custom events.

Question 7

What is the difference between system topics and custom topics?

Answer 7

System topics are built-in for Azure services, whereas custom topics are user-defined.

Question 8

What are the pricing considerations for Event Grid?

Answer 8

Azure Event Grid charges based on the number of operations, such as publishing events and delivering messages.

Question 9

What is an event handler in Event Grid?

Answer 9

An event handler processes the events delivered by Event Grid.

Question 10

Can Event Grid integrate with third-party services?

Answer 10

Yes, Event Grid can be used to route events to third-party services via webhooks.

Question 11

What is the maximum number of event subscriptions per topic?

Answer 11

Each topic supports up to 500 event subscriptions.

Question 12

How does Event Grid ensure security during event transmission?

Answer 12

Event Grid uses HTTPS for secure event delivery and supports managed identities for secure access to resources.

Question 13

What is a dead-letter queue in Event Grid?

Answer 13

The dead-letter queue stores undeliverable messages for future inspection and troubleshooting.

Question 14

How does Event Grid handle retries for failed deliveries?

Answer 14

Event Grid automatically retries failed event deliveries based on a built-in retry policy.

Question 15

What are the supported event formats in Event Grid?

Answer 15

Event Grid supports multiple formats including JSON, CloudEvents v1.0, and Event Grid schema.

Question 16

Can Event Grid handle high throughput?

Answer 16

Yes, Event Grid is designed to handle millions of events per second.

Question 17

How do event filtering rules work in Event Grid?

Answer 17

Event subscriptions can include filters to specify which events should be sent to subscribers based on event type or content.

Question 18

What are the retry policies available in Event Grid?

Answer 18

Event Grid supports exponential backoff and retry policies for failed deliveries.

Question 19

How does Azure Event Grid differ from Azure Event Hubs?

Answer 19

Event Grid is for event-based communication, while Event Hubs is designed for high-throughput streaming data ingestion.

Question 20

What is the maximum event size supported by Event Grid?

Answer 20

Event Grid supports a maximum event size of 1 MB.

Question 21

How can you monitor Event Grid activities?

Answer 21

Event Grid activities can be monitored through Azure Monitor and diagnostic logs.

Question 22

What are the benefits of using Event Grid over polling for event notifications?

Answer 22

Event Grid eliminates the need for continuous polling and delivers events in near real-time.

Question 23

What is the role of managed identities in Event Grid?

Answer 23

Managed identities allow secure access to resources like Azure Functions without needing explicit credentials.

Question 24

How does Event Grid support event-driven architecture?

Answer 24

Event Grid provides a way to build loosely coupled systems that react to events across services and resources.

Question 25

What types of events are supported by Azure Event Grid?

Answer 25

Event Grid supports various types of events, including resource events, custom events, and third-party webhooks.

Question 26

What is the benefit of using Event Grid for serverless applications?

Answer 26

Event Grid enables serverless applications to react to changes in resources or systems without the need for manual triggers.

Question 27

What is the latency of event delivery in Event Grid?

Answer 27

Event Grid delivers events with a latency of less than 60 seconds in most cases.

Question 28

Can Event Grid handle cross-region event delivery?

Answer 28

Yes, Event Grid can deliver events across different Azure regions.

Question 29

How does Event Grid support disaster recovery?

Answer 29

Event Grid supports disaster recovery through cross-region replication and redundant infrastructure.

Question 30

How do you create a custom event schema in Event Grid?

Answer 30

Custom event schemas can be created and published using custom topics in Event Grid.

Question 31

What is the role of webhooks in Azure Event Grid?

Answer 31

Webhooks act as event handlers that receive events from Event Grid and trigger actions in third-party services or custom applications.

Question 32

When should I choose Event Grid over Event Hub?

Answer 32

1. Azure Event Hub is designed for large-scale data ingestion. It can handle millions of messages per second and supports message persistence. It is ideal for high-throughput scenarios like telemetry and streaming. 2. Azure Event Grid, while also supporting event-driven architecture, is optimized for lightweight event notifications. It focuses on event distribution rather than handling a massive influx of messages over time. It does not focus on message persistence like Event Hub does.