Why consumer groups enable parallel processing in Kafka - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to assign a consumer to a group.

Kafka

consumer = KafkaConsumer('my_topic', group_id=[1])

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

A'partition1'

B'topic1'

C'offset1'

D'group1'

Attempts:

3 left

💡 Hint

Common Mistakes

Using topic name instead of group ID

Using partition or offset as group ID

The group_id parameter assigns the consumer to a consumer group, enabling parallel processing.

2fill in blank

medium

Complete the code to start consuming messages in parallel.

Kafka

for message in consumer.[1]():
    print(message.value)

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

Aconsume

Bpoll

Csubscribe

Dassign

Attempts:

3 left

💡 Hint

Common Mistakes

Using subscribe() which only sets topics

Using consume() which is not a KafkaConsumer method

The poll() method fetches messages for processing.

3fill in blank

hard

Fix the error in the code to enable parallel processing with consumer groups.

Kafka

consumer = KafkaConsumer('my_topic', group_id=[1])
consumer.subscribe(['my_topic'])

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

ANone

B'my_topic'

C'my_group'

D''

Attempts:

3 left

💡 Hint

Common Mistakes

Leaving group_id as None disables consumer groups

Using empty string disables group behavior

Setting group_id to a group name enables parallel processing by dividing partitions among consumers.

4fill in blank

hard

Fill both blanks to create a dictionary comprehension that maps partitions to consumers in a group.

Kafka

partition_map = {partition: consumer[1] for partition in partitions if partition [2] 0}

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

A.assign()

B>

C==

D.subscribe()

Attempts:

3 left

💡 Hint

Common Mistakes

Using subscribe() instead of assign()

Using == instead of > in condition

The assign() method assigns partitions to consumers, and > 0 filters partitions.

5fill in blank

hard

Fill all three blanks to create a dictionary comprehension that filters messages by offset and assigns them to a consumer group.

Kafka

filtered_messages = {msg[1]: msg.value for msg in messages if msg.offset [2] [3]

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

A.key

B>

C100

D==

Attempts:

3 left

💡 Hint

Common Mistakes

Using offset as key instead of message key

Using == instead of > for filtering

Using wrong offset value

We use .key as dictionary keys, filter messages with offset greater than 100.

Practice

1. What is the main reason consumer groups enable parallel processing in Kafka?

easy

A. They limit the number of messages a consumer can read at once.

B. They duplicate messages to all consumers for faster processing.

C. They combine all messages into a single stream for one consumer.

D. They allow multiple consumers to read different partitions of a topic simultaneously.

Solution

1. Step 1: Understand consumer groups and partitions

   Consumer groups split topic partitions among consumers so each reads a unique subset.

2. Step 2: Recognize parallel processing benefit

   Because consumers read different partitions at the same time, processing happens in parallel.

3. Final Answer:

   They allow multiple consumers to read different partitions of a topic simultaneously. -> Option D

4. Quick Check:

   Parallel reading = multiple consumers on partitions [OK]

Hint: Think: multiple consumers share partitions, not duplicate messages [OK]

Common Mistakes:

• Thinking all consumers get all messages
• Believing messages are duplicated for speed
• Confusing parallel with sequential processing

2. Which of the following is the correct way to assign a consumer to a group in Kafka's consumer configuration?

easy

A. group.id = "my-group"

B. consumer.group = "my-group"

C. groupName = "my-group"

D. assign.group = "my-group"

Solution

1. Step 1: Recall Kafka consumer configuration keys

   The correct key to set the consumer group is 'group.id'.

2. Step 2: Match the correct syntax

   Only 'group.id = "my-group"' matches Kafka's expected configuration format.

3. Final Answer:

   group.id = "my-group" -> Option A

4. Quick Check:

   Kafka uses 'group.id' to set consumer groups [OK]

Hint: Remember Kafka config uses 'group.id' for groups [OK]

Common Mistakes:

• Using incorrect keys like 'consumer.group'
• Confusing variable names with config keys
• Missing quotes around group name

3. Given a topic with 4 partitions and a consumer group with 2 consumers, what will happen when both consumers start reading?

medium

A. Each consumer reads 2 unique partitions, no overlap.

B. Each consumer reads all 4 partitions simultaneously.

C. Only one consumer reads all partitions; the other waits.

D. Consumers randomly read any partition, possibly overlapping.

Solution

1. Step 1: Understand partition assignment in consumer groups

   Partitions are divided among consumers so each partition is read by only one consumer.

2. Step 2: Calculate partition distribution

   With 4 partitions and 2 consumers, each consumer gets 2 partitions uniquely.

3. Final Answer:

   Each consumer reads 2 unique partitions, no overlap. -> Option A

4. Quick Check:

   Partitions split evenly among consumers [OK]

Hint: Partitions divide evenly among consumers in a group [OK]

Common Mistakes:

• Assuming consumers read all partitions
• Thinking partitions overlap between consumers
• Believing one consumer reads everything

4. You have 3 consumers in a group but only 2 partitions in the topic. What issue will occur?

medium

A. All consumers will share partitions equally.

B. One consumer will be idle with no partitions assigned.

C. Kafka will create a new partition automatically.

D. Consumers will read duplicate messages from partitions.

Solution

1. Step 1: Analyze partition to consumer ratio

   There are fewer partitions (2) than consumers (3), so not all consumers get partitions.

2. Step 2: Understand assignment behavior

   Kafka assigns partitions exclusively; one consumer will have no partition and remain idle.

3. Final Answer:

   One consumer will be idle with no partitions assigned. -> Option B

4. Quick Check:

   Partitions < consumers means idle consumers [OK]

Hint: More consumers than partitions means some idle consumers [OK]

Common Mistakes:

• Expecting Kafka to auto-create partitions
• Assuming consumers share partitions simultaneously
• Thinking all consumers always get messages

5. You want to maximize parallel processing for a topic with 5 partitions. Which setup best achieves this?

hard

A. Create 5 separate consumer groups with one consumer each.

B. Create a consumer group with 3 consumers, each reading multiple partitions.

C. Create a consumer group with 5 consumers, each reading one partition.

D. Create a single consumer reading all partitions sequentially.

Solution

1. Step 1: Understand parallelism limits

   Maximum parallelism equals the number of partitions because each partition can be read by only one consumer in a group.

2. Step 2: Match consumers to partitions

   Having 5 consumers in one group allows each to read one partition simultaneously, maximizing parallel processing.

3. Step 3: Evaluate other options

   Less than 5 consumers reduce parallelism; multiple groups duplicate messages; single consumer is sequential.

4. Final Answer:

   Create a consumer group with 5 consumers, each reading one partition. -> Option C

5. Quick Check:

   Consumers = partitions maximizes parallel processing [OK]

Hint: Match consumer count to partitions for max parallelism [OK]

Common Mistakes:

• Creating multiple groups duplicates messages, not parallelism
• Using fewer consumers limits parallel processing
• Thinking one consumer can process partitions in parallel