After maximum receives, unprocessable code-violation payloads must not block the main SQS backlog forever. What should the team configure?
Select an answer to reveal the explanation.
Short Explanation
Poison letters belong in a side bin, not forever at the front of the citizen complaint line. A dead-letter queue peels off messages that hit max receives so the main backlog keeps moving. Infinite retries, deleting before validation, or hoping FIFO dedupe alone won't quarantine bad payloads.
Full Explanation
Configuring a dead-letter queue with a maxReceiveCount moves repeatedly failing messages off the primary queue for inspection without blocking healthy traffic. Infinite retries keep poison messages in circulation. Deleting before validation risks silent data loss. FIFO deduplication addresses duplicate producers, not quarantine of unprocessable payloads.