Dataplex And BigQuery Governance
Overview
Use this skill when governance on GCP is centered on Dataplex, BigQuery, and related Google Cloud metadata controls. It helps agents define governance zones, policy-tag boundaries, lineage expectations, and trusted publishing patterns for warehouse and lake platforms.
When to Use
- designing
Dataplex lakes, zones, or governance domains
- defining
BigQuery policy tags and governed publish boundaries
- improving metadata quality, lineage, and discovery on
GCP
- aligning warehouse and lake governance across
Cloud Storage, BigQuery, Dataflow, and Dataproc
- making governed analytics delivery work with regional or regulated-data controls
Do not treat BigQuery governance as only a permissions problem. Trusted publishing also needs metadata, ownership, and policy boundaries.
Workflow
Define the governance boundary.
Decide:
- lakes and zones
- datasets and domains
- producer versus consumer boundaries
- ownership expectations
Define metadata and policy controls.
Include:
- policy tags
- classifications
- lineage coverage
- discovery metadata
- trusted versus exploratory asset signaling
Align lake and warehouse governance.
Make explicit how Cloud Storage, BigQuery, and processing services fit the same control model.
Design governed publish behavior.
Require:
- clear serving boundaries
- ownership visibility
- release or validation evidence where needed
- rules for schema and policy change
Validate day-2 operations.
Review whether onboarding, schema evolution, and new domains remain manageable under the governance model.
Common Rationalizations
| Rationalization |
Reality |
| "Policy tags are the whole governance design." |
Tags help, but they do not replace ownership, zone design, trusted publishing, or metadata quality. |
| "Dataplex is only for lake governance." |
Many teams need a joined governance model across storage, warehouse, and processing surfaces. |
| "Discovery will happen automatically once assets are scanned." |
Useful discovery requires curated metadata and trust signals. |
Red Flags
- lake, dataset, and domain boundaries are inconsistent
- policy tags exist without ownership or publish context
- warehouse and lake governance behave differently with no clear rule
- certification or trusted-asset behavior is missing
- schema and policy changes are operationally unclear
Verification
1---2name: dataplex-and-bigquery-governance3description: Guides agents through GCP-native data governance workflows with Dataplex and BigQuery. Use when designing lakes, zones, policy tags, metadata quality, lineage, discovery, and governed publishing across Cloud Storage, BigQuery, Dataflow, Dataproc, and Google Cloud analytics platforms.4---56# Dataplex And BigQuery Governance78## Overview910Use this skill when governance on `GCP` is centered on `Dataplex`, `BigQuery`, and related Google Cloud metadata controls. It helps agents define governance zones, policy-tag boundaries, lineage expectations, and trusted publishing patterns for warehouse and lake platforms.1112## When to Use1314- designing `Dataplex` lakes, zones, or governance domains15- defining `BigQuery` policy tags and governed publish boundaries16- improving metadata quality, lineage, and discovery on `GCP`17- aligning warehouse and lake governance across `Cloud Storage`, `BigQuery`, `Dataflow`, and `Dataproc`18- making governed analytics delivery work with regional or regulated-data controls1920Do not treat `BigQuery` governance as only a permissions problem. Trusted publishing also needs metadata, ownership, and policy boundaries.2122## Workflow23241. Define the governance boundary.25 Decide:26 - lakes and zones27 - datasets and domains28 - producer versus consumer boundaries29 - ownership expectations30312. Define metadata and policy controls.32 Include:33 - policy tags34 - classifications35 - lineage coverage36 - discovery metadata37 - trusted versus exploratory asset signaling38393. Align lake and warehouse governance.40 Make explicit how `Cloud Storage`, `BigQuery`, and processing services fit the same control model.41424. Design governed publish behavior.43 Require:44 - clear serving boundaries45 - ownership visibility46 - release or validation evidence where needed47 - rules for schema and policy change48495. Validate day-2 operations.50 Review whether onboarding, schema evolution, and new domains remain manageable under the governance model.5152## Common Rationalizations5354| Rationalization | Reality |55| --- | --- |56| "Policy tags are the whole governance design." | Tags help, but they do not replace ownership, zone design, trusted publishing, or metadata quality. |57| "Dataplex is only for lake governance." | Many teams need a joined governance model across storage, warehouse, and processing surfaces. |58| "Discovery will happen automatically once assets are scanned." | Useful discovery requires curated metadata and trust signals. |5960## Red Flags6162- lake, dataset, and domain boundaries are inconsistent63- policy tags exist without ownership or publish context64- warehouse and lake governance behave differently with no clear rule65- certification or trusted-asset behavior is missing66- schema and policy changes are operationally unclear6768## Verification6970- [ ] Governance boundaries are explicit across lake and warehouse surfaces71- [ ] Policy tags, metadata, and lineage expectations are defined72- [ ] Publish behavior is governed and reviewable73- [ ] Ownership and discovery expectations are visible74- [ ] Day-2 operations fit the governance design
Kilo-Org