[Solved] 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? | Kafka

Kafka - Event-Driven Architecture

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?

APrinting message values is not allowed in Kafka consumers.

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

CNot subscribing to the topic correctly.

DUsing a for loop instead of while True.

Step-by-Step Solution

Solution:

Step 1: Identify commit() impact on performance
Calling commit() after every message waits for confirmation, slowing down processing.
Step 2: Understand scaling impact
This slows consumer throughput and limits how well the app can scale with many messages.
Final Answer:
Calling commit() inside the loop slows processing and blocks scaling. -> Option B
Quick Check:
Frequent commit() = Slow processing = Poor scaling [OK]

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

Common Mistakes:

Master "Event-Driven Architecture" in Kafka

9 interactive learning modes - each teaches the same concept differently

More Kafka Quizzes

You have this Kafka consumer code snippet: