A poison record in a Kinesis batch causes the water-quality Lambda to fail the entire batch and stall shard iterator progress. What should the developer apply?
Select an answer to reveal the explanation.
Short Explanation
One bad water-quality blip should not freeze the whole stream like a jammed conveyor. Bisect-on-error (and similar tactics) isolates the poison pill so the shard can keep moving. Deleting the stream is using a sledgehammer on a sticky label.
Full Explanation
For Kinesis (and DynamoDB streams) event sources, Lambda can bisect batches on failure to narrow poison messages while allowing healthy records to proceed, often combined with destinations or DLQ patterns for bad records. Indefinitely hiding errors, deleting the stream, or disabling IteratorAge monitoring worsens operational risk.