Kubernetes CronJob Scheduling Language Collocations
Practise the standard verbs for scheduling Kubernetes CronJobs reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a CronJob with an explicit concurrency policy, rather than letting overlapping runs pile up on a slow cluster.'
We 'define a CronJob' — the standard, simple collocation for configuring a scheduled job. The other options are less idiomatic here.
2 / 5
Fill in: 'Setting startingDeadlineSeconds too low can ___ a legitimately delayed job skipped instead of actually run.'
We say a tight deadline will 'leave' a delayed job skipped — the standard, natural collocation for the resulting miss. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the schedule expression against the cluster's actual timezone, rather than assuming UTC when nobody's actually confirmed it.'
We 'verify a schedule' — the standard, simple collocation for confirming a cron expression against timezone. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every failed CronJob run against pod logs immediately, rather than a silent failure nobody actually notices for days.'
We 'check a run' — the standard, simple collocation for investigating a failed scheduled job. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ completed job history limits sensibly, rather than letting thousands of finished pods clutter the cluster indefinitely.'
We 'set limits' — the standard, simple collocation for capping retained job history. The other options aren't idiomatic here.