A parks department runs event-driven image moderation on AWS Lambda and must meet a latency SLO. CPU for Lambda scales with memory. What should the architect do?
Select an answer to reveal the explanation.
Short Explanation
Lambda’s CPU rides along with memory—like giving the worker both a bigger desk and a faster brain. Bumping memory (and thus CPU) is how you trim moderation latency to hit the SLO. Starving memory, parking on a tiny always-on box, or killing concurrency works against performance.
Full Explanation
AWS Lambda allocates CPU power proportional to configured memory. For latency-sensitive event-driven image moderation, increasing memory can reduce duration by providing more CPU, helping meet SLOs. Minimal memory settings, undersized single EC2 replacements, or disabling concurrency optimize neither throughput nor latency for bursty civic moderation pipelines.