Cloud Digital Leader Google Cloud Products and Services Practice Question
A startup is building a mobile app backend that requires a scalable NoSQL database with real-time synchronisation across devices. The database should support offline access and automatic conflict resolution. Which Google Cloud database service meets these requirements?
⚠ Common exam trap
The trap here is conflating 'scalable NoSQL on GCP' with Bigtable or Spanner — candidates who focus only on scale miss that the question's real signal is mobile offline sync and real-time listeners, which only Firestore provides.
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
✓
Firestore
Firestore is Google Cloud's serverless document NoSQL database with built-in real-time listeners, offline persistence on mobile/web SDKs, and automatic conflict resolution via last-write-wins semantics. These features map directly to the mobile backend requirements of real-time sync, offline access, and conflict handling without custom code. Cloud Spanner, Cloud SQL, and Bigtable do not provide native mobile SDKs with offline sync.
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.
Visual reference
Quick reference
Cloud Service Model Comparison
| Model | You Manage | Provider Manages | Examples |
|---|---|---|---|
| IaaS | OS, runtime, apps, data | Hardware, hypervisor, networking | EC2, Azure VMs, GCP Compute Engine |
| PaaS | Apps and data | OS, runtime, middleware, hardware | Elastic Beanstalk, Azure App Service |
| SaaS | Data and settings only | Everything else | Microsoft 365, Salesforce, Workday |
| FaaS / Serverless | Function code only | Infra, scaling, runtime | Lambda, Azure Functions, Cloud Run |
| CaaS | Containers and apps | Kubernetes, OS, hardware | EKS, AKS, GKE |
Go deeper
Related to this question
Learn chapter
Building a Cloud ROI Business Case
Key term
Firestore
Firestore is a flexible, scalable, serverless NoSQL database from Google Cloud that automatically syncs data across applications in real time.
Key term
Serverless
Serverless is a cloud computing model where the cloud provider manages the servers, and you only pay for the actual compute time your code uses, without having to worry about provisioning or maintaining infrastructure.
About these practice questions
One of 848 original GCDL practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official Google Cloud exam blueprint
This GCDL 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 GCDL exam.