Confluent Updated CCAAK Exam Questions and Answers by harper-rose

Kafka supports topic deletion via the kafka-topics.sh tool if the broker property delete.topic.enable=true. This is the recommended and cleanest method to delete a topic and its data from the cluster.

From Kafka documentation:

“To delete a topic, use kafka-topics.sh with --delete flag, provided delete.topic.enable is set to true on the broker.”

A → Correct: Official method.

B → Misunderstood use of null keys (used for compaction).

C → Not recommended; causes inconsistent state.

D → Deletes consumer state, not the topic itself.

Page Reference:

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

Apache Kafka Documentation: Topic Deletion

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

In ksqlDB, INSERT VALUES is used to produce data directly into a topic that underlies a STREAM or TABLE. It is a DML command that appends new records into a Kafka topic.

From ksqlDB documentation:

“INSERT VALUES adds data into a stream or table. This data is persisted in the Kafka topic backing the stream or table.”

Option analysis:

A/B → SELECT queries retrieve data but do not write.

D → Defines a table, does not write data.

C → Correct: Actually writes (produces) data to Kafka.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 7, p. 227–229

Confluent Docs: ksqlDB INSERT INTO and INSERT VALUES Statements

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

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

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

The consumer property auto.offset.reset applies only when no committed offset exists or the committed offset is invalid (e.g., below the log start offset).

However, if an offset is within the valid log range (even if the actual message was removed due to compaction), it is considered valid, and auto.offset.reset is not used.

From Kafka documentation:

“If the consumer’s committed offset is still within the range of the log, even if the message was compacted away, it will be respected.”

Explanation of options:

A, B, C → All scenarios where auto.offset.reset would apply.

D → Correct: Offset is valid even though the message is gone.

Page Reference:

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

Apache Kafka Documentation: Consumer Configs – auto.offset.reset

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