Practise the standard verbs for handling Redis Sentinel failover reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ three Sentinel nodes across separate hosts so a single host failure can't cost us the whole quorum.'
We 'deploy nodes' — the standard, established Redis Sentinel collocation for provisioning monitoring instances. The other options aren't the recognised term here.
2 / 5
Fill in: 'Running Sentinel with too few nodes can ___ a single network partition triggering a false failover.'
We say too few nodes will 'leave' the system open to a false failover — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a new primary automatically once quorum agrees the old primary is genuinely unreachable, not just slow.'
We 'promote a primary' — the standard, established Redis collocation for elevating a replica after failover. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ client connections to reconnect to the new primary via Sentinel's published address rather than a hard-coded host.'
We 'configure' connections — the standard collocation for setting up client discovery behaviour. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ a failover drill in staging regularly so we know Sentinel actually promotes cleanly before a real outage forces it.'
We 'run a drill' — the standard, simple collocation for executing a practice exercise. The other options are less idiomatic here.