CCDAK Exam Dumps : Confluent Certified Developer for Apache Kafka Certification Examination

For Kafka Streams to perform joins, topics must be co-partitioned, meaning:

They have the same number of partitions (A), and

They use the same partitioning strategy (typically by key) (B)

From Kafka Streams Documentation > Joins:

“Co-partitioning is required for Kafka Streams joins. Topics must have the same number of partitions and use the same key-based partitioner.”

Value schema (C) and retention time (D) have no bearing on join compatibility.

The default maximum message size that a Kafka broker accepts is 1MB (1,048,576 bytes), controlled by the config property message.max.bytes.

From Kafka Broker Configuration Docs:

“The default maximum message size is 1MB. To accept larger messages, configure message.max.bytes and the producer’s max.request.size.”

Producers also have a matching limit via max.request.size, and consumers via fetch.message.max.bytes.

Kafka Connect can run in standalone mode or distributed mode. For simple tasks like reading logs from a file on a single host, standalone mode is recommended.

From Kafka Connect User Guide:

“Standalone mode is useful when running connectors on a single machine (e.g., for development or simple deployments like log collection from a local file).”

Distributed mode is preferred for scalability and fault tolerance but overkill for this use case.