AWS Certified Developer - Associate
Get started today
Ultimate access to all questions.
The development team at an IT company has set up an Application Load Balancer (ALB) to route requests to a Lambda function named A. However, they have noticed that Lambda function A is not processing any of the requests sent by the ALB. Upon investigating the issue, they discovered that another Lambda function, named B, operating within the same AWS account is surpassing the concurrency limits set for their Lambda functions.
What steps can the development team take to resolve this problem?
The development team at an IT company has set up an Application Load Balancer (ALB) to route requests to a Lambda function named A. However, they have noticed that Lambda function A is not processing any of the requests sent by the ALB. Upon investigating the issue, they discovered that another Lambda function, named B, operating within the same AWS account is surpassing the concurrency limits set for their Lambda functions.
What steps can the development team take to resolve this problem?
Explanation:
Overall explanation Correct option:
Set up reserved concurrency for the Lambda function B so that it throttles if it goes above a certain concurrency limit
Concurrency is the number of requests that a Lambda function is serving at any given time. If a Lambda function is invoked again while a request is still being processed, another instance is allocated, which increases the function's concurrency.
To ensure that a function can always reach a certain level of concurrency, you can configure the function with reserved concurrency. When a function has reserved concurrency, no other function can use that concurrency. More importantly, reserved concurrency also limits the maximum concurrency for the function, and applies to the function as a whole, including versions and aliases.