Exploring data transformation

CDL notes, 18% of the exam, updated November 2026

This domain is about 18% of the exam. The main skill is matching a data need to a product: which database, which storage class, which analytics or pipeline tool. The guide’s list of products is Cloud Storage, Spanner, Cloud SQL, AlloyDB, Bigtable, BigQuery and Firestore, then Looker, Pub/Sub, Dataflow and Managed Service for Apache Spark. Know each as a one-line job.

Why data is valuable

  • Real-time business insight: see what is happening now, not last month.
  • Trends and patterns: forecast demand, spot churn, find fraud.
  • Strategic decisions: base choices on evidence.
  • Fuel for AI: models are only as good as the data they learn from. Organizations that own good data have an advantage.

Data is an asset only when it can be found, trusted and used. Collecting it without governance or analysis creates cost and risk, not value.

Databases, data warehouses and data lakes

Database Data warehouse Data lake
Purpose Run applications: read and write individual records quickly (OLTP) Analyze large volumes of structured data for reporting and BI (OLAP) Hold huge amounts of raw data in any format until needed
Data shape Structured, or flexible for NoSQL Structured, cleaned, modelled (schema defined up front) Structured, semi-structured and unstructured, kept as is
Users Applications Analysts, BI tools Data scientists, engineers
Google Cloud Cloud SQL, Spanner, AlloyDB, Firestore, Bigtable BigQuery Cloud Storage (often with BigQuery on top)

Trap: BigQuery is a warehouse for analytics, not a database to run a shopping cart. Cloud SQL or Spanner serve transactions. Many modern designs blur the lines with a “lakehouse” (open formats in Cloud Storage queried by BigQuery), but for the exam keep the basic split.

Types of data

By source

Type Meaning Example
First-party Collected directly by the organization from its own customers and systems Your website clicks, sales records
Second-party Another company’s first-party data, shared with you by agreement A partner airline sharing booking data with a hotel chain
Third-party Collected by an outside organization with no direct relationship, then sold or licensed Purchased demographic data sets

By structure

Type Meaning Example
Structured Fits rows and columns with a fixed schema Transactions, customer tables
Semi-structured Has tags or structure but no rigid table JSON, XML, logs
Unstructured No predefined model Images, video, audio, emails, documents

Most enterprise data is unstructured. AI, especially generative AI, makes unstructured data far more useful.

The data supply chain

Think of data as moving through stages, like goods in a supply chain.

  1. Data genesis: where data is created (customers, devices, apps, transactions).
  2. Data collection: gathering it (ingestion from apps, sensors, streams, batch loads). Pub/Sub often sits here.
  3. Data processing: cleaning, transforming and enriching (Dataflow, Spark).
  4. Data storage: keeping it in the right place (Cloud Storage, BigQuery, databases).
  5. Data analysis: exploring it with SQL, BI and ML (BigQuery, Looker, BigQuery ML).
  6. Data activation: putting insight to work: dashboards, alerts, personalised experiences, automated decisions, feeding apps and AI.

The last step matters most to business leaders. Insight that no one acts on has no value.

Data governance

Data governance is the set of policies, roles and processes that keep data accurate, secure, private, usable and compliant across its life.

It covers:

  • Ownership and stewardship: who is accountable for each data set.
  • Data quality standards.
  • Access control: who may see what (least privilege).
  • Privacy and compliance: GDPR, HIPAA and similar rules; classification of sensitive data.
  • Lineage and cataloging: knowing where data came from and what it means.
  • Retention and lifecycle rules.

Why it matters: trust in data, regulatory compliance, reduced risk of breaches, and reliable AI. Google Cloud tools that support governance include Dataplex Universal Catalog (discover, catalog and govern data across stores), Sensitive Data Protection (find and mask sensitive data) and IAM.

Openness and interoperability

A data silo is data trapped in one system or department. Vendor lock-in is being unable to leave a provider without heavy cost.

Why openness matters:

  • Open formats and standards (SQL, Parquet, Apache Iceberg, open source engines) let different tools read the same data.
  • Silos disappear when data from many sources and clouds can be analysed together.
  • Lock-in risk falls because data and code can move.

Google Cloud examples: BigQuery Omni analyses data sitting in other clouds, BigQuery reads open table formats, and managed open source engines (Spark, Kafka, PostgreSQL compatibility in AlloyDB) keep skills and code portable.

Choosing a Google Cloud data product

Key terms

Term Meaning
Relational Data in tables with rows, columns and relationships; queried with SQL (structured query language); strong consistency (ACID)
Non-relational (NoSQL) Flexible models: document, key-value, wide-column, graph; scales horizontally; schema can vary
Object storage Stores files as objects with metadata in buckets; ideal for unstructured data and backups

Product matching

Product Type Pick it when
Cloud Storage Object storage Store any unstructured data: images, video, backups, archives, data lake files. Very durable, unlimited scale
Cloud SQL Managed relational (MySQL, PostgreSQL, SQL Server) Standard business apps that need a regular relational database with minimal admin. Lift and shift of existing databases
AlloyDB Managed PostgreSQL-compatible relational High-performance, demanding transactional and analytical workloads on PostgreSQL; enterprise-grade, with strong performance and AI features. AlloyDB Omni runs it elsewhere
Spanner Globally distributed relational Relational with horizontal global scale, strong consistency and very high availability. Global financial or inventory systems that outgrow a single database
Bigtable NoSQL wide-column Very large, low-latency, high-throughput workloads: time series, IoT, ad tech, personalization. Billions of rows
Firestore NoSQL document database Mobile, web and serverless apps; real-time sync, offline support, flexible JSON-like documents
BigQuery Serverless data warehouse Analytics on petabytes with SQL; BI and ML on data; no infrastructure to manage

Quick decision path:

  1. Analytics over huge data and reporting -> BigQuery.
  2. Files, media, archives, raw lake data -> Cloud Storage.
  3. Transactions, relational and familiar -> Cloud SQL (or AlloyDB for higher performance).
  4. Relational but global scale and always on -> Spanner.
  5. Huge key-based throughput, IoT or time series -> Bigtable.
  6. App data with flexible documents and real-time sync -> Firestore.

Common trap: choosing Spanner when Cloud SQL is enough. Spanner is for global scale and very high availability; Cloud SQL is cheaper and simpler for ordinary apps.

Cloud Storage classes

All classes share the same durability, API and millisecond access. The differences are price to store, price to access, and minimum storage duration.

Class Access pattern Minimum duration Typical use
Standard Frequent, “hot” None Active data, websites, streaming, analytics
Nearline About once a month 30 days Regular backups, monthly reports
Coldline About once a quarter 90 days Disaster recovery files, older data
Archive Less than once a year 365 days Long-term retention, compliance archives
Autoclass Unpredictable n/a Moves each object automatically between classes based on actual access, removing the need to guess

The colder the class, the cheaper to store but the more expensive to retrieve. “Retrieve rarely, keep for years, lowest storage cost” means Archive. “Access pattern unknown or changing” means Autoclass. Object Lifecycle Management rules can also move or delete objects on a schedule.

Trap: colder classes are not slower to read. Even Archive returns data in milliseconds; you pay with higher access fees and minimum duration.

Migrating and modernizing databases

Options to bring a database to the cloud:

Approach Meaning Tool or example
Lift and shift (homogeneous) Same engine, moved to a managed equivalent Move MySQL to Cloud SQL for MySQL with Database Migration Service
Modernize to a managed or cloud-native database Change engine to gain scale or lower cost Oracle to AlloyDB or PostgreSQL; use DMS plus conversion tooling
Re-architect Redesign data model for the cloud Move to Spanner, Bigtable or Firestore for global scale or NoSQL needs
Rehost on VMs Run the database in Compute Engine unchanged Fastest but keeps the admin burden
Bare Metal Solution Specialised hardware for legacy workloads that can’t be virtualised Oracle workloads needing dedicated hardware

Benefits of managed databases: automated backups, patching, replication and failover, so teams spend time on applications. Database Migration Service performs minimal-downtime migration by continuously replicating changes.

Smart analytics and business intelligence

Looker

Looker is Google Cloud’s enterprise BI and analytics platform. Key ideas:

  • A semantic layer (LookML) defines metrics once, so everyone uses the same definition of “revenue”. This gives a single source of truth.
  • It democratizes data: business users explore data and build dashboards through self-service, without asking an analyst or writing SQL.
  • It queries data in place (including BigQuery), so reports reflect live data rather than stale extracts.
  • It supports embedded analytics and pushing insight into workflows, such as alerts and actions in business apps.
  • Conversational analytics with Gemini lets people ask questions in natural language.

Looker Studio is the lighter, free tool for simple dashboards and reports; Looker is the governed enterprise platform. For the exam, “governed, consistent metrics, embedded in apps” means Looker.

Real-time streaming analytics

Streaming analytics processes data as it arrives instead of in nightly batches.

Why it is critical:

  • Detect fraud while the transaction is happening.
  • Personalise the shopping experience during the visit.
  • Monitor equipment and react before failure.
  • Update dashboards and supply chains live.

Batch answers “what happened”. Streaming answers “what is happening”. Late insight often loses its value.

Modernizing data pipelines

Product Job
Pub/Sub Global, serverless messaging. Decouples producers from consumers; ingests streams of events at any scale (asynchronous, at-least-once delivery)
Dataflow Serverless processing for both streaming and batch data, based on open source Apache Beam. Transform, enrich and load data with autoscaling
Managed Service for Apache Spark (previously known as Dataproc) Managed Spark, Hadoop and related open source tools. Best for moving existing Spark and Hadoop jobs to the cloud with little change
BigQuery Receives streaming data directly and analyses it right away
Data Fusion / BigQuery pipelines Visual or low-code pipeline building

A typical streaming pipeline: devices or apps -> Pub/Sub -> Dataflow -> BigQuery -> Looker dashboard.

Choosing: new pipeline, serverless, streaming or batch = Dataflow. Existing Spark or Hadoop code = Managed Service for Apache Spark. Decoupled event ingestion = Pub/Sub.

Exam checklist

  • Database = run apps; warehouse = analytics (BigQuery); lake = raw data of any type (Cloud Storage).
  • Know first-, second- and third-party data and structured, semi-structured and unstructured data.
  • Supply chain order: genesis, collection, processing, storage, analysis, activation.
  • Governance = accuracy, security, privacy, compliance, ownership; supports trustworthy AI.
  • Openness avoids silos and lock-in; BigQuery Omni and open formats are examples.
  • Cloud SQL (standard relational), AlloyDB (high-performance PostgreSQL), Spanner (global relational), Bigtable (huge wide-column), Firestore (documents), BigQuery (warehouse), Cloud Storage (objects).
  • Storage classes: Standard, Nearline (30 days), Coldline (90), Archive (365), Autoclass (automatic).
  • Database Migration Service moves databases with minimal downtime.
  • Looker = governed, self-service BI on a semantic layer, querying BigQuery in place.
  • Pub/Sub ingests, Dataflow processes, Managed Service for Apache Spark runs existing Spark and Hadoop.

Test what you just read. 16 practice questions on exploring data transformation.

Practise this domain

All CDL notes