A solutions architect has an application container, an AWS Lambda function, and an Amazon Simple Queue Service (Amazon SQS) queue. The Lambda function uses the SQS queue as an event source. The…

Question

Options

• AConfigure the Lambda function with a larger amount of memory.
• BConfigure an increase in the Lambda function's timeout value.
• CConfigure the SQS queue's delivery delay value to be greater than the maximum time it takes to
• DConfigure the SQS queue's visibility timeout value to be greater than the maximum time it takes to

• A
  3% (1)
• B
  9% (3)
• C
  3% (1)
• D
  86% (30)

Explanation

When using an SQS queue as an event source for AWS Lambda, the visibility timeout of the SQS queue plays a critical role in preventing duplicate message processing. "If your Lambda function doesn't process the message and delete it from the queue within the visibility timeout period, the message becomes visible again and can be processed again by the same or another function instance." In this scenario, the third-party API may take up to 60 seconds to respond. Since the Lambda function is configured with a 65-second timeout, the visibility timeout of the queue must be greater than or equal to the maximum function execution time to avoid the same message being Incorrect Options: A: Memory allocation doesn't impact duplicate message handling. B: Timeout is already sufficient; increasing it further does not solve the core issue. C: Delivery delay controls initial delivery delay, not reprocessing logic.

No community discussion yet for this question.