Confluent CCAAK Exam Dumps

Avro is the original and most commonly used schema format supported by Schema Registry.

Confluent Schema Registry supports JSON Schema for validation and compatibility checks.

Protocol Buffers (Protobuf) are supported for schema management in Schema Registry.

Increasing batch.size allows the producer to accumulate more messages into a single batch, improving compression and reducing the number of requests sent to the broker.

Increasing linger.ms gives the producer more time to fill up batches before sending them, which improves batching efficiency and throughput.

This combination is a best practice for maximizing throughput, especially when message volume is high or consistent latency is not a strict requirement.

Kafka checks permissions in the following sequence:

1. Super Users: If the user is a super user (defined via super.users), access is granted immediately.

2. Allow ACL: If there is a matching Allow ACL, Kafka proceeds to the next step.

3. Deny ACL: If there is a matching Deny ACL, access is denied (even if an Allow exists).

4. Deny: If no matching ACLs are found, access is denied by default.

This order ensures that super users bypass ACLs, denials override allows, and default is deny.

With 9 partitions spread across 3 brokers, each broker typically hosts 3 leaders (assuming even distribution). When Broker 0 fails, the partitions for which it was leader will elect new leaders on brokers 1 or 2 if enough in-sync replicas (ISRs) remain. But since min.insync.replicas=3 and only 2 brokers are up, no partition can meet the minimum in-sync replica requirement, so producers with acks=all will fail to write. However, for partitions where Broker 0 is not the leader, consumers can still read committed messages. Given that only 3 partitions likely had Broker 0 as leader, six partitions remain accessible for reads, but not writes.

In this scenario, the offset itself is still valid, even though the record at that offset was compacted away. The consumer can continue consuming from the next available record. Therefore, auto.offset.reset does NOT apply, because there is a valid offset present.