Courseiva
mediumMultiple ChoiceObjective-mapped

Google ACE Practice Question: A team is building a real-time multiplayer game…

A team is building a real-time multiplayer game backend requiring low-latency state synchronization between players worldwide. Session data must persist for the duration of a game (up to 2 hours) but doesn't need long-term storage. Which managed service best fits?

⚠ Common exam trap

Google Cloud often tests the distinction between in-memory caches (Redis) and persistent databases (Cloud SQL, Bigtable, Firestore), where candidates mistakenly choose a database with real-time features (like Firestore) without recognizing that its latency and consistency model are insufficient for sub-millisecond state synchronization.

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Cloud Memorystore for Redis

Cloud Memorystore for Redis is the best fit because it provides an in-memory data store with sub-millisecond latency, ideal for real-time state synchronization in a multiplayer game. Redis supports data structures like sets and sorted sets for leaderboards or session state, and its optional persistence (RDB/AOF) can cover the 2-hour game duration without needing long-term storage. This aligns with the requirement for low-latency, ephemeral session data that must survive only the game session.

Answer analysis

Option-by-option breakdown

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

  • Cloud SQL for PostgreSQL with connection pooling

    Why it's wrong here

    Cloud SQL for PostgreSQL is a fully managed relational database built for ACID transactions and complex SQL, but its average query latency often ranges from 5–20 ms, even with connection pooling from the app tier, because the bottleneck is database engine processing and disk I/O. It does not provide automatic key expiry, so session cleanup would require custom jobs or a scheduled delete process, adding operational complexity. Relational databases are designed for structured, persistent operational data, not for low-latency temporary key-value lookups, making it unsuitable for real-time session synchronization.

  • Cloud Memorystore for Redis

    Why this is correct

    Cloud Memorystore for Redis is a fully managed in-memory data store that delivers sub-millisecond latency, making it ideal for real-time game session state. Its native key expiration (TTL) automatically clears stale sessions, and the Redis data structure server supports complex session objects such as hashes or sorted sets. Unlike persistent databases, Memorystore is designed for high-throughput, low-latency read/write workloads with occasional data loss tolerated, perfectly matching ephemeral state requirements.

  • Cloud Bigtable

    Why it's wrong here

    Cloud Bigtable is a wide-column NoSQL database that excels at serving large-scale analytical and time-series workloads with high throughput, but its latency profile is single-digit milliseconds, too high for sub-millisecond session lookups. Bigtable also lacks native key-level TTL; data expiration requires application-managed deletion or column-level timestamps for garbage collection. Its storage architecture is optimized for range scans and batch reads, not for the highly random, write-heavy access pattern of game session updates.

  • Cloud Firestore in Native mode

    Why it's wrong here

    Cloud Firestore in Native mode is a serverless, document-oriented database that prioritizes data durability, strong consistency (in most regions), and real-time synchronization through listeners. However, it persists data to disk and replicates it, introducing latency in the tens to hundreds of milliseconds — far above the sub-millisecond target for live game state. Using Firestore as a session cache would incur extra cost, higher latency, and unneeded features like queries and transactions, while TTLs are only available via a scheduled delete service, not native key expiration.

About these practice questions

Courseiva writes every ACE question from scratch — 769 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ACE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the ACE exam.