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.
Your organization manages a BigQuery dataset containing a customer transactions table with sensitive Personally Identifiable Information (PII), including columns for tax_id, email_address, and credit_card_number. You are preparing this data for enterprise-wide visualization and reporting.
You have the following security and access requirements:
Which solution should you implement?
Customer-Managed Encryption Keys (CMEK) in Google Cloud are typically applied at the resource level (such as an entire BigQuery dataset, table, or Cloud Storage bucket) or used with AEAD encryption functions in SQL to encrypt specific column values at rest.
BigQuery Job User without decryption permissions will cause analytical queries referencing encrypted AEAD columns to fail outright with cryptographic errors, rather than returning usable obfuscated values (such as masked email prefixes or hash strings) for reporting.BYTES data type) that cannot be aggregated, joined, or rendered cleanly in visual dashboards.This design would be appropriate for regulatory mandates requiring dual-authorization cryptographic envelope encryption at the database cell level, where unauthorized users should receive encrypted ciphertext blobs rather than formatted masked data.
Sensitive Data Protection (formerly Cloud DLP) offers automated inspection, tokenization, and de-identification capabilities. A batch job inspects datasets in Cloud Storage or BigQuery, applies cryptographic transformation techniques (such as deterministic pseudonymization or format-preserving encryption with Cloud KMS), and outputs the results to a new destination.
This approach would be correct if data needed application-level tokenization or irreversible anonymization during the ingestion ETL pipeline before landing in non-confidential environments, or if tokenized records needed to be stored outside Google Cloud.
While Cloud DLP and Cloud KMS are essential components of data privacy frameworks, they operate at the data ingestion and storage layers rather than providing real-time, identity-aware column masking inside the BigQuery query execution engine.
SHA256() on sensitive columns. Grant BI Analysts access to the authorized views and grant Compliance Auditors direct access to the underlying base tables.Authorized views in BigQuery allow data administrators to share query results with specific users and groups without giving them direct access to the underlying source tables. SQL logic within the view can filter rows, drop columns, or transform cleartext values using built-in scalar functions such as SHA256() or SUBSTR().
SHA256() in SQL views run unconditionally for anyone querying the view, regardless of fine-grained IAM roles.This approach would be suitable for simple, isolated use cases where an organization does not use Dataplex/Data Catalog policy taxonomies and simply needs to expose a static subset of pre-filtered data to a single external contractor group without granular role-based de-identification.
Dataplex policy tags (managed via the Dataplex taxonomy and Data Catalog catalog services) provide a centralized way to enforce column-level access control and dynamic data masking across BigQuery tables. By defining hierarchical taxonomies and assigning masking rules (such as SHA-256 hashing, default masking values, email masking, or nullification) directly to policy tags, organizations can manage data protection policies independently of the underlying table schemas.
roles/bigquery.maskedReader (or roles/datacatalog.maskedReader) role allows BI analysts to execute queries against the dataset while BigQuery dynamically transforms sensitive column values into masked representations at query runtime.roles/datacatalog.categoryFineGrainedReader role on the specific policy tags. This permission overrides the masking rules and allows authorized identities to view the raw, cleartext values.roles/bigquery.dataViewer on the table but lacks both the Masked Reader and Fine-Grained Reader roles for the attached policy tags, BigQuery rejects queries referencing those protected columns with an access denied error.This approach directly leverages native Google Cloud governance mechanisms in Dataplex and BigQuery. It satisfies all multi-tiered persona requirements (auditors, analysts, and unauthorized users) with zero compute overhead for ETL duplication, unified IAM management, and native integration with visualization tools like Looker Studio.
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