Prepare and test your skills

Prepare and test your skills

Free sample question, answered and explained below. The Professional Data Engineer practice bank has 1,353 more like it. Try 10 free: instant score, no account.
An enterprise data platform spans multiple Google Cloud projects containing BigQuery tables and multi-terabyte Cloud Storage buckets containing semi-structured JSON and Parquet datasets.
Your data governance team requires a centralized metadata architecture that fulfills the following criteria:
Which architecture should you implement?
This solution relies on generating JSON Lines (NDJSON) metadata files alongside data files in Cloud Storage and using Vertex AI Search (Discovery Engine) to index and query document-level metadata using natural language.
You were building an enterprise search application or retrieval-augmented generation (RAG) system over unstructured internal documents (such as PDF policies, whitepapers, or contracts).
Dataplex Universal Catalog and Data Catalog provide an automated, policy-driven metadata management and discovery service. Dataplex manages distributed data lakes and data zones, automatically extracting technical metadata through Discovery jobs, while Data Catalog provides schematized Tag Templates to capture business and operational metadata across resources like BigQuery, Cloud Storage, and Pub/Sub.
bigquery.tables.get or roles/bigquery.metadataViewer). A user cannot view search results for assets they lack permissions to access. Furthermore, configuring private tag templates restricts the visibility and searchability of sensitive compliance metadata exclusively to principals granted explicit IAM permissions on the template.This architecture leverages fully managed Google Cloud governance services without requiring custom ETL pipelines, third-party metastores, or bespoke metadata synchronization scripts.
This solution uses a Cloud Data Fusion data integration pipeline to read Cloud Storage object metadata, populate an external Dataproc Metastore instance, and apply standard Google Cloud resource labels on the storage buckets for business context.
You only needed infrastructure-level resource grouping for cost allocation and billing attribution via Cloud Billing.
This approach uses event-driven serverless Cloud Functions to detect new file uploads in Cloud Storage, parse schemas programmatically, execute CREATE EXTERNAL TABLE statements in BigQuery, and store governance tags as relational rows inside a custom BigQuery dataset.
tag:) across the Google Cloud Console or Data Catalog API.You needed to build a bespoke, non-standard cataloging system for environments where Dataplex and Data Catalog APIs are strictly prohibited.
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 Validated