Replicated data stays correct only if replicas agree on what happened. Quorums are the simplest tool: with N replicas, writing to W and reading from R guarantees a read sees the latest acknowledged write whenever R + W > N. Majorities (more than half) are the common choice because any two majorities overlap.
Some decisions must be made by exactly one node at a time: which replica is the leader, who holds a lock, which configuration version is current. Consensus protocols such as Raft and Paxos let a majority agree on a sequence of decisions even when nodes fail or messages are delayed. They cannot stop a deposed leader that does not yet know it lost; a fencing token (a number that grows with every new leader) lets storage reject the old leader's writes. Use consensus for small, critical state, not for bulk data.
Size quorums, elect one leader safely and fence leaders that lost their role.