Under eventual consistency, what happens to disagreeing copies?
- They reconcile and converge later
- They disagree forever
- They delete themselves
Under strong consistency, what does every reader see?
- A random older copy
- The latest write, as if one copy existed
- Nothing until the next day
During a network split a store can stay strongly consistent and fully available at once.
Circle one: True False
The same split happens under eventual consistency. What may each side do?
- Shut down until an operator arrives
- Keep serving and merge changes when the link heals
- Refuse all reads and writes
A split divides the store in two under strong consistency. What may each side do?
- Both sides keep taking writes freely
- Both sides delete their data
- One side pauses writes so no split brain grows
Should a shopping basket and a bank balance share one consistency choice?
- No, the balance needs strong while the basket survives eventual
- Yes, one database means one choice
- No, the basket needs strong while the balance survives eventual
A developer says eventual consistency means reads may return stale data forever. What is wrong?
- Nothing, forever-stale is the definition
- Convergence is promised: copies reconcile once the split heals
- Stale reads never happen under eventual consistency
A ticket shop sells the last seat twice during a split. Which choice caused it, and what fixes it?
- Strong consistency caused it; go eventual
- The split caused it; no model choice matters
- Eventual consistency caused it; the seat count needs strong