CCAAK Exam Study Guide: The Ultimate 2026 Practice Test

The Kafka REST Proxy, provided as part of Confluent Platform, allows clients to interact with Kafka over REST APIs. When securing communication between REST Proxy and REST clients, it uses TLS (HTTPS).

As per the official Confluent documentation for REST Proxy security:

“The REST Proxy supports HTTPS to encrypt communication between REST clients and the REST Proxy.”

TLS/SSL encryption ensures that data in transit is secure and private.

Other options listed, such as MD5 (a hashing algorithm), SCRAM (an authentication mechanism), and Kerberos (an authentication protocol), do not provide direct encryption of the communication channel itself for REST Proxy. They can be part of broader security configurations (e.g., SCRAM for Kafka brokers, Kerberos for SASL authentication), but TLS (HTTPS) is the explicit mechanism for encrypting data between the REST Proxy and its clients.

Page Reference:

Confluent Kafka: The Definitive Guide, 1st Edition, Chapter 9 (“Kafka Security”), Section “REST Proxy Security” (p. 288–289).

Confluent Platform REST Proxy Documentation, “Encryption (HTTPS)”.

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

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

Apache Kafka's built-in ACL mechanism (SimpleAclAuthorizer) stores ACL data in ZooKeeper. ACLs are propagated to brokers from ZooKeeper and cached in memory for fast lookup.

From Kafka documentation:

“ACLs are stored in ZooKeeper under /kafka-acl and are loaded into each broker at startup and on updates.”

B → Correct: ZooKeeper stores ACLs centrally.

A → Brokers load ACLs but don’t persist them.

C & D → Do not store or manage ACLs.

Page Reference:

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

Apache Kafka Documentation: Authorizer Configuration