Practise the standard verbs for tuning Cloud Run concurrency correctly.
0 / 5 completed
1 / 5
Fill in: 'We ___ a per-instance concurrency limit based on load testing, rather than a default that fits no actual workload's real profile.'
We 'set a limit' — the standard, simple collocation for configuring Cloud Run concurrency. The other options are less idiomatic here.
2 / 5
Fill in: 'Setting concurrency too high on a CPU-bound service can ___ requests queued behind work an instance can't actually finish.'
We say an overly high setting will 'leave' requests queued — the standard, natural collocation for the resulting backlog. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ minimum instance counts explicitly for latency-sensitive services, rather than accepting cold starts nobody's actually measured.'
We 'configure counts' — the standard, simple collocation for setting minimum warm instances. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ concurrency settings against real load tests before rollout, rather than shipping a guess nobody's actually validated.'
We 'test settings' — the standard, simple collocation for validating concurrency under real load. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ instance CPU and request latency together, rather than tuning concurrency without actually seeing the resulting tradeoff.'
We 'monitor metrics' — the standard, simple collocation for watching CPU and latency together. The other options aren't idiomatic here.