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 stores customer transaction data in a centralized BigQuery table named sales.transactions. You need to securely share this table with three distinct user groups while enforcing the principle of least privilege:
region = 'EMEA', and payment identifiers must be masked.How should you configure access controls and data policies in Google Cloud to achieve these requirements?
This solution combines BigQuery Column-Level Access Control, Dynamic Data Masking (DDM) via Data Catalog policy tags, and Row-Level Security (RLS) to enforce multi-layered, fine-grained access controls.
roles/datacatalog.categoryFineGrainedReader) role on the taxonomy policy tag allows auditors to read the unmasked cleartext data in the tagged column across all rows.roles/bigquery.maskedReader) role allows their queries to execute normally while dynamically returning obscured/masked values.CREATE ROW ACCESS POLICY ... FILTER USING (region = 'EMEA')) restricts the returned rows to EMEA, while the assigned BigQuery Masked Reader role ensures that the payment identifier column in those permitted rows remains masked.This approach avoids data duplication, eliminates maintenance overhead associated with managing separate localized views or export tables, and natively enforces fine-grained authorization using standard Google Cloud IAM and BigQuery DDL policies.
This option grants broad administrative privileges to auditors, constructs an authorized materialized view for analysts, and attempts to apply IAM conditions to filter table rows.
roles/bigquery.admin gives full administrative control over all BigQuery resources in the project, far exceeding the read-only requirement of Finance Auditors.region = 'EMEA') within BigQuery tables.CREATE ROW ACCESS POLICY).Auditors needed full administrative access to manage project datasets and schemas, and data segregation was handled entirely by physical table separation rather than granular row/column rules.
This option uses a Dataflow pipeline and Sensitive Data Protection (Cloud DLP) to permanently tokenize sensitive columns prior to storing them in BigQuery, requiring users to hold decryption key access in Cloud KMS to unwrap ciphertext.
EMEA region.Strict compliance mandates required that data be cryptographically protected at rest such that the storage layer and hosting provider never store cleartext identifiers.
This option relies on creating distinct authorized views in separate datasets, manually embedding SQL expressions (such as SHA256() or fixed redact strings) to obscure columns and appending SQL WHERE clauses to filter rows.
You needed to share an aggregated or heavily transformed slice of data across disparate departments where granular column/row-level engine primitives were not applicable.
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