A malformed sanitation-route event repeatedly crashes a parser in the main Kafka consumer group. What handling approach keeps the healthy stream moving?
Select an answer to reveal the explanation.
Short Explanation
One rotten apple should not stop the whole truck. Park the bad event on a dead-letter side path, fix it later, and let good sanitation messages keep flowing. That is poison-message hygiene for city buses.
Full Explanation
Poison messages are malformed or repeatedly failing payloads that can stall consumers if left in the main path. Dead-letter or quarantine routing isolates those events for inspection while healthy traffic continues. Freezing the whole topic, only adding partitions, or abandoning the consumer group does not solve schema or payload defects. Civic pipelines need an explicit bad-message strategy as part of ingestion operations awareness.