Study guide

2.2 Google Cloud Data Management Solutions

Google Cloud Digital Leader Exam

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

1.1 Current Exam Facts 1.2 How to Prepare & Use This Guide 1.3 What Changed in the August 12, 2026 Exam Update

2 Digital Transformation with Google Cloud

1.1 Why Cloud Technology Is Transforming Business 1.2 Fundamental Cloud Concepts 1.3 Cloud Computing Models and Shared Responsibility 1.4 Agentic AI, Open Standards, and Google Cloud's Differentiators

3 Exploring Data Transformation with Google Cloud

2.1 The Value of Data 2.2 Google Cloud Data Management Solutions 2.3 Making Data Useful and Accessible 2.4 Data Types, the Data Supply Chain, and Interoperability

4 Innovating with Google Cloud Artificial Intelligence

3.1 AI and ML Fundamentals 3.2 Google Cloud's AI and ML Solutions 3.3 Building and Using Google Cloud AI and ML Solutions 3.4 Gemini, the Agent Platform, and the AI Hypercomputer

5 Modernize Infrastructure and Applications with Google Cloud — Part 1

4.1 Cloud Modernization and Migration 4.2 Computing in the Cloud 4.3 Serverless Computing

6 Modernize Infrastructure and Applications with Google Cloud — Part 2

4.4 Containers in the Cloud 4.5 The Value of APIs 4.6 Hybrid and Multi-Cloud

7 Trust and Security with Google Cloud

5.1 Trust and Security in the Cloud 5.2 Google's Trusted Infrastructure 5.3 Google Cloud's Trust Principles and Compliance 5.4 Google Threat Intelligence, Security Command Center, and Google SecOps 5.5 Securing the AI Stack: AI Protection, Model Armor, and Zero Trust

8 Scaling with Google Cloud Operations

6.1 Financial Governance and Managing Cloud Costs 6.2 Operational Excellence and Reliability at Scale 6.3 Sustainability with Google Cloud 6.4 Cloud Observability, SLIs, SLOs, and the Four Golden Signals

2.2 Google Cloud Data Management Solutions

Key Takeaways Explain This Topic AI

Google Cloud offers purpose-built data management products: Cloud SQL and Cloud Spanner for relational workloads, Firestore and Cloud Bigtable for NoSQL, BigQuery for analytics, and Cloud Storage for object data

BigQuery is a serverless, managed enterprise data warehouse and analytics engine that can query data across clouds with BigQuery Omni, charging per query rather than per idle server

Cloud Storage offers four classes, Standard, Nearline, Coldline, Archive, differentiated by access frequency, minimum storage duration, and price, so organizations match cost to access patterns

Database migration and modernization paths include lift-and-shift to managed services, refactoring to cloud-native engines, and tools such as Database Migration Service that minimize downtime

Last updated: August 2026

Relational, Non-Relational, and Object Storage

Quick Answer: Google Cloud data management products fall into three families. Relational systems (Cloud SQL, Cloud Spanner) store structured rows with strict schemas and SQL (Structured Query Language). Non-relational systems (Firestore, Cloud Bigtable) store flexible, schemaless records optimized for scale or developer speed. Object storage (Cloud Storage) stores blobs of any type and size, accessed by a key rather than queried.

Concept What it is Query style Strength

Relational (SQL) Tables with fixed schema, rows and columns, strong consistency SQL, joins, transactions Complex relationships, ACID guarantees

Non-relational (NoSQL) Documents, key-value, wide-column, or graph stores API or simple queries by key Horizontal scale, flexible schema, low latency at high throughput

Object storage Blobs (images, video, backups, logs) addressed by URL/key REST API, not SQL Massive scale, low cost, any data type

Google Cloud Data Management Product Decision Matrix

Product Data model Type Scaling Best-fit use case Not for

Cloud SQL Relational (PostgreSQL, MySQL, SQL Server) Managed SQL database Vertical, read replicas Web and application backends, ERP/CRM lift-and-shift Global horizontal scale beyond one region

Cloud Spanner Relational, horizontally scalable Managed, globally distributed SQL database Horizontal, global Global transactional apps, financial ledgers, inventory at planet scale Cheap, small, single-region workloads

Cloud Bigtable Wide-column NoSQL Managed NoSQL Horizontal, petabyte-scale High-throughput time-series, IoT telemetry, AdTech, ML feature stores Small datasets, complex ad-hoc SQL analytics

Firestore Document NoSQL Serverless document database Automatic Mobile and web apps, user profiles, real-time sync, serverless backends Heavy joins, relational analytics

BigQuery Relational, columnar Serverless data warehouse and analytics engine Petabyte-scale, serverless Analytics, BI, data warehouse, ML, multicloud analysis Low-latency transactional writes, OLTP

Cloud Storage Objects (blobs) Object storage Exabyte-scale, global Media, backups, archives, data lake, static website, ML training data Querying rows with joins

AlloyDB Relational (PostgreSQL-compatible) Managed PostgreSQL-compatible database Vertical plus read pools; columnar engine for analytics Demanding PostgreSQL workloads needing more throughput than Cloud SQL, and hybrid transactional/analytical work in one engine Non-PostgreSQL engines; global multi-region writes

A practical rule: if the workload is transactional and relational, start with Cloud SQL; if it must be global and strongly consistent, choose Spanner; if it is high-throughput and schema-flexible, use Bigtable or Firestore; if it is analytics, use BigQuery; if it is a file or blob, use Cloud Storage.

Updated-exam addition - AlloyDB. The exam guide effective August 12, 2026 adds AlloyDB to the products you must be able to place. AlloyDB is Google Cloud's PostgreSQL-compatible database built for demanding enterprise workloads: it keeps full PostgreSQL compatibility (so migration is a replatform, not a rewrite) while delivering substantially higher transactional throughput than standard Cloud SQL and adding a built-in columnar engine that runs analytical queries on live operational data. Position it between Cloud SQL and Spanner: choose Cloud SQL for ordinary managed PostgreSQL, AlloyDB when PostgreSQL compatibility must be preserved but performance has outgrown Cloud SQL, and Spanner when the requirement is globally distributed strong consistency.

BigQuery: Serverless, Managed, Multicloud Analytics

BigQuery is Google Cloud's serverless, fully managed enterprise data warehouse and analytics engine. Its defining properties:

Serverless : no infrastructure to provision, patch, or scale. Capacity is allocated automatically per query.

Managed warehouse : storage, indexing, caching, and compute are handled by Google. You load or stream data in, then query it with standard SQL.

Analytics engine : BigQuery is not just storage. It runs fast, distributed SQL across petabytes, supports ML (BigQuery ML), geospatial analysis, and federated queries against external data.

Pay-per-query : pricing is based on bytes processed (for queries) and bytes stored (for storage), not on idle servers. This aligns cost to actual use.

Multicloud via BigQuery Omni : BigQuery Omni lets you run BigQuery analytics against data stored in AWS S3 or Azure Blob without moving it into Google Cloud, addressing multicloud and data-residency constraints.

Common use cases: replacing an on-prem data warehouse, building a single source of truth, ad-hoc exploration, dashboard backends for Looker, and training ML models without exporting data.

Cloud Storage Classes: Match Cost to Access Frequency

Cloud Storage stores immutable objects in buckets . Classes differ in price, access frequency assumptions, minimum storage duration, and availability SLA. Choosing the right class is one of the most common exam scenarios.

Class Designed for Access frequency Minimum storage duration Availability SLA Relative cost Typical use case

Standard Hot, frequently accessed data Frequent None 99.95% in multi-region Highest of the four Website assets, active analytics inputs, hot backups

Nearline Infrequently accessed data Once per month or less 30 days 99.9% in multi-region Lower than Standard Backups accessed monthly, long-tail log files

Coldline Rarely accessed data Once per quarter or less 90 days 99.9% in multi-region Lower than Nearline Disaster recovery backups, regulatory archives accessed rarely

Archive Very rarely or never accessed Once per year or less 365 days 99.9% in multi-region Lowest Cold archives, raw data retained for compliance, rarely touched backups

Two price components matter: storage price (lower for colder classes) and retrieval price (higher for colder classes). The right choice minimizes the combined cost. An object accessed daily should be Standard; an object accessed once a year should be Archive. Misclassifying hot data as Archive can cost more in retrieval fees than the storage savings - and because every class carries a minimum storage duration, deleting or rewriting an Archive object before 365 days still bills you for the full 365.

Exam trap - all four classes are equally fast. Cloud Storage classes differ in price , not in access speed . Google states that Archive data "is available within milliseconds, not hours or days," which is a deliberate contrast with the multi-hour thaw times other cloud providers impose on their coldest tiers. If a question offers "retrieval takes several hours" as a property of Archive, that option is wrong. What actually changes as you go colder is the storage price (down), the retrieval price (up), and the minimum storage duration (up).

Updated-exam addition - Autoclass. The exam guide that takes effect on August 12, 2026 adds Autoclass to this list. Autoclass is a bucket-level setting that moves each object between Standard, Nearline, Coldline, and Archive automatically based on that object's own access pattern, with no early-deletion or retrieval charges. It is the right answer when a customer wants class-based savings but cannot predict or does not want to manage access patterns per object.

Database Migration and Modernization Paths

Organizations rarely build greenfield; they migrate existing databases. Google Cloud supports multiple paths:

Lift-and-shift — move a database to a managed service with minimal change, for example, on-prem MySQL to Cloud SQL. Lowest risk, fastest, but leaves the schema and architecture as-is.

Refactor / modernize — change the schema or engine to a cloud-native option, for example, moving from a single-region relational database to Cloud Spanner for global scale, or from a custom key-value store to Bigtable. Higher effort, greater long-term benefit.

Database Migration Service (DMS) — a managed migration service that streamlines moving databases to Google Cloud with minimal downtime, using continuous replication to keep source and target in sync until cutover.

Native tools — engine-specific tools such as pg_dump / pg_restore for PostgreSQL, SQL Server Import/Export, and third-party ETL (Extract, Transform, Load) for large-scale reshaping.

The right path depends on urgency, risk tolerance, and the desired end state. Many migrations start with lift-and-shift to retire data-center contracts quickly, then refactor over time.