Producers can set acks=1 to get acknowledgement from partition leader only.

To isolate logs for a specific connector, you can configurea separate logger and appenderin theConnect worker's log4j.propertiesfile, using the connector's name as the logging context.
FromKafka Connect Logging Docs:
"Kafka Connect loggers use hierarchical logger names. You can configure per-connector log levels and output files by extending log4j.properties."
* A and C change verbosity but don't separate logs.
* D is false; targeted logging is possible.
Reference:Kafka Connect > Logging and Debugging

To skip a corrupted record and avoid failing the application, you mustseek past the failed offsetmanually using consumer.seek(). This allows the application to resume consumption from the next offset.
FromKafka 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'sno skip() methodin the Kafka consumer API.
* D results in service interruption - not ideal for resiliency.
Reference:Kafka Consumer API - Exception Handling and seek()

Keys are necessary if you require strong ordering or grouping for messages that share the same key. If you require that messages with the same key are always seen in the correct order, attaching a key to messages will ensure messages with the same key always go to the same partition in a topic. Kafka guarantees order within a partition, but not across partitions in a topic, so alternatively not providing a key - which will result in round-robin distribution across partitions - will not maintain such order.

assign() can be used for manual assignment of a partition to a consumer, in which case subscribe() must not be used. Assign() takes a collection of TopicPartition object as an argument https://kafka.apache.org/23
/javadoc/org/apache/kafka/clients/consumer/KafkaConsumer.html#assign-java.util.Collection-