Practise the standard verbs for deduplicating with a Redis Bloom filter.
0 / 5 completed
1 / 5
Fill in: 'We ___ each processed message ID to a Bloom filter so a redelivered duplicate can be recognised and skipped without a full database lookup.'
We 'add an ID' — the standard, simple collocation for inserting an item into a Bloom filter. The other options are less idiomatic here.
2 / 5
Fill in: 'Skipping a dedup check on redelivered messages can ___ the same payment event processed twice after a consumer restart.'
We say a missing dedup check will 'leave' an event processed twice — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the Bloom filter for the expected item count and an acceptable false-positive rate, rather than guessing a size that fills up too soon.'
We 'size' a filter — the standard, simple collocation for calculating the parameters of a Bloom filter ahead of use. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ an incoming ID against the filter before doing any real work, so a genuine duplicate is rejected in microseconds, not after a full write.'
We 'check' an ID — the standard, simple collocation for testing membership in a Bloom filter. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ the Bloom filter periodically to a fresh one, since Redis Bloom filters can't shrink and a stale one only ever grows.'
We 'rotate a filter' — the standard, established collocation for replacing an ever-growing structure with a fresh one. The other options aren't the recognised term here.