Cloud Digital Leader Practice Question: A startup is building a gaming application where…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Eventual consistency is sufficient; the game can show slightly stale state to some players without impact on gameplay

  Why it's wrong here

  In a real-time multiplayer game, eventual consistency means replays or replicas may lag behind the latest write, so different players can simultaneously read different versions of game state. That is not a benign minor artifact: a player who moves to a new position while another player still reads the old position will produce contradictory combat or capture events, and the game will have no single authoritative result to resolve disputes. Strong consistency ensures that every read after a write returns the latest value, preventing these conflicting views from ever becoming visible.

• ✓

  Strong consistency is required so all players simultaneously read the same current game state; eventual consistency would create conflicting game states visible to different players

  Why this is correct

  This is correct. Strong consistency guarantees that after a write (player moves), all subsequent reads from any client see that write. This ensures all players operate on the same view of game state. Cloud Spanner's external consistency or Firestore's strongly consistent reads serve this requirement.

• ✗

  Consistency doesn't matter for gaming databases because games update state so frequently that any inconsistency resolves within milliseconds

  Why it's wrong here

  The claim that frequent updates make inconsistency irrelevant confuses eventual convergence with immediate correctness. In a real-time game with tens of state changes per second, even a few hundred milliseconds of divergence is an eternity: one player's client may show a shield as active while another player's client reads it as expired, leading to damage calculations based on incompatible realities. Furthermore, frequent writes do not guarantee that conflicting replicas will converge quickly—without strong consistency, multiple clients can commit conflicting writes, and the resulting state may never be fully reconciled into a single consistent timeline.

• ✗

  The game should avoid databases entirely and use local storage on each player's device to ensure fast, consistent state access

  Why it's wrong here

  Using local storage on each player's device removes any shared source of truth, which is precisely what real-time multiplayer needs. If every player writes to their own local store and asynchronously merges, there is no global arbitration: one player's local state may record a successful shot while another player's local state records a dodge, and no database or server can impose a single serial order of operations. Strong consistency requires a centralized or coordinated system (like Cloud Spanner or strongly consistent Firestore reads) that orders all writes and ensures every client observes the same latest game state.

Go deeper

Related to this question