Why event-driven scales applications in Kafka - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to create a Kafka producer that sends a message.

Kafka

from kafka import KafkaProducer
producer = KafkaProducer(bootstrap_servers=[1])
producer.send('my_topic', b'Hello World')
producer.flush()

Drag options to blanks, or click blank then click option'

A'localhost:9092'

B'127.0.0.1:2181'

C'localhost:2181'

D'kafka:2181'

Attempts:

3 left

💡 Hint

Common Mistakes

Using ZooKeeper port 2181 instead of Kafka broker port 9092.

Using incorrect IP or hostname.

The Kafka producer connects to the Kafka broker using the bootstrap server address, which usually runs on port 9092.

2fill in blank

medium

Complete the code to consume messages from a Kafka topic.

Kafka

from kafka import KafkaConsumer
consumer = KafkaConsumer('my_topic', bootstrap_servers=[1])
for message in consumer:
    print(message.value)

Drag options to blanks, or click blank then click option'

A'localhost:2181'

B'kafka:2181'

C'127.0.0.1:2181'

D'localhost:9092'

Attempts:

3 left

💡 Hint

Common Mistakes

Using ZooKeeper port 2181 instead of Kafka broker port 9092.

Confusing broker and ZooKeeper addresses.

The Kafka consumer connects to the Kafka broker on port 9092 to receive messages.

3fill in blank

hard

Fix the error in the code to produce messages asynchronously.

Kafka

from kafka import KafkaProducer
producer = KafkaProducer(bootstrap_servers='localhost:9092')
future = producer.send('my_topic', [1])
result = future.get(timeout=10)

Drag options to blanks, or click blank then click option'

Ab'Hello Kafka'

B'Hello Kafka'

CHello Kafka

Db"Hello Kafka"

Attempts:

3 left

💡 Hint

Common Mistakes

Sending a string instead of bytes causes errors.

Forgetting the b prefix for bytes literals.

Kafka producer expects message data as bytes, so the message must be a bytes object like b'Hello Kafka'.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that filters events with value greater than 10.

Kafka

events = {'a': 5, 'b': 15, 'c': 20}
filtered = {k: v for k, v in events.items() if v [1] 10 and k [2] 'b'}

Drag options to blanks, or click blank then click option'

A>

B<

C!=

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using < instead of > for value comparison.

Using == instead of != for key exclusion.

The comprehension keeps events where value is greater than 10 and key is not 'b'.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that uppercases keys, keeps values, and filters values greater than 10.

Kafka

events = {'a': 5, 'b': 15, 'c': 20}
result = {{ [1]: [2] for k, v in events.items() if v [3] 10 }}

Drag options to blanks, or click blank then click option'

Ak.upper()

Bv

C>

Dk.lower()

Attempts:

3 left

💡 Hint

Common Mistakes

Using k.lower() instead of k.upper().

Using < instead of > for filtering.

The comprehension creates a new dictionary with uppercase keys, original values, and filters values greater than 10.

Practice

1. What is the main reason event-driven architecture helps applications scale better?

easy

A. It forces all parts of the app to run in a single sequence.

B. It stores all data in one central database for faster access.

C. It allows different parts of the app to work independently by sending messages.

D. It requires fewer servers to run the app.

Solution

1. Step 1: Understand event-driven independence

   Event-driven design lets parts of an app send messages and work independently without waiting for each other.

2. Step 2: Connect independence to scaling

   This independence means tasks can run at the same time, helping the app handle more work smoothly as it grows.

3. Final Answer:

   It allows different parts of the app to work independently by sending messages. -> Option C

4. Quick Check:

   Event-driven = Independent parts = Scales well [OK]

Hint: Event-driven means parts work alone and talk by messages [OK]

Common Mistakes:

• Thinking event-driven forces sequential processing
• Believing event-driven centralizes all data
• Assuming event-driven reduces server count automatically

2. Which Kafka component is responsible for storing and distributing messages in an event-driven system?

easy

A. Broker

B. Producer

C. Consumer

D. Zookeeper

Solution

1. Step 1: Identify Kafka components roles

   Producer sends messages, Consumer reads messages, Broker stores and distributes messages, Zookeeper manages cluster metadata.

2. Step 2: Match storage and distribution role

   The Broker is the Kafka server that stores messages and sends them to consumers.

3. Final Answer:

   Broker -> Option A

4. Quick Check:

   Broker = Stores and distributes messages [OK]

Hint: Broker stores and sends messages in Kafka [OK]

Common Mistakes:

• Confusing Producer as storage
• Thinking Consumer stores messages
• Assuming Zookeeper handles message storage

3. Given this Kafka event-driven flow:

Producer sends 3 messages: M1, M2, M3
Consumer processes messages asynchronously

What is the expected order of message processing by the consumer?

medium

A. Messages may be processed in any order depending on consumer speed

B. M3, M2, M1 always in reverse order

C. M1, M2, M3 always in order

D. Only M1 is processed, others are ignored

Solution

1. Step 1: Understand asynchronous processing

   Consumers process messages independently and may handle them at different speeds.

2. Step 2: Analyze message order in async processing

   Because processing is asynchronous, messages can be handled in any order, not necessarily the order sent.

3. Final Answer:

   Messages may be processed in any order depending on consumer speed -> Option A

4. Quick Check:

   Async consumer = Any order processing [OK]

Hint: Async means order can vary in processing [OK]

Common Mistakes:

• Assuming strict order always preserved
• Thinking reverse order is default
• Believing some messages get ignored

4. You have this Kafka consumer code snippet:

consumer.subscribe(['topic1'])
for message in consumer:
    print(message.value)
    consumer.commit()

What is the main issue that can cause scaling problems?

medium

A. Printing message values is not allowed in Kafka consumers.

B. Calling commit() inside the loop slows processing and blocks scaling.

C. Not subscribing to the topic correctly.

D. Using a for loop instead of while True.

Solution

1. Step 1: Identify commit() impact on performance

   Calling commit() after every message waits for confirmation, slowing down processing.

2. Step 2: Understand scaling impact

   This slows consumer throughput and limits how well the app can scale with many messages.

3. Final Answer:

   Calling commit() inside the loop slows processing and blocks scaling. -> Option B

4. Quick Check:

   Frequent commit() = Slow processing = Poor scaling [OK]

Hint: Avoid commit() inside message loop for better scaling [OK]

Common Mistakes:

• Thinking subscribe() is incorrect syntax
• Believing print() causes errors
• Confusing loop type with scaling issue

5. You want to design a scalable event-driven app using Kafka that handles thousands of users sending events simultaneously. Which approach best supports scaling?

hard

A. Send events directly between users without Kafka.

B. Use a single Kafka partition and one consumer to keep order.

C. Store all events in a database first, then process them sequentially.

D. Use multiple Kafka partitions and consumers to process events in parallel.

Solution

1. Step 1: Understand Kafka partitions and consumers

   Kafka partitions allow splitting event streams so multiple consumers can read in parallel.

2. Step 2: Connect parallel processing to scaling

   Using multiple partitions and consumers lets the app handle many events at once, improving scalability.

3. Final Answer:

   Use multiple Kafka partitions and consumers to process events in parallel. -> Option D

4. Quick Check:

   Partitions + consumers = Parallel processing = Scales well [OK]

Hint: Parallel consumers on partitions scale Kafka apps best [OK]

Common Mistakes:

• Choosing single partition limits throughput
• Processing events sequentially slows app
• Skipping Kafka loses event-driven benefits