Confluent CCAAK Dumps

Kafka performs an authorization check every time a client attempts to access a resource (topics, consumer groups, etc.), ensuring real-time enforcement of security policies.

From Kafka documentation:

“Kafka checks authorization for every operation, every time the resource is accessed.”

This behavior ensures that any changes to ACLs are applied immediately and consistently.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 9, p. 284

Apache Kafka Documentation: “Kafka Security - Authorization”

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

Kafka topics support two main cleanup policies:

delete: The default policy where Kafka deletes old log segments based on retention time or size.

compact: Enables log compaction, retaining only the latest value for each key.

From Kafka documentation:

“Valid cleanup.policy values are 'delete' and 'compact'.”

B → Invalid: 'default' is not a recognized cleanup policy.

D → Invalid: 'cleanup' is not a valid keyword in this context.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 6, p. 196–197

Apache Kafka Documentation: Topic Configs – cleanup.policy

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

When a broker is shut down gracefully:

It flushes data from memory to disk to avoid log recovery upon restart.

It also notifies the controller to reassign leadership of the partitions it leads, ensuring high availability.

From Kafka documentation:

“A graceful shutdown will first flush logs to disk and then hand over leadership of partitions to ensure minimal disruption.”

C → Incorrect: Leader election happens only when the controller detects broker loss; it’s not guaranteed on restart.

D → Incorrect: Partition rebalancing is not automatic on broker restart unless manually initiated.

Page Reference:

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

Apache Kafka Documentation: Graceful Shutdown Behavior

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