1 / 5
Fill in: 'We ___ a cron expression carefully so a job doesn't silently run twice an hour by mistake.'
-
-
-
-
We 'write an expression' — the standard, simple collocation for authoring a schedule. The other options are less idiomatic here.
2 / 5
Fill in: 'Overlapping runs can ___ two instances of the same job fighting over the same resource.'
-
-
-
-
We say overlap will 'create' contention — the standard, simple collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a lock so a slow-running job can't start a second instance before the first finishes.'
-
-
-
-
We 'use a lock' — the standard, simple collocation for adopting a mutual-exclusion mechanism. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ every scheduled job to a dashboard so a silently skipped run gets noticed quickly.'
-
-
-
-
We 'report' a job — the standard collocation for surfacing its execution status. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ all cron schedules in one place instead of scattering them across unrelated services.'
-
-
-
-
We 'centralise' schedules — the standard collocation for consolidating configuration. The other options aren't idiomatic here.