You have a cluster with a topic t1 that already has uncompressed messages. A new Producer starts sending messages to t1 with compression enabled.
Which condition would allow this?
Kafka allows mixed compression formats within the same topic and even the same partition. Each message batch includes metadata indicating whether and how it is compressed. Therefore, a new producer can send compressed messages to a topic that already contains uncompressed messages, as long as it is configured with a compression codec (e.g., compression.type=gzip, snappy, etc.).
Why does Kafka use ZooKeeper? (Choose two.)
ZooKeeper stores metadata such as partition leadership and ISR (in-sync replicas), which brokers use to coordinate.
Kafka uses ZooKeeper to perform leader election for the Controller broker, which manages cluster metadata and leadership changes.
Which property in broker configuration specifies that a broker belongs to a particular rack?
Which property in broker configuration specifies that a broker belongs to a particular rack?
The broker.rack property is used in a Kafka broker's configuration to specify the rack or availability zone the broker belongs to. This is important for rack-aware replica placement, allowing Kafka to distribute replicas across different racks for fault tolerance.
By default, what do Kafka broker network connections have?
By default, Kafka brokers use the PLAINTEXT protocol for network communication. This means:
No encryption -- data is sent in plain text.
No authentication -- any client can connect without verifying identity.
No authorization -- there are no access control checks by default.
Security features like TLS, SASL, and ACLs must be explicitly configured.
Your Kafka cluster has four brokers. The topic t1 on the cluster has two partitions, and it has a replication factor of three. You create a Consumer Group with four consumers, which subscribes to t1.
In the scenario above, how many Controllers are in the Kafka cluster?
In a Kafka cluster, only one broker acts as the Controller at any given time. The Controller is responsible for managing cluster metadata, such as partition leadership and broker status. Even if the cluster has multiple brokers (in this case, four), only one is elected as the Controller, and others serve as regular brokers. If the current Controller fails, another broker is automatically elected to take its place.
Dennis Nguyen
28 days agoPaul Lewis
1 month agoMark Cooper
2 months agoNancy Garcia
2 months agoAshley Morris
3 months agoBrenda Walker
3 months agoDonald Moore
4 months agoAshley Ramirez
4 months agoRobert King
5 months agoMichael Jones
5 months agoJeffrey Evans
6 months agoAmy Evans
6 months agoSusan Hill
5 months agoTiffany Wright
6 months agoAnthony Martinez
5 months agoDonald Hernandez
6 months agoAntonette
7 months agoCassie
7 months agoKayleigh
7 months agoLeanora
7 months agoBritt
8 months agoLatricia
8 months agoBarney
8 months agoFrankie
8 months agoFidelia
9 months agoYuette
9 months agoElise
9 months agoFabiola
9 months agoEarleen
10 months agoLuisa
10 months agoJesusita
10 months agoTish
10 months agoDiane
11 months agoKattie
11 months agoVanesa
11 months agoJanna
11 months agoElliot
12 months agoErnest
12 months agoZena
1 year agoAshton
1 year agoDustin
1 year agoGerardo
1 year agoAnabel
1 year agoRoosevelt
1 year agoKanisha
1 year agoThora
1 year agoCarlene
1 year agoJohnetta
1 year agoShayne
1 year agoTarra
1 year ago