Broker nodes in Kafka - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is a broker node in Kafka?

A broker node is a server in a Kafka cluster that stores and manages message data. It receives messages from producers, stores them, and serves them to consumers.

beginner

How does a Kafka broker handle message storage?

A Kafka broker stores messages in partitions on disk. Each partition is an ordered, immutable sequence of messages that is continually appended to.

intermediate

What role does a broker node play in fault tolerance?

Broker nodes replicate partitions to other brokers. If one broker fails, another broker with a replica can take over, ensuring no data loss and high availability.

intermediate

Explain the difference between a leader and follower broker in Kafka.

Each partition has one leader broker that handles all reads and writes. Other brokers with replicas are followers that replicate data from the leader to stay in sync.

beginner

How do broker nodes communicate with producers and consumers?

Broker nodes use TCP connections to communicate with producers and consumers. Producers send messages to brokers, and consumers fetch messages from brokers.

What is the main function of a Kafka broker node?

A Store and manage messages

B Produce messages only

C Consume messages only

D Manage user authentication

Kafka broker nodes store and manage messages by receiving from producers and serving to consumers.

What is a partition leader in Kafka?

A A consumer that reads messages

B A backup server for Kafka

C A producer that sends messages

D A broker that handles all reads and writes for a partition

The leader broker manages all read and write requests for its partition.

How do Kafka brokers ensure data availability if one broker fails?

A By replicating partitions to follower brokers

B By deleting old messages

C By stopping all producers

D By restarting the cluster

Replication to follower brokers allows failover and data availability.

Which protocol do Kafka brokers use to communicate with clients?

A FTP

B TCP

C HTTP

D SMTP

Kafka brokers use TCP connections for communication with producers and consumers.

What happens if a follower broker falls behind the leader?

A It deletes all data

B It becomes the leader immediately

C It tries to catch up by replicating missing data

D It disconnects from the cluster

Followers replicate data from the leader to stay synchronized.

Describe the role of broker nodes in a Kafka cluster and how they manage message data.

Think about how messages flow through Kafka and where they are kept.

Explain how Kafka broker nodes handle fault tolerance and data replication.

Consider what happens if one broker stops working.

Practice

1.

What is the primary role of a broker node in Kafka?

easy

A. Store and manage Kafka messages

B. Produce messages to topics

C. Consume messages from topics

D. Monitor network traffic

Solution

1. Step 1: Understand broker node function

   A broker node is a Kafka server that stores and manages messages.

2. Step 2: Differentiate roles

   Producers send messages, consumers read them, but brokers store/manage them.

3. Final Answer:

   Store and manage Kafka messages -> Option A

4. Quick Check:

   Broker = Store/manage messages [OK]

Hint: Broker nodes store messages; producers and consumers do not [OK]

Common Mistakes:

• Confusing brokers with producers or consumers
• Thinking brokers monitor network traffic
• Assuming brokers only route messages

2.

Which of the following is the correct way to specify a broker's unique ID in the Kafka server.properties file?

easy

A. broker.id=1

B. brokerID=1

C. broker-id=1

D. brokerId=1

Solution

1. Step 1: Recall Kafka broker ID syntax

   The correct property name is broker.id with a dot separator.

2. Step 2: Check options for exact match

   Only broker.id=1 matches Kafka's expected syntax.

3. Final Answer:

   broker.id=1 -> Option A

4. Quick Check:

   Broker ID property uses dot notation [OK]

Hint: Broker ID uses dot notation: broker.id [OK]

Common Mistakes:

• Using camelCase or hyphens instead of dot
• Misspelling the property name
• Confusing broker.id with other properties

3.

Given the following snippet from a Kafka server.properties file:

broker.id=2
listeners=PLAINTEXT://localhost:9093
log.dirs=/tmp/kafka-logs-2

What will be the broker's ID and listening port when Kafka starts?

medium

A. Broker ID 1, listening on port 9092

B. Broker ID 2, listening on port 9093

C. Broker ID 2, listening on port 9092

D. Broker ID 1, listening on port 9093

Solution

1. Step 1: Identify broker ID from properties

   The property broker.id=2 sets the broker ID to 2.

2. Step 2: Identify listener port

   listeners=PLAINTEXT://localhost:9093 means the broker listens on port 9093.

3. Final Answer:

   Broker ID 2, listening on port 9093 -> Option B

4. Quick Check:

   broker.id=2 and port=9093 [OK]

Hint: Broker ID and port come directly from properties file [OK]

Common Mistakes:

• Assuming default port 9092 without checking listeners
• Mixing up broker IDs
• Ignoring the listeners property

4.

Consider this server.properties snippet:

broker.id=abc
listeners=PLAINTEXT://localhost:9092

What is the issue when starting Kafka with this configuration?

medium

A. broker.id can be a string, so no issue

B. listeners property is missing a port

C. Kafka will ignore broker.id and assign default

D. broker.id must be an integer, so 'abc' causes an error

Solution

1. Step 1: Check broker.id value type

   Kafka requires broker.id to be an integer number.

2. Step 2: Identify invalid value

   Setting broker.id=abc is invalid and causes startup error.

3. Final Answer:

   broker.id must be an integer, so 'abc' causes an error -> Option D

4. Quick Check:

   broker.id integer required [OK]

Hint: broker.id must be a number, not letters [OK]

Common Mistakes:

• Assuming broker.id can be string
• Ignoring error messages on startup
• Thinking Kafka assigns default broker.id automatically

5.

You want to run three Kafka broker nodes on the same machine for testing. Which configuration change is essential for each broker to avoid conflicts?

hard

A. Use the same broker.id but different log.dirs

B. Keep listeners port same but change broker.id

C. Assign unique broker.id and different listeners ports

D. Only change log.dirs for each broker

Solution

1. Step 1: Understand broker uniqueness requirements

   Each broker must have a unique broker.id to identify it in the cluster.

2. Step 2: Avoid port conflicts

   Each broker must listen on a different port to avoid network conflicts.

3. Final Answer:

   Assign unique broker.id and different listeners ports -> Option C

4. Quick Check:

   Unique IDs and ports prevent conflicts [OK]

Hint: Unique broker.id and ports prevent conflicts [OK]

Common Mistakes:

• Using same broker.id for multiple brokers
• Using same port for multiple brokers
• Only changing log directories without ports or IDs