You have an Azure Event Hub with 4 partitions. You send 1000 events with the same partition key. How many partitions will these events be distributed across?
Think about how partition keys affect event routing.
Events with the same partition key always go to the same partition to preserve order.
You expect to send 20 MB per second of data to an Event Hub. Each throughput unit supports 1 MB/s ingress. How many throughput units should you provision?
Each throughput unit supports 1 MB/s ingress.
You need one throughput unit per 1 MB/s of ingress, so 20 MB/s requires 20 units.
You want to allow a service to send events to your Event Hub but not read from it. Which Azure role should you assign to the service's managed identity?
Look for the role that only allows sending events.
The 'Azure Event Hubs Data Sender' role allows sending events but not reading them.
You configure Event Hub Capture to save data to Azure Blob Storage every 5 minutes or 100 MB, whichever comes first. What happens if 100 MB is reached before 5 minutes?
Think about the 'whichever comes first' condition.
Capture triggers as soon as either condition is met, so hitting 100 MB triggers capture immediately.
You have multiple independent applications reading from the same Event Hub. What is the best practice to ensure each application reads all events without interfering with others?
Consider how consumer groups isolate read positions.
Each consumer group maintains its own read position, so separate groups prevent interference.