AWS Lambda Provisioned Concurrency Language Collocations
Practise the standard verbs for managing AWS Lambda provisioned concurrency.
0 / 5 completed
1 / 5
Fill in: 'We ___ provisioned concurrency on a latency-sensitive function so it never pays a cold-start penalty during peak traffic.'
We 'enable' provisioned concurrency — the standard, established Lambda collocation for keeping execution environments warm ahead of demand. The other options aren't the recognised term here.
2 / 5
Fill in: 'Relying on default on-demand concurrency for a spiky, latency-critical function can ___ p99 latency dominated by cold starts.'
We say relying on defaults will 'leave' latency dominated by cold starts — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ provisioned concurrency to match the daily traffic pattern with scheduled scaling, rather than paying for it around the clock.'
We 'scale' provisioned concurrency — the standard, established collocation for adjusting the warm-instance count over time. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ cold-start and warm-start latency separately in CloudWatch so provisioned concurrency's actual impact is easy to prove.'
We 'compare' latency figures — the standard, simple collocation for contrasting two measured values. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the provisioned concurrency cost against the cold-start savings regularly, since always-warm capacity isn't free.'
We 'review' a cost — the standard, simple collocation for periodically reassessing a spend trade-off. The other options are less idiomatic here.