Study guide

4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable

Google Cloud Associate Cloud Engineer ACE

Track your progress as you read

Finished sections get a check mark.

1 Chapter 1: Introduction & Exam Overview

1.1 About the GCP Associate Cloud Engineer Exam 1.2 How to Use This Study Guide & Build a Study Plan

2 Chapter 2: Resource Hierarchy, IAM Basics & Cloud Identity

2.1 The GCP Resource Hierarchy: Organizations, Folders & Projects 2.2 Organization Policies & Granting IAM Roles 2.3 Cloud Identity: Managing Users and Groups

3 Chapter 3: APIs, Quotas & Billing Configuration

3.1 Enabling APIs and Provisioning Cloud Operations Suite 3.2 Assessing and Requesting Quota Increases 3.3 Billing Accounts, Project Linking & Billing Exports 3.4 Billing Budgets and Alerts

4 Chapter 4: Planning Compute & Storage Resources

4.1 Choosing the Right Compute Option: GCE vs. GKE vs. Cloud Run vs. Cloud Functions 4.2 Spot VMs, Custom Machine Types & Cost-Optimized Compute Planning 4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable 4.4 Cloud Storage Classes & Persistent Disk Types

5 Chapter 5: Planning Network Resources

5.1 Load Balancing Options and Use Cases 5.2 Regional Resource Placement & High Availability Planning 5.3 Network Service Tiers: Premium vs. Standard

6 Chapter 6: Deploying Compute Engine Workloads

6.1 Launching Compute Engine Instances: Disks, SSH Keys & Availability Policies 6.2 Managed Instance Groups, Instance Templates & Autoscaling 6.3 OS Login and VM Manager for Fleet Configuration

7 Chapter 7: Deploying Google Kubernetes Engine Workloads

7.1 Installing and Configuring kubectl 7.2 Deploying GKE Clusters: Autopilot, Regional, Private & GKE Enterprise 7.3 Deploying Containerized Applications to GKE

8 Chapter 8: Deploying Serverless & Event-Driven Applications

8.1 Deploying Applications to Cloud Run and Cloud Functions 8.2 Event-Driven Architectures: Pub/Sub, Cloud Storage Triggers & Eventarc

9 Chapter 9: Deploying Data Solutions

9.1 Deploying Data Products: Cloud SQL, Firestore, Spanner, BigQuery & AlloyDB 9.2 Deploying Pub/Sub, Dataflow & Loading Data into Google Cloud

10 Chapter 10: Deploying Networking Resources & Infrastructure as Code

10.1 Creating VPCs, Subnets & Shared VPC 10.2 Firewall Rules, Cloud VPN & VPC Network Peering 10.3 Infrastructure as Code: Terraform, Config Connector, Cloud Foundation Toolkit & Helm

11 Chapter 11: Managing Compute Engine & GKE in Production

11.1 Connecting to and Managing Running Compute Engine Instances 11.2 Working with Snapshots and Custom Images 11.3 Managing GKE Clusters: Node Pools, Workloads & Artifact Registry Access 11.4 Horizontal and Vertical Pod Autoscaling in GKE

12 Chapter 12: Managing Cloud Run, Storage & Database Operations

12.1 Managing Cloud Run Revisions, Traffic Splitting & Scaling 12.2 Managing and Securing Cloud Storage Objects & Lifecycle Policies 12.3 Querying, Estimating Costs, Backup & Job Monitoring for Databases (Cloud SQL, BigQuery, Spanner, Dataflow)

13 Chapter 13: Networking Operations, Monitoring & Logging

13.1 Networking Operations: Subnets, Static IPs, Cloud DNS & Cloud NAT 13.2 Cloud Monitoring: Alerts, Custom Metrics & Dashboards 13.3 Cloud Logging: Buckets, Log Analytics, Routers & Filtering 13.4 Diagnostics, Ops Agent, Managed Service for Prometheus & Audit Logs

14 Chapter 14: IAM Policies & Role Types

14.1 IAM Policies: Structure, Bindings & Policy Hierarchy 14.2 IAM Role Types: Basic, Predefined & Custom Roles

15 Chapter 15: Service Accounts & Security Configuration

15.1 Creating Service Accounts & Assigning Least-Privilege Permissions 15.2 Assigning Service Accounts to Resources & Managing SA IAM Policies 15.3 Service Account Impersonation & Short-Lived Credentials

16 Chapter 16: Exam Readiness — Scenarios & Test-Day Strategy

16.1 Common ACE Exam Scenarios & Decision Frameworks 16.2 Test-Day Logistics, Time Management & Final Review Checklist

4.3 Choosing a Data Storage Product: Cloud SQL, BigQuery, Firestore, Spanner & Bigtable

Key Takeaways Explain This Topic AI

Start every storage-product decision with two questions: transactional vs. analytical, and (if transactional) relational/SQL vs. NoSQL.

Cloud SQL scales vertically within one region (MySQL/PostgreSQL/SQL Server); Cloud Spanner scales horizontally across regions with SQL and 99.999% availability.

AlloyDB is the PostgreSQL-compatible option for enterprise workloads needing higher throughput than Cloud SQL without Spanner's global distribution.

Firestore is a serverless NoSQL document database with real-time sync and offline support, built for mobile/web app backends.

Bigtable handles massive-scale, low-latency NoSQL wide-column workloads (IoT, time-series); BigQuery is the separate OLAP data warehouse for large-scale SQL analytics.

Last updated: July 2026

Why This Section Matters

The exam guide's third planning bullet is data storage product choice , and it is arguably the single most-tested "which service?" decision on the entire ACE exam because Google Cloud offers so many overlapping-sounding database options. The exam expects you to sort a scenario along two axes almost instantly: transactional versus analytical , and relational (SQL) versus non-relational (NoSQL) . Once those two questions are answered, the correct product is usually the only one left standing.

The Two Questions That Decide Everything

Is this workload transactional (OLTP) — many small, fast reads/writes supporting an application — or analytical (OLAP) — scanning large volumes of historical data to find patterns and produce reports?

If transactional, does it need a fixed relational schema and SQL joins, or is it flexible/document/key-value shaped?

The Five Core Products

Cloud SQL is a fully managed relational database running MySQL, PostgreSQL, or SQL Server . It automates provisioning, patching, backups, and failover, but it scales vertically within a single region — there is a ceiling on how large a single instance can grow. It is the default choice for general-purpose web apps, CRM/ERP systems, and any workload that just needs "a normal SQL database, but managed."

Cloud Spanner is Google's globally distributed, horizontally scalable relational database with SQL support and strong (external) consistency , backed by a 99.999% availability SLA on multi-region configurations. Choose Spanner over Cloud SQL exactly when a scenario needs relational/SQL semantics at a scale or geographic distribution Cloud SQL cannot reach — global financial ledgers, worldwide inventory systems, or any workload where a single-region vertical-scaling ceiling would eventually be hit.

AlloyDB for PostgreSQL is a fully managed, PostgreSQL-compatible database built for the most demanding enterprise workloads, offering significantly higher transactional throughput and much faster analytical queries than standard PostgreSQL while remaining wire-compatible with the open-source ecosystem. Think of it as the answer when a scenario specifically calls for PostgreSQL compatibility at higher performance than Cloud SQL for PostgreSQL provides, without needing Spanner's global distribution.

Firestore is a serverless, NoSQL document database optimized for application and mobile/web backends: it offers real-time data synchronization, offline support for mobile clients, and flexible JSON-like documents rather than fixed schemas/tables. It is the default pick for mobile app backends, user profiles, and content that naturally nests as documents.

Bigtable is a wide-column NoSQL database built for massive scale, high throughput, and low latency — think terabytes to petabytes of data with millions of operations per second, such as IoT sensor streams, time-series data, and ad-tech clickstreams. Bigtable does not support SQL joins or complex ad-hoc queries; it is optimized around fast lookups by row key.

BigQuery , though it also appears in this ecosystem, is fundamentally different from the other four: it is a serverless data warehouse for OLAP — large-scale SQL analytics over historical/aggregated data — priced primarily by data stored plus data scanned per query (or flat-rate/reservation pricing for predictable heavy workloads). If a scenario describes "running ad-hoc SQL reports across years of business data," BigQuery is almost always the answer, regardless of what other database is mentioned in the same sentence.

Comparison Table

  • Product Data model Scale pattern Best for
  • Cloud SQL Relational (MySQL/PostgreSQL/SQL Server) Vertical, single-region General web/CRM/ERP apps

Cloud Spanner Relational, SQL, strongly consistent Horizontal, multi-region Global-scale relational apps needing strong consistency

  • AlloyDB PostgreSQL-compatible Vertical, high-performance Enterprise Postgres workloads needing more throughput
  • Firestore NoSQL document Horizontal, serverless Mobile/web app backends, real-time sync
  • Bigtable NoSQL wide-column Horizontal, massive throughput IoT, time-series, ad-tech at petabyte scale

BigQuery SQL data warehouse (OLAP) Serverless, scans petabytes Analytics, BI reporting, ad-hoc SQL over history

Realistic Exam Scenario

A logistics company needs a single source of truth for shipment records that must remain strongly consistent across data centers in the US, Europe, and Asia, using standard SQL for application queries, with no acceptable window of inconsistency. Cloud SQL cannot span regions with strong consistency, so the answer is Cloud Spanner — the combination of "global," "SQL," and "strongly consistent" is Spanner's exact niche.

Now contrast: a mobile fitness app needs to sync workout data across a user's phone and the cloud in real time, and must keep working (queueing writes) when the phone loses connectivity. That combination of real-time sync and offline support points to Firestore , not Cloud SQL or Bigtable, since neither of those offers native mobile offline persistence.

Common Traps

Picking Bigtable for a workload that needs SQL joins or complex queries — Bigtable intentionally trades query flexibility for raw throughput, so if the scenario needs relational queries, Bigtable is wrong even if the data volume sounds "big."

Picking BigQuery for an OLTP workload just because it says "big" data — BigQuery is not designed for row-level transactional updates at low latency; that is Cloud SQL, Spanner, AlloyDB, or Firestore territory.

Defaulting to Cloud SQL whenever "relational" appears in a scenario without checking for the words "global," "multi-region," or "unlimited horizontal scale" — those words signal Spanner, not Cloud SQL.