DVA-C02 · Question #255
A company recently deployed an AWS Lambda function. A developer notices an increase in the function throttle metrics in Amazon CloudWatch. What are the MOST operationally efficient solutions to…
The correct answer is C. Increase the function's reserved concurrency. E. Request a service quota change for increased concurrency. Lambda throttling occurs when concurrent executions exceed the account or function limit; increasing reserved concurrency and requesting a quota increase are the two most direct operational solutions.
Question
A company recently deployed an AWS Lambda function. A developer notices an increase in the function throttle metrics in Amazon CloudWatch. What are the MOST operationally efficient solutions to reduce the function throttling? (Choose two.)
Options
- AMigrate the function to Amazon Elastic Kubernetes Service (Amazon EKS).
- BIncrease the maximum age of events in Lambda.
- CIncrease the function's reserved concurrency.
- DAdd the lambda:GetFunctionConcurrency action to the execution role.
- ERequest a service quota change for increased concurrency.
How the community answered
(35 responses)- A6% (2)
- B3% (1)
- C83% (29)
- D9% (3)
Why each option
Lambda throttling occurs when concurrent executions exceed the account or function limit; increasing reserved concurrency and requesting a quota increase are the two most direct operational solutions.
Migrating to EKS changes the compute platform entirely and does not resolve Lambda concurrency throttling.
The maximum age of events controls how long Lambda retains unprocessed events in the queue before discarding them; it does not affect concurrency or throttling rates.
Increasing a function's reserved concurrency allocates a dedicated pool of concurrent executions for that function, preventing it from being starved by other functions and directly reducing throttling for that specific function.
The `lambda:GetFunctionConcurrency` IAM action is a read permission to view concurrency settings; it does not increase available concurrency or reduce throttling.
Requesting a service quota increase raises the account-level concurrent executions limit (default 1,000 per region), which expands the total concurrency available to all functions and directly addresses account-wide throttling.
Concept tested: Lambda concurrency limits and throttling remediation
Source: https://docs.aws.amazon.com/lambda/latest/dg/configuration-concurrency.html
Community Discussion
No community discussion yet for this question.