Kafka - Event-Driven Architecture
You want to implement a Dead Letter Queue pattern in Kafka that retries failed messages up to 3 times before sending them to the DLQ. Which approach correctly achieves this?
You want to implement a Dead Letter Queue pattern in Kafka that retries failed messages up to 3 times before sending them to the DLQ. Which approach correctly achieves this?
hard📝 Application Q15 of 15
Step-by-Step Solution
Solution:
Step 1: Understand retry logic with DLQ
Retries require tracking how many times a message was processed; using headers to count retries is common.Step 2: Implement conditional retry or DLQ send
If retry count is less than 3, retry processing; if 3 or more, send message to DLQ topic.Step 3: Evaluate other options
Kafka broker does not handle retries automatically; immediate DLQ send skips retries; deleting messages after retries is incorrect.Final Answer:
Use a retry counter in message headers; on failure increment and retry, else send to DLQ after 3 tries -> Option AQuick Check:
Retry count in headers controls DLQ after 3 tries [OK]
Quick Trick: Track retries in headers; send to DLQ after max retries [OK]
Common Mistakes:
- Expecting Kafka broker to retry automatically
- Sending all failures immediately to DLQ
- Deleting messages instead of sending to DLQ
Master "Event-Driven Architecture" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes