Confluent CCDAK Dumps Questions Answers

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.

To ensureexactly-once deliveryand avoid duplicates even during retries:

enable.idempotence=trueensures deduplication on the broker

retries=2147483647allows unlimited retries on retriable errors

max.in.flight.requests.per.connection=5is themaximum value that preserves message order with idempotence

FromKafka Producer Config Docs:

“To achieve exactly-once semantics, set enable.idempotence=true, and max.in.flight.requests.per.connection ≤ 5.”

A is unrelated (consumer-side)

C disables retries

D disables idempotence, leading to duplicates

For proper delivery handling with acks=all:

Usecallbackto log or act on success/failure.

Usetry/catchto handle synchronous exceptions like serialization errors or network failures.

FromKafka Producer Documentation:

“Errors can be caught either via the returned Future or via the callback interface. For fatal errors, use a try/catch block around the send call.”

Option B is incorrect because send() returns a Future, not RecordMetadata directly.

Option D is invalid — ProducerRecord has no method called status().