Practise the standard verbs for configuring PagerDuty escalation policies.
0 / 5 completed
1 / 5
Fill in: 'We ___ an escalation policy with at least two levels so an unacknowledged page automatically reaches a second engineer instead of going unanswered.'
We 'define a policy' — the standard, simple collocation for specifying who gets paged and in what order. The other options are less idiomatic here.
2 / 5
Fill in: 'Configuring an escalation policy with a single level and no fallback can ___ a page going completely unanswered if that one on-call engineer is unreachable.'
We say a single-level policy will 'leave' a page unanswered — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ an unacknowledged critical alert to the next escalation level automatically after a short timeout, rather than letting it wait indefinitely for a response.'
We 'escalate an alert' — the standard, established PagerDuty collocation for automatically advancing an unacknowledged page to the next responder. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ the escalation policy quarterly against the current on-call roster, so a departed engineer's name doesn't sit uselessly at the top of every page.'
We 'review' a policy — the standard, simple collocation for periodically reassessing whether a configuration still matches reality. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a new escalation policy with a simulated page before relying on it during a genuine incident, so a misconfigured level isn't discovered mid-outage.'
We 'test' a policy — the standard, simple collocation for validating its behaviour before trusting it live. The other options are less idiomatic here.