How does "AWS Lambda" handle concurrency limits, and what is the difference between "account-level concurrency" and "reserved concurrency" for a specific function?
Correct! Well done.
Incorrect.
The correct answer is A) Account-level concurrency is the total concurrent executions for all functions in a region (a soft, increasable limit), while reserved concurrency sets a guaranteed min and max for one function, isolating it from being starved but also capping its scaling
Correct Answer
Account-level concurrency is the total concurrent executions for all functions in a region (a soft, increasable limit), while reserved concurrency sets a guaranteed min and max for one function, isolating it from being starved but also capping its scaling
Without reserved concurrency, a function competes for the shared account-level pool of concurrent executions; setting reserved concurrency carves out a dedicated allocation for that function (protecting it from contention) but also caps how far it can scale, even if the account has spare capacity.