Why topics organize messages in Kafka - Quick Recap

Recall & Review

beginner

What is a topic in Kafka?

A topic in Kafka is like a category or folder where messages are stored and organized. It helps group similar messages together so consumers can read them easily.

beginner

Why does Kafka use topics to organize messages?

Kafka uses topics to organize messages so that producers can send messages to specific categories, and consumers can subscribe to only the topics they care about. This keeps data organized and efficient.

intermediate

How do topics help in message delivery in Kafka?

Topics help by acting as channels where messages are stored in order. Consumers read messages from topics, ensuring they get the right data in the right sequence.

beginner

What happens if messages were not organized by topics?

Without topics, messages would be mixed up, making it hard for consumers to find and process the messages they need. It would be like searching for a book in a messy library without sections.

intermediate

How do topics improve scalability in Kafka?

Topics allow Kafka to split messages into partitions, which can be handled by different servers. This makes it easy to handle lots of messages and users at the same time.

What is the main purpose of a topic in Kafka?

A To display messages on screen

B To store user passwords

C To run database queries

D To organize messages into categories

Topics organize messages into categories so producers and consumers can manage data efficiently.

How do consumers use topics in Kafka?

A They send messages to topics

B They create new topics automatically

C They subscribe to topics to read messages

D They delete topics after reading

Consumers subscribe to topics to receive and process messages relevant to them.

What would happen if Kafka did not use topics?

A Messages would be mixed and hard to find

B Messages would be faster

C Messages would be encrypted automatically

D Messages would be deleted immediately

Without topics, messages would be disorganized, making it difficult to manage and consume them.

How do topics help Kafka scale to many users?

A By storing messages in a single file

B By splitting messages into partitions handled by different servers

C By limiting the number of messages

D By deleting old messages quickly

Topics can be divided into partitions, allowing Kafka to handle large amounts of data across servers.

Which of these best describes a Kafka topic?

A A message category or channel

B A user account

C A database table

D A network protocol

A Kafka topic is a category or channel where messages are grouped.

Explain why Kafka uses topics to organize messages and how this helps producers and consumers.

Think about how sorting mail into boxes helps delivery.

Describe how topics contribute to Kafka's ability to handle many messages and users at once.

Imagine dividing work among many helpers.

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