Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A retail organization is expanding its analytics platform on Google Cloud and faces several data governance challenges:
How should the organization use Knowledge Catalog to address these governance requirements?
In Knowledge Catalog, Identity and Access Management (IAM) permissions are separated into data roles, metadata roles, and lineage roles. The Dataplex Data Reader role (roles/dataplex.dataReader) is a data-level IAM role that grants users read access to both the metadata and the actual underlying data within a managed resource and its children.
roles/dataplex.dataReader gives auditors direct read access to the raw customer records, which directly contradicts the compliance requirement to restrict auditors from viewing sensitive data values.roles/dataplex.dataReader): Includes all permissions of roles/dataplex.metadataReader plus permissions to read the actual data in managed resources.roles/dataplex.metadataReader): Grants read-only access strictly to metadata (such as table schemas) without exposing raw table contents.roles/dataplex.catalogViewer): Allows users to view metadata about an asset entry stored in Knowledge Catalog.roles/datalineage.viewer): Required on both the active project and the compute project where lineage was recorded to view lineage graphs and read from the Data Lineage API.This option would be appropriate if the target users were data scientists or business analysts who required direct read access to query both the raw data rows and the metadata across resources managed by Knowledge Catalog.
Effective data governance relies on separating metadata access from data access. By combining roles/datalineage.viewer and roles/dataplex.catalogViewer (or roles/dataplex.metadataReader), organizations empower users to discover assets and audit data flows while keeping sensitive payloads locked down.
Data lineage in Knowledge Catalog (formerly Dataplex Universal Catalog) is a governance and metadata management capability that provides a visual map tracking the complete lifecycle of data across an organization. By enabling the Data Lineage API, supported Google Cloud services—such as BigQuery, Dataflow, and Vertex AI—automatically report lineage metadata whenever data is moved or transformed.
Implementing automated data lineage in Knowledge Catalog directly establishes transparency, accountability, and asset discoverability across the data lifecycle. Unlike manual documentation or raw data auditing, automated lineage continuously updates visual dependency graphs using metadata, ensuring reliable change management and regulatory compliance at scale.
In Knowledge Catalog, data lineage is strictly a metadata tracking mechanism that records relationships between source assets, transformation processes, and target assets. While collected lineage information is retained in the system for 30 days, it only stores structural and operational metadata about data movement—never copies of the raw data records themselves.
fullyQualifiedName), processes (transformation definitions like SQL queries), runs (execution timestamps and states), and events (directional links).This approach would be conceptually relevant if the organization needed to recover accidentally deleted rows from a table within a recent window using a storage feature like BigQuery time travel or table snapshots, and if auditors were explicitly authorized to inspect raw customer records.
A common misconception in data governance is confusing metadata management with data backup. Metadata describes the properties, schema, origin, and movement of data ("data about data"), enabling discovery and compliance auditing without duplicating sensitive business payloads.
The Data Lineage API supports ingesting custom lineage events formatted according to the OpenLineage standard. This capability is designed to record lineage information for external systems, third-party databases, or on-premises pipelines that are not natively integrated with Google Cloud's automated lineage tracking.
CREATE TABLE, INSERT, UPDATE, MERGE, and SELECT queries) without manual intervention.fullyQualifiedName to custom catalog entries and are restricted to table-level lineage only.This approach would be the right choice if the organization needed to track table-level lineage for data transformations occurring in external, non-Google Cloud databases or on-premises ETL pipelines that already emit OpenLineage events.
When planning a data governance strategy on Google Cloud, organizations should rely on automated data lineage for native cloud services like BigQuery and Vertex AI to minimize operational burden and retain column-level visibility, reserving custom API ingestion for external hybrid or multi-cloud data sources.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated