Kubernetes Pod Disruption Budget Language Collocations
Practise the standard verbs for configuring Kubernetes pod disruption budgets.
0 / 5 completed
1 / 5
Fill in: 'We ___ a PodDisruptionBudget on every stateful workload so a voluntary node drain can't take down every replica of a service at once.'
We 'define a budget' — the standard, established Kubernetes collocation for declaring a disruption limit on a workload. The other options aren't the recognised term here.
2 / 5
Fill in: 'Running a service without a disruption budget can ___ a routine cluster upgrade evicting all its replicas simultaneously.'
We say no budget will 'leave' a service fully evicted at once — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ minAvailable to match the workload's real quorum requirement, not just an arbitrary number that happens to sound safe.'
We 'set' a field — the standard, simple collocation for configuring a specific budget parameter. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the disruption budget during a planned node drain so the eviction API waits rather than forcing pods out regardless of the limit.'
We 'respect a budget' — the standard, established collocation for the eviction process honouring a configured disruption limit. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ a disruption budget in staging with a simulated drain before relying on it to protect a production quorum-sensitive service.'
We 'test' a budget — the standard, simple collocation for validating its behaviour before trusting it in production. The other options are less idiomatic here.