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 maintains a central data lakehouse architecture managed by Dataplex Universal Catalog, consisting of native BigQuery analytical tables and raw semi-structured data residing in Cloud Storage bucket assets. The compliance team requires an automated solution to:
Which configuration strategy should the data engineering team implement to meet these governance requirements?
Dataplex Universal Catalog works in tandem with Sensitive Data Protection (Cloud DLP) and BigLake to deliver unified, automated data discovery, classification, and security enforcement across heterogeneous cloud storage layers.
Standard BigQuery external tables do not support column-level security or dynamic data masking. Upgrading assets to BigLake tables brings first-class governance and masking capabilities to data lakes, unifying the security posture across all data lakehouse assets.
This approach uses Dataproc Metastore to store discovered table schemas and attempts to secure sensitive fields by restricting catalog visibility with conditional bindings on the Dataplex Metadata Reader (roles/dataplex.metadataReader) role.
The primary goal was to prevent specific users from seeing table schemas and metadata definitions inside Dataproc Metastore or Data Catalog search indexes.
This configuration grants broad data read permissions (roles/dataplex.dataReader) across the Dataplex lake, encloses storage within a VPC Service Controls perimeter, and configures Cloud DLP job triggers to publish inspection findings to a Pub/Sub topic for reactive alerting.
roles/dataplex.dataReader at the lake level propagates read permissions to all underlying Cloud Storage buckets and BigQuery datasets, exposing raw PII in plaintext to all analysts.The objective was to establish perimeter network security against data exfiltration while building an asynchronous compliance alerting mechanism via Pub/Sub.
This approach suggests keeping standard external tables in BigQuery while using Dataflow and the Sensitive Data Protection API to physically rewrite files stored in Cloud Storage with format-preserving encryption (FPE), decrypting data by distributing Cloud KMS cryptographic keys to analytical users.
The organization required irreversible, batch-level tokenization or field-level ciphertext stored at rest before loading into third-party downstream platforms outside Google Cloud.
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