CCAAK Exam Dumps - Confluent Certified Administrator for Apache Kafka

Confluent Schema Registry supports the following schema types for use with Kafka:

Avro

Protobuf

JSON Schema

These schemas are officially supported for subject versioning, compatibility checks, and REST interface integration.

From Confluent documentation:

“The Confluent Schema Registry supports Avro, JSON Schema, and Protobuf formats.”

Incorrect Options:

gRPC is not supported as a schema format.

Thrift is not supported in Schema Registry.

Page Reference:

Confluent Kafka: The Definitive Guide, 1st Edition, Chapter 7, p. 208–210

Confluent Schema Registry Documentation: Overview Section (Schema Types)

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

With min.insync.replicas=3 and acks=all, a partition must have at least 3 in-sync replicas (ISRs) for the producer to succeed. With one broker down (broker 0), only 2 ISRs remain → not enough to meet the requirement. Therefore, producers cannot write to affected partitions.

However, for some partitions where the leader and replicas are on brokers 1 and 2, the full ISR (3) may still be present (if broker 0 was not a replica). In this scenario, exactly 6 of the 9 partitions may still have ISR=3 depending on replica distribution.

From Kafka documentation:

“When acks=all and min.insync.replicas is not met, the broker will reject the produce request with an exception.”

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 5, p. 159–161

Apache Kafka Documentation: Topic Config – min.insync.replicas

By default, Kafka does not enable any security mechanism. This means:

Communication is done over PLAINTEXT (unencrypted).

No authentication is configured.

No authorization is enforced.

From Apache Kafka documentation:

“By default, Kafka has no security. All network communication is done in plaintext, and there is no client authentication or authorization.”

This means that:

Option A is correct.

Option B is incorrect because encryption is not enabled by default.

Option C is incorrect because authentication is not provided unless SASL is configured.

Option D is incorrect as neither encryption nor authentication is enabled by default.

Page Reference:

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

Apache Kafka Documentation: “Security Overview” section

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

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

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

Partitions are Kafka’s core mechanism for scaling and distributing load. Each partition of a topic is distributed across brokers. Producers and consumers interact with specific partitions, and Kafka automatically balances those partitions across available brokers.

From Kafka documentation:

“Partitions allow Kafka to parallelize data and distribute load across brokers and clients.”

A → Correct: Distributes data and load

B → Incorrect: Replicas are for fault tolerance, not load balancing

C → Incorrect: Offsets track read progress, not distribute load

D → Incorrect: Connectors are part of Kafka Connect, not used for client balancing

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 4, p. 132–134

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

Kafka Connect is a framework for connecting Kafka with external systems like databases, key-value stores, file systems, etc. It handles ingestion and egress of data using scalable and fault-tolerant connectors.

From Kafka documentation:

“Kafka Connect is a scalable and fault-tolerant component for efficiently streaming data between Kafka and other systems.”

A → Correct: Purpose-built for data integration.

B → For stream processing, not integration.

C → Manages schemas, not data movement.

D → For HTTP-based Kafka interaction.

Page Reference:

Kafka: The Definitive Guide, 1st Edition, Chapter 8, p. 239–241

Apache Kafka Documentation: Kafka Connect Overview

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

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

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

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

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