Ballot tabulation mirrors across election sites must never display conflicting totals to the public. Under a network partition, which consistency stance is most appropriate?
Select an answer to reveal the explanation.
Short Explanation
Election totals are not the place for "close enough" reads. If sites disagree, citizens lose trust fast. Consistency-first under partition means you may wait or block rather than flash two different scores.
Full Explanation
Ballot tabulation is a workload where conflicting reads across sites are unacceptable. Consistency-oriented (CP) choices favor agreement—even if some requests fail or wait—when partitions occur. Availability-first serving of divergent local totals would undermine public trust in election results. Selecting a consistency-preferring stance under partition aligns the NoSQL or distributed store with that civic requirement.