0
0
Kafkadevops~5 mins

Broker configuration basics in Kafka - Cheat Sheet & Quick Revision

Choose your learning style9 modes available
Recall & Review
beginner
What is a Kafka broker?
A Kafka broker is a server that stores and serves Kafka topics. It handles data storage, message delivery, and client requests.
Click to reveal answer
beginner
What does the broker.id configuration do?
The broker.id is a unique identifier for each Kafka broker in the cluster. It helps Kafka distinguish between brokers.
Click to reveal answer
beginner
Why is log.dirs important in broker configuration?
log.dirs specifies the directory where Kafka stores its log data (messages). It must point to a valid disk location.
Click to reveal answer
intermediate
What is the role of zookeeper.connect in Kafka broker config?
zookeeper.connect tells the broker how to connect to ZooKeeper, which manages cluster metadata and broker coordination.
Click to reveal answer
intermediate
How does num.network.threads affect broker performance?
num.network.threads sets how many threads handle network requests. More threads can improve throughput but use more CPU.
Click to reveal answer
What must each Kafka broker have to be uniquely identified in a cluster?
Azookeeper.connect
Blog.dirs
Cbroker.id
Dnum.network.threads
Which configuration specifies where Kafka stores its message logs?
Abroker.id
Bnum.network.threads
Czookeeper.connect
Dlog.dirs
What does zookeeper.connect configure?
AConnection to ZooKeeper service
BLog storage location
CBroker's unique ID
DNumber of network threads
Increasing num.network.threads will likely:
AImprove network request handling
BDecrease CPU usage
CChange broker ID
DModify log directory
Which of these is NOT a broker configuration?
Abroker.id
Btopic.name
Czookeeper.connect
Dlog.dirs
Explain the purpose of the broker.id and why it is important in Kafka broker configuration.
Think about how Kafka knows which server is which.
You got /3 concepts.
    Describe how log.dirs and zookeeper.connect work together in Kafka broker setup.
    One handles data storage, the other handles cluster metadata.
    You got /4 concepts.