Cloud Digital Leader Google Cloud Products and Services Practice Question

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 Spanner

  Why it's wrong here

  Cloud Spanner is a globally distributed, strongly consistent relational database designed for horizontal scalability across regions, but it operates as a server-side OLTP system. It offers no client-side offline persistence or synchronization primitives for mobile endpoints. Mobile apps require local caching and conflict resolution to function without continuous connectivity, which Spanner does not provide. Additionally, its SQL and distributed transaction model are overkill for a typical mobile backend and add latency and cost.

• ✗

  Cloud SQL

  Why it's wrong here

  Cloud SQL is a managed relational database service (MySQL/PostgreSQL) that requires persistent connectivity from the application; it has no built-in client-side data cache or offline write queue. Real-time synchronization to mobile devices is absent, as it uses traditional query protocols and does not emit event-driven updates. For a mobile backend, developers would need to build custom sync logic and conflict handling, which Firestore already provides natively.

• ✗

  Cloud Bigtable

  Why it's wrong here

  Cloud Bigtable is a high-throughput, low-latency wide-column NoSQL database optimized for analytical and operational workloads such as time-series or IoT data, not for mobile client synchronization. It does not provide an offline-first data model or a client SDK with automatic sync and conflict resolution. While Bigtable supports replication across regions, that is server-side durability, not the app-level real-time updates required for offline-aware mobile apps. Its access patterns and API are also inappropriate for a small mobile backend.

• ✓

  Firestore

  Why this is correct

  Firestore is a mobile-first document database with built-in offline persistence: data is stored locally on the device, enabling reads and writes without connectivity. When the device reconnects, Firestore automatically synchronizes local changes to the server and resolves conflicts using deterministic rules (e.g., last-write-wins by server timestamp). Its SDK offers real-time listeners that push updates to clients, making it ideal for chat, collaboration, and other interactive mobile features. Firestore's security rules and transaction support further streamline mobile backend development.

Go deeper

Related to this question