Why topics organize messages in Kafka - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why does Kafka use topics to organize messages?

Kafka organizes messages into topics. What is the main reason for this design?

A To encrypt messages automatically for security

B To store messages in a random order for faster retrieval

C To limit the number of messages a producer can send

D To group related messages so consumers can subscribe to specific streams of data

💡 Hint

Think about how consumers get messages they want.

Topics group related messages so consumers can subscribe to only the data they need, making message handling efficient and organized.

❓ Predict Output

intermediate

What is the output when subscribing to a Kafka topic?

Given a Kafka topic named 'orders' with messages: 'order1', 'order2', 'order3', what will a consumer receive when subscribed to this topic?

A The consumer receives only the last message: 'order3'

B The consumer receives all messages: 'order1', 'order2', 'order3' in order

C The consumer receives messages in random order

D The consumer receives no messages until a new one is produced

💡 Hint

Think about how Kafka delivers messages from a topic.

Consumers subscribed to a topic receive all messages in the order they were produced, ensuring no message is missed.

🔧 Debug

advanced

Why does this Kafka consumer miss some messages?

Consider this Kafka consumer code snippet that subscribes to a topic but misses some messages:

consumer.subscribe(['sales'])
consumer.poll(0)
consumer.close()

What is the likely reason?

A The consumer polls with zero timeout and closes immediately, not waiting for messages

B The topic name 'sales' is incorrect and does not exist

C The consumer group ID is missing causing no messages to be assigned

D Kafka topics do not support polling messages

💡 Hint

Think about how polling works in Kafka consumers.

Polling with zero timeout returns immediately without waiting for messages. Closing the consumer right after means no messages are processed.

📝 Syntax

advanced

Identify the syntax error in Kafka topic subscription code

Which option contains a syntax error in subscribing a Kafka consumer to a topic?

Kafka

consumer.subscribe('payments')

A consumer.subscribe('payments')

B consumer.subscribe({'payments'})

C consumer.subscribe(['payments'])

D consumer.subscribe(('payments'))

💡 Hint

Check the expected argument type for subscribe method.

The subscribe method expects a list of topics, not a single string. Passing a string causes an error.

🚀 Application

expert

How do Kafka topics help scale message processing?

Kafka topics are divided into partitions. How does this help scale message processing?

A Partitions limit the number of messages stored in a topic

B Partitions encrypt messages to improve security

C Partitions allow multiple consumers to read from the same topic in parallel, increasing throughput

D Partitions automatically delete old messages to save space

💡 Hint

Think about how dividing work helps many workers process faster.

Partitions split a topic into parts so multiple consumers can read different partitions at the same time, making processing faster and scalable.

Practice

1. Why does Kafka use topics to organize messages?

easy

A. To group related messages together for easier management

B. To store messages permanently on the producer side

C. To encrypt messages automatically

D. To limit the number of messages sent

Solution

1. Step 1: Understand the purpose of topics in Kafka

   Topics are used to group messages that belong to the same category or stream.

2. Step 2: Identify the role of topics in message management

   Grouping messages helps producers and consumers handle data efficiently and logically.

3. Final Answer:

   To group related messages together for easier management -> Option A

4. Quick Check:

   Topics group messages = A [OK]

Hint: Topics group messages logically for easy handling [OK]

Common Mistakes:

• Thinking topics store messages on producer side
• Confusing topics with encryption features
• Believing topics limit message quantity

2. Which of the following is the correct way to create a topic in Kafka using the command line?

easy

A. kafka topic create myTopic --partitions 3

B. kafka-topics --create --topic myTopic --partitions 3 --replication-factor 1 --bootstrap-server localhost:9092

C. create kafka topic myTopic partitions=3

D. kafka-create-topic --name myTopic --partitions 3

Solution

1. Step 1: Recall the Kafka CLI syntax for topic creation

   The correct command uses 'kafka-topics' with '--create' and required flags.

2. Step 2: Match the command with the correct options

   kafka-topics --create --topic myTopic --partitions 3 --replication-factor 1 --bootstrap-server localhost:9092 matches the official syntax including bootstrap-server, partitions, and replication-factor.

3. Final Answer:

   kafka-topics --create --topic myTopic --partitions 3 --replication-factor 1 --bootstrap-server localhost:9092 -> Option B

4. Quick Check:

   Correct Kafka topic creation syntax = D [OK]

Hint: Use kafka-topics with --create and required flags [OK]

Common Mistakes:

• Using incorrect command names like kafka-create-topic
• Omitting bootstrap-server flag
• Wrong order or missing required flags

3. Given a Kafka topic with 3 partitions, what happens when a producer sends 6 messages without specifying a key?

medium

A. Messages are sent randomly to any partition

B. All messages go to the first partition

C. Messages are distributed evenly across the 3 partitions

D. Messages are rejected because no key is provided

Solution

1. Step 1: Understand default partitioning behavior without a key

   When no key is provided, Kafka uses round-robin to distribute messages evenly across partitions.

2. Step 2: Apply this to 6 messages and 3 partitions

   Messages will be sent 2 per partition, balancing the load.

3. Final Answer:

   Messages are distributed evenly across the 3 partitions -> Option C

4. Quick Check:

   No key means round-robin distribution = A [OK]

Hint: No key means even round-robin distribution [OK]

Common Mistakes:

• Assuming all messages go to one partition
• Thinking messages are rejected without a key
• Believing distribution is random without pattern

4. You have a Kafka topic with 2 partitions but your consumer only reads from partition 0. What is the likely problem?

medium

A. Kafka does not support multiple partitions

B. The topic only has one partition

C. The producer is sending messages only to partition 1

D. The consumer is not configured to subscribe to all partitions

Solution

1. Step 1: Analyze consumer subscription behavior

   If a consumer reads only from partition 0, it likely subscribed only to that partition explicitly.

2. Step 2: Check topic partition count and producer behavior

   The topic has 2 partitions, so consumer should subscribe to both to read all messages.

3. Final Answer:

   The consumer is not configured to subscribe to all partitions -> Option D

4. Quick Check:

   Consumer subscription controls partitions read = C [OK]

Hint: Consumer must subscribe to all partitions to read all messages [OK]

Common Mistakes:

• Assuming topic has only one partition
• Believing Kafka does not support multiple partitions
• Thinking producer controls consumer reading partitions

5. How can partitioning in Kafka topics improve performance when handling large message streams?

hard

A. By allowing parallel processing of messages across multiple consumers

B. By encrypting messages faster

C. By reducing the total number of messages sent

D. By storing messages only on the producer side

Solution

1. Step 1: Understand the role of partitions in Kafka topics

   Partitions split a topic into multiple parts that can be processed independently.

2. Step 2: Connect partitions to performance benefits

   Multiple consumers can read from different partitions in parallel, increasing throughput and speed.

3. Final Answer:

   By allowing parallel processing of messages across multiple consumers -> Option A

4. Quick Check:

   Partitions enable parallelism = B [OK]

Hint: Partitions enable parallel consumer processing [OK]

Common Mistakes:

• Confusing partitioning with encryption
• Thinking partitioning reduces message count
• Believing messages are stored only on producer