Practise the standard verbs for handling MySQL replication failover.
0 / 5 completed
1 / 5
Fill in: 'We ___ a replica to primary automatically when health checks confirm the original primary is truly unreachable.'
We 'promote a replica' — the standard, established MySQL collocation for elevating a replica to primary role. The other options aren't the recognised term here.
2 / 5
Fill in: 'Promoting a lagging replica too early can ___ recent committed writes lost during the failover.'
We say an early promotion will 'leave' writes lost — the standard, natural collocation for the resulting data loss. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ replication lag continuously so a replica that's falling behind is flagged before it becomes a failover candidate.'
We 'monitor' lag — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ application connections to the new primary via a proxy layer so clients never need to know the actual hostname.'
We 'route connections' — the standard, simple collocation for directing traffic to the correct destination. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ a failover drill quarterly in staging so the runbook actually works when a real primary outage happens.'
We 'run a drill' — the standard, simple collocation for executing a practice exercise. The other options are less idiomatic here.