Confluent CCAAK Exam With Confidence Using Practice Dumps

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

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

To increase throughput, Kafka recommends allowing larger batches and giving more time for the producer to accumulate records into batches:

batch.size: Increasing this allows more records to be sent in a single request.

linger.ms: Increasing this adds a delay so that the producer can accumulate more messages into a batch.

From Kafka documentation:

“Increasing both batch.size and linger.ms allows the producer to send larger, more efficient batches, improving throughput at the cost of slightly increased latency.”

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 5, p. 162–163

Apache Kafka Documentation: Producer Configuration Parameters

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

Kafka supports quotas to limit the broker resources each client can use. This is used to prevent one client from monopolizing cluster bandwidth.

From Kafka documentation:

“Quotas can be applied to both producers and consumers. These quotas are enforced based on the number of bytes per second, and they are applied to ensure fair usage of broker resources.”

A. Quotas → Correct: Admins can define quotas on throughput per client ID or user.

B. Consumer Groups → Incorrect: This controls parallelism in consumption but not resource fairness.

C. Rebalancing → Incorrect: This helps with load balancing but not with resource limitation.

D. ACLs → Incorrect: ACLs define access permissions but not resource usage.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 10 (“Administering Kafka”), p. 306–308

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