Confluent Certified Administrator CCAAK Full Course Free

Kafka supports multiple listeners, allowing you to configure different security settings for internal and external traffic. For example, one listener can use PLAINTEXT for internal replication traffic, and another can use SASL_SSL for external client traffic.

From Kafka documentation:

“Kafka allows configuration of multiple listeners to segregate internal and external traffic, each with its own security protocol.”

B → Correct: Enables secure and isolated communication channels.

A → Unnecessary and inefficient.

C → Invalid: A single listener supports only one protocol.

D → Not a Kafka-level configuration.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 10, p. 305

Apache Kafka Documentation: Security Configuration – Multiple Listeners

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

Kafka consumers in a consumer group consume partitions exclusively. With 4 partitions and only 2 consumers, each consumer is processing 2 partitions. To increase parallelism, more consumers can be added to the group (up to 4) so that each consumer handles fewer partitions, which reduces the lag.

From Kafka documentation:

“Increasing the number of consumers in a group increases parallelism and helps reduce lag, assuming there are enough partitions.”

A → Ineffective unless followed by rebalancing and consumer scaling.

B → Would create a separate group and not share load.

C → Not applicable; consumers don’t acknowledge messages like producers.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 4, p. 127–129

Apache Kafka Documentation: Consumer Group Behavior

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

Kafka architecture maintains exactly one active Controller at any given time, regardless of the number of brokers. The Controller is responsible for administrative tasks like partition leader election and topic creation. The remaining brokers are replicas, ready to take over if the Controller fails.

From Kafka documentation:

“At any given time, there is only one active controller in the Kafka cluster.”

Even in a cluster with 4 brokers, only 1 broker acts as the Controller.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 6, p. 189

Apache Kafka Documentation: Controller Role Description

‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾‾

The kafka-consumer-groups.sh script is used to monitor consumer group offsets and lag. It shows the current offset, log end offset, and lag for each partition consumed by a consumer group.

From Kafka documentation:

“You can use kafka-consumer-groups.sh with the --describe flag to get the offset lag per consumer group.”

A → Incorrect: No such built-in script.

B → Correct: Official script for viewing consumer group lag.

C → Incorrect: Does not exist as a built-in Kafka tool.

D → Incorrect: Used for partition reassignment, unrelated to lag monitoring.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 10, p. 308

Apache Kafka Documentation: kafka-consumer-groups.sh usage