Kubernetes Horizontal Pod Autoscaler Language Collocations
Practise the standard verbs for configuring the Kubernetes Horizontal Pod Autoscaler.
0 / 5 completed
1 / 5
Fill in: 'We ___ a target CPU utilization on the HPA so replica count grows before requests actually start queueing up.'
We 'set a target' — the standard, established Kubernetes HPA collocation for configuring the scaling threshold. The other options aren't the recognised term here.
2 / 5
Fill in: 'Missing resource requests on a deployment can ___ the HPA unable to compute utilization and never scale at all.'
We say missing requests will 'leave' the HPA unable to act — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a stabilization window on scale-down so a brief traffic dip doesn't immediately shed pods we'll need again in minutes.'
We 'configure' a window — the standard collocation for setting up a scaling behaviour parameter. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ current replica counts against the HPA's target metric closely after a deploy to confirm it's actually reacting.'
We 'compare' counts — the standard, simple collocation for contrasting actual values against a target. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a maximum replica count on the HPA so a runaway metric can't scale the deployment into an unbounded, costly sprawl.'
We 'cap' a count — the standard, established collocation for placing an upper bound on autoscaling. The other options aren't the recognised term here.