A company processes incoming documents from an Amazon S3 bucket. Users upload documents to an S3 bucket using a web user interface. Upon receiving files in S3, an AWS Lambda function is invoked to pro

Question

Options

• ANotification of a failed S3 event is sent as an email through Amazon SNS.
• BThe S3 event is sent to the default Dead Letter Queue.
• CThe S3 event is processed until it is successful.
• DThe S3 event is discarded after the event is retried twice.

• A
  3% (1)
• B
  3% (1)
• C
  7% (2)
• D
  87% (26)

Explanation

Option D is correct because S3 event notifications invoke Lambda asynchronously, and by default, AWS Lambda automatically retries failed asynchronous invocations twice (3 total attempts). Once those retries are exhausted with no success - including timeout exceptions - the event is silently discarded with no further action.

Why the distractors are wrong:

• A - Lambda does not automatically notify via SNS on failure; SNS integration must be explicitly configured as an event destination.
• B - There is no automatic or "default" Dead Letter Queue; a DLQ must be manually configured on the Lambda function or event source mapping.
• C - Lambda does not retry indefinitely; it retries exactly twice by default, then gives up.

Memory tip: Think of the number 2 - Lambda retries async invocations 2 times (for 2 distractors that sound plausible but require explicit setup). No setup = no DLQ, no SNS, no infinite retries - just 2 retries, then gone.

No community discussion yet for this question.