[Solved] What is wrong with this Kafka Connect DLQ configuration snippet?errors.deadletterqueue.topic.name=dlq-topic errors.deadletterqueue.context.headers.enable=false errors.tolerance=none | Kafka

Kafka - Event-Driven Architecture

What is wrong with this Kafka Connect DLQ configuration snippet?

errors.deadletterqueue.topic.name=dlq-topic
errors.deadletterqueue.context.headers.enable=false
errors.tolerance=none

Aerrors.tolerance=none will stop processing on errors, so DLQ is unused.

Berrors.deadletterqueue.context.headers.enable must be true for DLQ to work.

CDLQ topic name cannot contain hyphens.

Derrors.deadletterqueue.topic.name must be empty to enable DLQ.

Step-by-Step Solution

Solution:

Step 1: Understand errors.tolerance=none effect
This setting causes the connector to stop on the first error, so DLQ is never used.
Step 2: Confirm other settings are valid
DLQ topic name and context headers setting are valid and do not prevent DLQ usage if tolerance allowed errors.
Final Answer:
errors.tolerance=none will stop processing on errors, so DLQ is unused. -> Option A
Quick Check:
errors.tolerance=none disables DLQ usage [OK]

Quick Trick: errors.tolerance must allow errors for DLQ to work [OK]

Common Mistakes:

Master "Event-Driven Architecture" in Kafka

9 interactive learning modes - each teaches the same concept differently

More Kafka Quizzes

What is wrong with this Kafka Connect DLQ configuration snippet?