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

According to the official Apache Kafka Connect documentation, RegexRouter is the SMT specifically designed to dynamically change the destination topic name of records produced by a connector. It works by applying a regular expression to the original topic name and rewriting it to a new topic name.

This makes RegexRouter the correct choice when some records must be routed to a different topic, typically in combination with connector-level logic, predicates, or multiple connectors. It is commonly used for topic renaming, topic versioning, or routing records to alternate topics.

InsertField (Option B) only adds metadata fields (such as topic, partition, or timestamp) to the record payload and does not affect routing. TombstoneHandler (Option C) is used to manage null-value records, especially with compacted topics. HeaderFrom (Option D) copies fields into headers but does not change the target topic.

Therefore, RegexRouter is the only SMT that directly supports changing the output topic, as documented in the Kafka Connect SMT reference.

=========================

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.

To skip a corrupted record and avoid failing the application, you must seek past the failed offset manually using consumer.seek(). This allows the application to resume consumption from the next offset.

From Kafka Consumer Error Handling Docs:

“On deserialization failure, you can catch RecordDeserializationException, log the error, and call seek() to the next offset to skip the bad record.”

A does not prevent re-processing the bad record.

C is invalid; there's no skip() method in the Kafka consumer API.

D results in service interruption — not ideal for resiliency.