Event Hubs for streaming data in Azure - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ service_behavior

intermediate

Event Hub Partition Behavior

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?

A Events will be evenly distributed across all 4 partitions.

B All 1000 events will go to exactly 1 partition.

C Events will be randomly distributed across 2 partitions.

D Events will be distributed across 3 partitions based on load.

💡 Hint

Think about how partition keys affect event routing.

Events with the same partition key always go to the same partition to preserve order.

❓ Architecture

intermediate

Choosing Event Hub Throughput Units

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?

A 5 throughput units

B 10 throughput units

C 1 throughput unit

D 20 throughput units

💡 Hint

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.

❓ security

advanced

Securing Event Hub Access

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?

A Azure Event Hubs Contributor

B Azure Event Hubs Data Receiver

C Azure Event Hubs Data Sender

D Azure Event Hubs Data Owner

💡 Hint

Look for the role that only allows sending events.

The 'Azure Event Hubs Data Sender' role allows sending events but not reading them.

❓ Configuration

advanced

Event Hub Capture Configuration

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?

A Capture triggers immediately when 100 MB is reached, before 5 minutes.

B Capture waits full 5 minutes regardless of size.

C Capture triggers only after 5 minutes even if size is larger.

D Capture triggers randomly, ignoring size and time.

💡 Hint

Think about the 'whichever comes first' condition.

Capture triggers as soon as either condition is met, so hitting 100 MB triggers capture immediately.

✅ Best Practice

expert

Optimizing Event Hub Consumer Group Usage

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?

A Assign each application its own consumer group.

B Share a single consumer group among all applications.

C Use no consumer groups and read directly from partitions.

D Use the same consumer group but different partitions per app.

💡 Hint

Consider how consumer groups isolate read positions.

Each consumer group maintains its own read position, so separate groups prevent interference.

Practice

1. What is the main purpose of Azure Event Hubs in cloud infrastructure?

easy

A. To manage user identities and access

B. To store data permanently like a database

C. To collect and stream large amounts of data in real time from multiple sources

D. To host virtual machines for applications

Solution

1. Step 1: Understand Event Hubs role

   Event Hubs is designed to collect and stream data from many sources in real time, acting like a big pipeline for data.

2. Step 2: Compare other options

   Options A, B, and C describe other Azure services like identity management, databases, and virtual machines, not Event Hubs.

3. Final Answer:

   To collect and stream large amounts of data in real time from multiple sources -> Option C

4. Quick Check:

   Event Hubs = real-time data streaming [OK]

Hint: Event Hubs streams data live, not stores or hosts [OK]

Common Mistakes:

• Confusing Event Hubs with databases
• Thinking Event Hubs manages users
• Assuming Event Hubs runs virtual machines

2. Which of the following is the correct way to create an Event Hub namespace using Azure CLI?

easy

A. az eventhubs create namespace --resource MyNamespace --group MyResourceGroup --location eastus

B. az eventhubs namespace create --name MyNamespace --resource-group MyResourceGroup --location eastus

C. az namespace eventhubs create --name MyNamespace --group MyResourceGroup --location eastus

D. az create eventhubs namespace --resource-group MyResourceGroup --name MyNamespace --region eastus

Solution

1. Step 1: Recall Azure CLI syntax for Event Hubs namespace

   The correct command starts with az eventhubs namespace create followed by required parameters.

2. Step 2: Check parameters and order

   az eventhubs namespace create --name MyNamespace --resource-group MyResourceGroup --location eastus uses correct parameter names: --name, --resource-group, --location. Other options have wrong command order or parameter names.

3. Final Answer:

   az eventhubs namespace create --name MyNamespace --resource-group MyResourceGroup --location eastus -> Option B

4. Quick Check:

   Correct CLI syntax = az eventhubs namespace create --name MyNamespace --resource-group MyResourceGroup --location eastus [OK]

Hint: Use 'az eventhubs namespace create' with proper flags [OK]

Common Mistakes:

• Mixing command order
• Using wrong parameter names
• Confusing resource group and namespace names

3. Given an Event Hub with 4 partitions and a retention period of 2 days, what happens if data is sent continuously for 3 days without reading it?

medium

A. Data is duplicated across partitions to increase retention

B. All 3 days of data are stored permanently

C. Event Hub stops accepting new data after 2 days

D. Data older than 2 days is automatically removed, so only the last 2 days of data remain

Solution

1. Step 1: Understand retention period effect

   Retention period defines how long data is kept. After 2 days, older data is deleted automatically.

2. Step 2: Analyze continuous data sending

   Since data is sent for 3 days, data from the first day exceeds retention and is removed, leaving only last 2 days.

3. Final Answer:

   Data older than 2 days is automatically removed, so only the last 2 days of data remain -> Option D

4. Quick Check:

   Retention period limits data age [OK]

Hint: Retention period limits data age, older data is deleted [OK]

Common Mistakes:

• Assuming data is stored forever
• Thinking partitions increase retention
• Believing Event Hub stops on retention limit

4. You have an Event Hub configured with 2 partitions but your streaming application is only reading from one partition. What issue might occur?

medium

A. Data from the unread partition will accumulate and may cause delays or data loss

B. Event Hub will automatically merge partitions to fix the issue

C. The application will read data from both partitions anyway

D. Partitions do not affect data reading, so no issue occurs

Solution

1. Step 1: Understand partition role in Event Hubs

   Partitions split data streams. Each partition must be read to process all data.

2. Step 2: Analyze reading from only one partition

   If only one partition is read, data in the other partition accumulates, risking delays or data loss if retention expires.

3. Final Answer:

   Data from the unread partition will accumulate and may cause delays or data loss -> Option A

4. Quick Check:

   Unread partitions cause data buildup [OK]

Hint: Read all partitions to avoid data backlog [OK]

Common Mistakes:

• Assuming automatic partition merging
• Thinking one reader covers all partitions
• Ignoring partition impact on data flow

5. You want to design an Event Hub solution to handle a sudden spike of 10,000 events per second for 10 minutes, then normal traffic. Which approach is best to ensure no data loss and smooth processing?

hard

A. Create an Event Hub namespace with enough throughput units and increase partitions to distribute load

B. Use a single partition with default throughput units and rely on retry logic in the consumer

C. Set retention period to 1 hour to keep data longer during spikes

D. Disable partitions and use a single stream to simplify processing

Solution

1. Step 1: Understand throughput units and partitions

   Throughput units control capacity. More partitions allow parallel processing and better load distribution.

2. Step 2: Analyze spike handling

   To handle 10,000 events/sec, increase throughput units and partitions to avoid throttling and data loss during spikes.

3. Step 3: Evaluate other options

   Use a single partition with default throughput units and rely on retry logic in the consumer risks overload; C affects retention but not throughput; D disables partitions which reduces scalability.

4. Final Answer:

   Create an Event Hub namespace with enough throughput units and increase partitions to distribute load -> Option A

5. Quick Check:

   Scale throughput and partitions for spikes [OK]

Hint: Scale throughput units and partitions for high load [OK]

Common Mistakes:

• Relying on single partition for high load
• Confusing retention with throughput
• Disabling partitions reduces scalability