QuizzesDead Letter Topic (DLT) — Concept Check
intermediate
kafka

Dead Letter Topic (DLT) — Concept Check

Questions on Dead Letter Topic (DLT). Failed records after exhausting retries are forwarded to a DLT (topic-name.DLT); a separate listener monitors the DLT for alerting, inspection, or replaying.

8 minutes 8 questions Pass at 70%
Time Limit
8 minutes - timer starts when you begin
Change Answers Freely
Revisit and change any answer before submitting
Full Review After Submit
Correct answers and explanations shown for every question
Auto-submit on timeout
Quiz submits automatically when time runs out

Questions in this quiz

8 questions on Dead Letter Topic (DLT) — Concept Check. Work through them here, then start the quiz to answer them and see your score.

  1. 1.A payment processing service using Spring Kafka has exhausted retries for a record. What happens next?

    • AThe record is sent back to the original topic for another attempt.
    • BThe record is retried indefinitely until successful.
    • CThe record is forwarded to a Dead Letter Topic (DLT) for inspection.
    • DThe record is permanently discarded without any notification.
  2. 2.A developer notices increasing depth in the payments.DLT topic. What does this indicate?

    • AThe application is not consuming messages from the original topic.
    • BMessages are being processed faster than they are produced.
    • CThe Kafka broker is misconfigured, causing message loss.
    • DThere are unresolved issues causing permanent message failures.
  3. 3.In a Spring Kafka setup, what is the role of the @RetryableTopic annotation?

    • AIt logs failed messages without any retries.
    • BIt configures the Kafka broker to handle retries automatically.
    • CIt prevents messages from being retried after failure.
    • DIt automatically creates retry topics and a DLT for failed messages.
  4. 4.A developer configures a DefaultErrorHandler but notices exceptions are not routed to the DLT. What could be the issue?

    • AThe back-off intervals are too short, causing premature retries.
    • BThe exceptions are not added to the not-retryable list.
    • CThe DLT topic is not created automatically by Kafka.
    • DThe Kafka broker is down, preventing DLT routing.
  5. 5.Why is monitoring the depth of a DLT important in a Kafka-based system?

    • AIt allows the application to retry messages indefinitely.
    • BIt helps in identifying persistent processing issues.
    • CIt ensures messages are processed in order.
    • DIt prevents the Kafka broker from crashing.
  6. 6.A developer believes that Kafka automatically handles retries and DLT routing like RabbitMQ. What is the reality?

    • AKafka does not support DLTs or retries at all.
    • BKafka relies on external tools to manage DLTs.
    • CKafka requires the application to manage retries and DLT routing.
    • DKafka handles retries and DLT routing automatically like RabbitMQ.
  7. 7.What happens when a record lands in payments.DLT in a Spring Kafka application?

    • AIt triggers a DLT handler for alerting or reprocessing.
    • BIt is deleted from the Kafka topic immediately.
    • CIt is sent back to the original topic for reprocessing.
    • DIt is automatically retried by the Kafka broker.
  8. 8.A developer configures retries with a FixedBackOff of 1s, 2s, and 4s. What is the total retry duration before reaching the DLT?

    • A3 seconds
    • B6 seconds
    • C7 seconds
    • D8 seconds