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 Bigtable

  Why it's wrong here

  Cloud Bigtable is a fully managed, scalable wide-column NoSQL database optimized for large analytical and operational workloads, not document-oriented data. It excels at time-series, IoT, and high-throughput key-value access patterns, but does not provide a document data model with flexible schemas, nested fields, or rich querying like Firestore. Its scaling and low-latency strengths target a different access profile than the mobile/web real-time document use case.

• ✓

  Firestore

  Why this is correct

  Firestore is Google Cloud's fully managed, scalable NoSQL document database designed for mobile and web applications, offering real-time listeners, offline persistence, and automatic multi-region replication. Data is stored in documents organized into collections, with flexible schema and powerful querying, making it ideal for user profiles, chat messages, and other semi-structured data. Its serverless scaling and client SDKs are optimized for direct app-to-database access, which distinguishes it from the alternatives.

• ✗

  Cloud SQL

  Why it's wrong here

  Cloud SQL is a fully managed relational database service supporting MySQL, PostgreSQL, and SQL Server, and is fundamentally not a document database. It uses a fixed schema with rows and columns, enforcing ACID transactions and SQL joins, which contrasts sharply with Firestore's document model and flexible schema. While Cloud SQL is scalable to a degree, it does not offer real-time listeners or offline synchronization for client apps, and scaling typically requires read replicas or sharding rather than automatic distribution.

• ✗

  Memorystore

  Why it's wrong here

  Memorystore is Google Cloud's managed in-memory caching service, providing Redis and Memcached engines for sub-millisecond latency use cases like session storage, caching, and real-time leaderboards. It is not a document database and does not store structured documents with queryable fields; data is typically stored as key-value pairs or Redis data structures. Memorystore is designed to offload reads from primary databases, not to serve as the authoritative, durable data store with real-time listening that Firestore provides.

Go deeper

Related to this question