Practise the standard verbs for consuming MongoDB change streams reliably.
0 / 5 completed
1 / 5
Fill in: 'We ___ a change stream on the orders collection so downstream services react to writes in near real time.'
We 'open a stream' — the standard, established MongoDB collocation for starting a change stream cursor. The other options aren't the recognised term here.
2 / 5
Fill in: 'Not persisting the resume token can ___ a restarted consumer missing every change event that happened while it was down.'
We say a missing resume token will 'leave' events missed — the standard, natural collocation for the resulting gap. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the resume token after every processed event so a crashed consumer can restart exactly where it left off.'
We 'persist a token' — the standard, established collocation for durably storing a stream position. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ change events by operation type so an insert, update and delete each trigger their own dedicated handler.'
We 'filter events' — the standard, simple collocation for selecting a subset of a stream by criteria. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ consumer lag on the change stream so a slow downstream handler is caught before the oplog window rolls past it.'
We 'monitor' lag — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.