After a citizen updates a profile, two readers briefly see different versions before the system converges. What NoSQL behavior does this illustrate?
Select an answer to reveal the explanation.
Short Explanation
Sometimes one phone shows the new address a beat before another does—that is eventual consistency. Replicas catch up; they just are not identical every millisecond. Totally normal in many NoSQL setups.
Full Explanation
Eventual consistency allows replicas to diverge temporarily after an update and later converge to the same value. Brief disagreements between readers are expected under that model rather than treated as catastrophic failure. Many distributed NoSQL systems accept this tradeoff to improve availability and latency. Recognizing eventual consistency prevents misreading temporary profile version skew as permanent corruption.