A developer is configuring a serverless application where an AWS Lambda function processes… — AWS Certified Developer - Associate

A developer is configuring a serverless application where an AWS Lambda function processes messages from an Amazon SQS queue. The function performs CPU-intensive video transcoding that takes up to $3$ minutes to complete per message. During initial testing, the Lambda function's timeout is set to the default of $15$ seconds, resulting in execution timeouts. Additionally, the developer needs to prevent messages from being received and processed multiple times by other concurrent Lambda invocations while a message is currently being processed. Which configuration changes will resolve the execution timeouts and prevent duplicate message processing?

Configure the Lambda function's timeout to $180$ seconds, and set the Amazon SQS queue's visibility timeout to at least $1080$ seconds.Answer
B
Configure the Lambda function's timeout to $180$ seconds, and set the Amazon SQS queue's visibility timeout to $30$ seconds.
C
Configure the Lambda function's timeout to $15$ seconds, and set the Amazon SQS queue's visibility timeout to $90$ seconds.
D
Configure the Lambda function's timeout to $1080$ seconds, and set the Amazon SQS queue's visibility timeout to $180$ seconds.

Answer

Configure the Lambda function's timeout to

180

seconds, and set the Amazon SQS queue's visibility timeout to at least

1080

seconds.

The correct configuration is to set the Lambda function's timeout to

180

seconds (to accommodate the

3

-minute processing time) and the SQS visibility timeout to at least

1080

seconds. According to AWS best practices, the visibility timeout of an SQS queue triggering a Lambda function should be configured to at least

6

times the Lambda function's timeout to prevent message processing loops and duplication due to throttling or retries.

Step-by-Step Solution

Analyze the processing time requirement of the backend task.

The video transcoding task requires up to

3

minutes (

180

seconds) to complete. The Lambda function's timeout must be set to at least

180

seconds to prevent execution failures.

If the Lambda function's timeout is shorter than the task execution time, the environment terminates the execution before completion, causing the task to fail.

Determine the required SQS queue visibility timeout configuration.

The visibility timeout of the SQS queue must be set to at least

6

times the timeout of the Lambda function, which is

6 \times 180

seconds =

1080

seconds.

AWS recommends setting the SQS visibility timeout to at least

6

times the Lambda function timeout. This provides a safety margin so that if a Lambda function is throttled or fails, the message does not immediately become visible to other consumers before the current invocation finishes or retries.

Key Concept

AWS Lambda integration with Amazon SQS and visibility timeout configuration guidelines

Estimated Time:2m 0s

Question

Answer

Step-by-Step Solution

Key Concept

Common Mistakes

Topics

More questions from this topic