Master moving data in and out of Kafka with Kafka Connect.
0 / 5 completed
1 / 5
At standup, a dev wants to ingest data from a database into Kafka without custom code. Which connector type fits?
A source connector pulls data from an external system into Kafka topics. Its counterpart, a sink connector, writes from Kafka out to an external system. Connect provides these so you avoid bespoke producer/consumer code.
2 / 5
During a design review, the team writes Kafka data into Elasticsearch. Which connector type is this?
A sink connector reads from Kafka topics and writes to an external datastore like Elasticsearch. It is the mirror of a source connector. Sinks handle delivery and offset commit for you.
3 / 5
In a code review, a dev needs to rename a field per-record in the pipeline. Which Connect feature fits?
A Single Message Transform (SMT) applies lightweight per-record transformations like renaming or masking fields inside Connect. They run inline without a separate stream processor. SMTs are configured in the connector config.
4 / 5
During a PR review, a dev sets how records are serialized to/from bytes. Which Connect component controls this?
Converters translate between Connect's internal data and the byte format on the topic, such as JSON, Avro, or Protobuf. They are configured for keys and values independently. Choosing the right converter ensures schema compatibility.
5 / 5
An incident report shows a restarted source connector reprocessed old data. Which mechanism should have prevented this, and how is the connector managed?
Kafka Connect uses offset management to record a source connector's position so restarts resume correctly. Connectors are created and managed through the Connect REST API. Reprocessing usually means offsets weren't committed or were reset.