nerdexam
Amazon

DVA-C02 · Question #324

A developer is building an application that invokes AWS Lambda functions asynchronously to process events. The developer notices that a Lambda function fails to process some events at random times. Th

The correct answer is B. Configure the Lambda function with a dead-letter queue based in Amazon Kinesis. Update the. There appears to be an error in the provided answer key - option B as written (Kinesis as a dead-letter queue) is incorrect per AWS documentation. Lambda's DLQ feature only supports Amazon SQS and Amazon SNS as destinations; Kinesis cannot be configured as a Lambda DLQ. The corre

Submitted by fatima_kr· Mar 5, 2026Development with AWS Services

Question

A developer is building an application that invokes AWS Lambda functions asynchronously to process events. The developer notices that a Lambda function fails to process some events at random times. The developer needs to investigate the failed events and capture the events that the Lambda function fails to process. Which solution will meet these requirements?

Options

  • AAdd an Amazon EventBridge rule for the Lambda function. Configure the EventBridge rule to
  • BConfigure the Lambda function with a dead-letter queue based in Amazon Kinesis. Update the
  • CConfigure the Lambda function with an Amazon Simple Queue Service (Amazon SQS) dead-
  • DConfigure the Lambda function with an Amazon Simple Queue Service (Amazon SQS) FIFO

How the community answered

(38 responses)
  • A
    8% (3)
  • B
    71% (27)
  • C
    5% (2)
  • D
    16% (6)

Explanation

There appears to be an error in the provided answer key - option B as written (Kinesis as a dead-letter queue) is incorrect per AWS documentation. Lambda's DLQ feature only supports Amazon SQS and Amazon SNS as destinations; Kinesis cannot be configured as a Lambda DLQ.

The correct answer is C - configuring the Lambda function with an SQS dead-letter queue (DLQ). When an async Lambda invocation fails after retries (default: 2 attempts), the failed event payload is automatically routed to the configured SQS DLQ, preserving it for investigation and reprocessing.

Why the others are wrong:

  • A (EventBridge rule): EventBridge can trigger Lambda but cannot natively capture and preserve payloads of failed Lambda invocations for debugging.
  • B (Kinesis DLQ): Kinesis is not a supported DLQ destination for Lambda - this option is invalid.
  • D (SQS FIFO queue): FIFO queues enforce ordering and deduplication, which are unnecessary requirements here. Standard SQS queues are the correct DLQ type.

Memory tip: Think "Dead Letters go to the Post Office (SQS/SNS)" - failed async Lambda events need a holding place (SQS) where you can pick them up later, just like undeliverable mail at a post office. Kinesis is a streaming service, not a message holding destination.

Double-check the source of this practice question - the answer key may have a typo (B vs. C).

Topics

#Lambda Asynchronous Invocation#Dead-Letter Queues (DLQ)#Error Handling#Event Processing

Community Discussion

No community discussion yet for this question.

Full DVA-C02 Practice