DVA-C02 · Question #36
An ecommerce company is using an AWS Lambda function behind Amazon API Gateway as its application tier. To process orders during checkout, the application calls a POST API from the frontend. The…
The correct answer is B. Create and inspect the Lambda dead-letter queue. Troubleshoot the failed functions. Reprocess. https://docs.aws.amazon.com/lambda/latest/dg/invocation-retries.html Asynchronous invocation - Lambda retries function errors twice. If the function doesn't have enough capacity to handle all incoming requests, events might wait in the queue for hours or days to be sent to the…
Question
An ecommerce company is using an AWS Lambda function behind Amazon API Gateway as its application tier. To process orders during checkout, the application calls a POST API from the frontend. The POST API invokes the Lambda function asynchronously. In rare situations, the application has not processed orders. The Lambda application logs show no errors or failures. What should a developer do to solve this problem?
Options
- AInspect the frontend logs for API failures. Call the POST API manually by using the requests from
- BCreate and inspect the Lambda dead-letter queue. Troubleshoot the failed functions. Reprocess
- CInspect the Lambda logs in Amazon CloudWatch for possible errors. Fix the errors.
- DMake sure that caching is disabled for the POST API in API Gateway.
How the community answered
(29 responses)- A7% (2)
- B59% (17)
- C10% (3)
- D24% (7)
Explanation
https://docs.aws.amazon.com/lambda/latest/dg/invocation-retries.html Asynchronous invocation - Lambda retries function errors twice. If the function doesn't have enough capacity to handle all incoming requests, events might wait in the queue for hours or days to be sent to the function. You can configure a dead-letter queue on the function to capture events that weren't successfully processed.
Community Discussion
No community discussion yet for this question.