Confluent Updated CCDAK Exam Questions and Answers by mohamad

unclean.leader.election.enable=false→ Prevents data loss by only considering in-sync replicas when rebalancing.

replication.factor→ Specifies how many redundant copies of partitions are distributed across brokers.

min.insync.replicas=2→ Sets the standard for the number of partition instances that must keep up with the latest committed message.

unclean.leader.election.enable=false ensures that onlyin-sync replicascan be elected as leaders. If disabled, an out-of-sync replica may become leader, potentially leading to data loss.

replication.factor defineshow many brokerswill maintain copies of each partition, directly impacting durability and availability.

min.insync.replicas determineshow many replicas must acknowledgea write when acks=all is used, enforcing write durability.

For Kafka Streams to performjoins, topics must beco-partitioned, meaning:

They have thesame number of partitions(A), and

They use thesame partitioning strategy(typically by key) (B)

FromKafka 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.

SMTs (Single Message Transforms) arelightweight transformationsapplied to individual messages as they pass through Kafka Connect.

Chaining SMTs: You can applymultiple SMTsin sequence by defining them in order in the connector config.

Masking or modifying fieldsis acommon use case(e.g., redacting sensitive data).

FromKafka Connect Documentation:

“Single Message Transforms (SMTs) are applied to individual messages. You can chain multiple SMTs together.”

SMTsdo not perform joins(B is incorrect).

Converters and SMTs areseparate concerns(D is incorrect).