Practise the standard verbs for configuring Kubernetes resource limits.
0 / 5 completed
1 / 5
Fill in: 'We ___ CPU and memory requests on every pod so the scheduler can place workloads onto nodes accurately.'
We 'set requests' — the standard, established Kubernetes collocation for declaring a pod's resource needs. The other options aren't the recognised term here.
2 / 5
Fill in: 'Leaving memory limits unset can ___ a single leaking pod consuming an entire node and evicting its neighbours.'
We say missing limits will 'allow' a pod to consume everything — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a pod that exceeds its memory limit so it never drags down every other workload sharing the node.'
We 'kill a pod' — the standard, established Kubernetes collocation (OOMKilled) for terminating an over-limit process. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ actual usage against configured requests regularly so limits get tuned instead of guessed once and forgotten.'
We 'compare usage' — the standard, simple collocation for contrasting real values against configured ones. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a LimitRange at the namespace level so every new pod gets a sane default even without an explicit request.'
We 'define a range' — the standard, established Kubernetes collocation for declaring a namespace-wide default policy. The other options aren't the recognised term here.