Cassandra Consistency Level Tuning Language Collocations
Practise the standard verbs for tuning Cassandra consistency levels per query.
0 / 5 completed
1 / 5
Fill in: 'We ___ the read and write consistency level per query rather than globally, so a critical read can demand QUORUM while a low-stakes write stays fast at ONE.'
We 'set a consistency level' — the standard, simple collocation for configuring how many replicas must agree per query. The other options are less idiomatic here.
2 / 5
Fill in: 'Defaulting every query to consistency level ONE can ___ a stale replica's answer accepted as correct even seconds after a conflicting write elsewhere in the cluster.'
We say a low consistency level will 'leave' stale reads accepted — the standard, natural collocation for the resulting risk. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the consistency level against the replication factor deliberately, since QUORUM only guarantees a consistent read when reads and writes together exceed the replica count.'
We 'tune' a level — the standard, simple collocation for deliberately balancing a configuration against another related setting. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ read-after-write behaviour under the chosen consistency level in a staging cluster, so a surprising stale read isn't discovered for the first time in production.'
We 'verify' behaviour — the standard, simple collocation for confirming a system behaves as expected before trusting it live. The other options are less idiomatic here.
5 / 5
Fill in: 'We ___ consistency level choices across every query path periodically, since a level picked hastily during an incident can quietly stay wrong long after the outage ends.'
We 'audit' choices — the standard, simple collocation for periodically reviewing configuration decisions. The other options are less idiomatic here.