Practise the standard verbs for handling replication lag safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ replica lag continuously so stale reads never surprise a downstream service.'
We 'monitor' lag — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.
2 / 5
Fill in: 'A long-running transaction on the primary can ___ replication lag on every follower at once.'
We say a long transaction will 'increase' lag — the standard, simple collocation for the resulting slowdown. The other options are less idiomatic here.
3 / 5
Fill in: 'We ___ read-after-write requests to the primary so a user never sees their own stale data.'
We 'route' requests — the standard collocation for directing traffic to a specific node. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ a replica from the pool automatically once its lag crosses a hard limit.'
We 'remove' a replica — the standard collocation for taking a lagging node out of rotation. The other options aren't idiomatic here.
5 / 5
Fill in: 'We ___ lag alerts to the on-call channel so a growing gap gets attention early.'
We 'send alerts' — the standard, simple collocation for notifying responders. The other options are less idiomatic here.