Dataplex Study Notes

Dataplex is an intelligent data fabric that helps you discover, organize, secure, and govern data at scale across data lakes, warehouses, and databases. It provides a unified catalog, data quality, and governance layer over assets stored in Cloud Storage and BigQuery. Dataplex addresses management and trust, not raw storage or query execution itself.

Key facts

• Dataplex organizes data into lakes, which are logical domains, containing zones that are either raw or curated, with assets mapped to underlying Cloud Storage buckets or BigQuery datasets.
• Raw zones hold data in its original format with no quality guarantees, while curated zones hold cleaned, formatted data in formats such as Parquet with schemas enforced for consumers.
• Automatic metadata harvesting crawls registered assets to build a searchable data catalog, capturing schemas, partitions, and technical metadata without manual documentation effort.
• Data quality tasks in Dataplex can run scheduled checks using defined rules, publish results to BigQuery and the catalog, and alert on failures to support data reliability practices.
• Data lineage and discovery features, now closely integrated with Dataplex Catalog, help users find trusted datasets, understand origins, and assess impact before changing pipelines.
• Dataplex integrates with IAM and VPC Service Controls to apply consistent security and governance policies centrally, rather than configuring every bucket and dataset in isolation.
• It supports data profiling that computes statistics such as null counts, distinct values, and distributions, helping teams understand new datasets quickly during exploration.
• Dataplex does not replace storage or compute engines; BigQuery still runs queries and Cloud Storage still stores files, while Dataplex provides the governance and discovery layer above them.
• Business glossaries and aspects, formerly called entry aspects, enrich catalog entries with business context, ownership, and data classification tags such as sensitivity labels for governance.

What the exam expects you to know

• Choose Dataplex when the scenario is about governing, discovering, cataloging, or ensuring quality of data spread across many buckets and BigQuery datasets in an organization.
• Map the hierarchy correctly: a lake contains zones, zones contain assets, and assets point to actual storage resources like buckets or datasets in projects.
• Know the difference between raw and curated zones and that moving data from raw to curated implies cleaning, formatting, and schema conformance for consumption.
• Recognize automated data quality and profiling as Dataplex capabilities, distinct from building custom Dataflow validation pipelines for every dataset.
• Understand Dataplex is a management plane, not a query engine; questions asking where a SQL query runs should still answer BigQuery, not Dataplex.
• Identify catalog search and governance as the solution for data silos and unknown datasets, a common scenario phrasing in Associate Cloud Engineer questions.

Dataplex vs BigQuery: when to use which

Use Dataplex when your problem is finding, trusting, governing, and monitoring data quality across many storage locations and teams, regardless of where the data physically lives. Use BigQuery when your problem is running fast SQL analytics over large structured datasets in a serverless warehouse. They complement each other: Dataplex catalogs and governs the BigQuery datasets that analysts then query in BigQuery. On the exam, governance, catalog, lake zones, and data quality keywords point to Dataplex, while SQL analytics, joins, and warehousing keywords point to BigQuery. See also the BigQuery notes.

Useful gcloud commands

gcloud dataplex lakes create my-lake --location=us-central1 --description=GovernanceLake
gcloud dataplex zones create raw-zone --lake=my-lake --location=us-central1 --type=RAW --resource-spec-location-type=SINGLE_REGION
gcloud dataplex assets create my-asset --lake=my-lake --zone=raw-zone --location=us-central1 --resource-spec-type=STORAGE_BUCKET --resource-spec-name=projects/my-project/buckets/my-bucket

Common exam traps

• Dataplex is not a storage service and does not hold your data itself; assets remain in Cloud Storage or BigQuery and Dataplex only manages and describes them.
• Creating a lake does not move or copy data automatically; you attach existing buckets and datasets as assets and Dataplex begins discovery and governance from there.
• Dataplex is not the same as Dataproc; Dataproc runs Spark and Hadoop clusters for processing, while Dataplex governs data across the platform.
• A curated zone implies trusted, conformed data, so placing raw unprocessed files directly for business consumption contradicts the raw-to-curated model the exam expects.

Frequently asked questions

What is a Dataplex lake?

A Dataplex lake is a logical grouping representing a business or data domain, such as finance or marketing, that contains zones and assets across projects and storage services. It is an organizational and governance construct, not a physical storage location. Lakes let central teams apply consistent discovery, security, and quality policies to all data in that domain.

How does Dataplex help with data quality?

Dataplex lets you define data quality rules and run them as scheduled tasks against tables and files, checking for nulls, duplicates, ranges, and custom conditions. Results are published to BigQuery and surfaced in the catalog so consumers can see whether a dataset passed its checks. This replaces ad hoc manual validation with a managed, repeatable governance process.

Does Dataplex replace Data Catalog?

Dataplex has evolved to incorporate the data catalog experience, with Dataplex Catalog providing search, metadata, glossaries, and lineage for data assets across Google Cloud. Older Data Catalog concepts map into the new unified catalog model. For the exam, treat catalog and discovery questions in a governance context as Dataplex responsibilities rather than a separate standalone product.

Study aid disclaimer: Cloud Cert Notes is an independent educational study aid. It is not affiliated with, endorsed by, or sponsored by Google, Microsoft, Amazon, Oracle, or Alibaba. Google Cloud, Associate Cloud Engineer, and Cloud Digital Leader are trademarks of Google LLC; all other certification names and product names are trademarks of their respective owners. Always confirm service details against the official provider documentation before sitting an exam.