A bursty 311 webhook invokes AWS Lambda and occasionally throttles during storm-related spikes. What should the architect do to meet burst concurrency needs?
Select an answer to reveal the explanation.
Short Explanation
Storm day 311 traffic is a flash mob at the door—Lambda needs enough concurrency tickets. Reserved or provisioned concurrency sized for the burst stops throttles. Zeroing concurrency, killing the API, or lowering account limits makes the outage worse.
Full Explanation
Lambda concurrency controls how many invocations run simultaneously. Bursty civic webhooks may require reserved concurrency or provisioned concurrency so spikes do not hit throttling that breaks SLOs. Reducing concurrency, disabling the entry API, or lowering account limits increases throttling risk rather than meeting Task 3.2 performance goals.