A city newsletter Lambda is invoked asynchronously to send bulk alerts. After Lambda exhausts its async retries, failed deliveries must land somewhere the ops team can inspect and replay later. What should the developer configure?
Select an answer to reveal the explanation.
Short Explanation
Think of the DLQ as a lost-and-found bin for async Lambda calls that still fail after AWS retries. Parking those payloads in SQS or SNS lets staff inspect and replay instead of hoping the log stream is enough. Timeout tweaks and tracing help elsewhere—they do not replace failure capture.
Full Explanation
For asynchronous Lambda invocations, AWS retries failed attempts according to the async retry policy. Configuring a dead-letter queue (Amazon SQS or Amazon SNS) on the function captures events that still fail after those retries so operators can analyze and redrive them. Raising timeout, adding X-Ray, or wrapping every path in Step Functions does not provide the same post-retry failure capture for async invoke.