A sudden open-enrollment spike exhausts account concurrency and starves an unrelated payroll Lambda in the same account. How should critical capacity be protected?
Select an answer to reveal the explanation.
Short Explanation
Reserve a quiet lane for payroll so the open-enrollment parade can't block the city's paychecks. Reserved concurrency fences critical functions (and can cap noisy ones). Deleting payroll, sharing one uncapped pool, or tweaking timeout won't protect account concurrency.
Full Explanation
Reserved concurrency guarantees a function can obtain execution slots up to that reservation and removes those slots from the unreserved account pool, protecting critical workloads from noisy neighbors. Deleting the critical function, leaving both uncapped, or changing timeout does not solve account-level concurrency exhaustion.