hardMultiple ChoiceObjective-mapped
BigQuery Data Masking with Policy Tags
A security engineer needs to protect sensitive data in BigQuery. The data includes columns with personally identifiable information (PII). They want to automatically mask PII data for users with the role 'analyst' but allow full access for 'admin' users. Which approach should they use?
Quick Answer
The answer is to apply policy tags with data masking policies to PII columns and assign the tag to the analyst role. This approach is correct because BigQuery’s data masking with policy tags allows you to define column-level security rules that automatically mask sensitive data at query time based on a user’s role, without altering the underlying table. By attaching a masking policy to a policy tag and then applying that tag to PII columns, you ensure that users with the ‘analyst’ role see masked data, while ‘admin’ users—who typically have higher-level IAM permissions like BigQuery Data Owner—see the full data by default. On the Google Professional Cloud Security Engineer exam, this scenario tests your understanding of how BigQuery’s fine-grained access control differs from simple IAM roles; a common trap is to confuse policy tags with classification labels or to assume masking requires separate views. Remember the key distinction: policy tags enforce masking, while IAM roles grant access to the tag itself. Memory tip: “Tag it, mask it, role it”—policy tags define the mask, and the role determines who sees through it.
⚠ Common exam trap
Google Cloud often tests the distinction between column-level access control (which can only hide or deny columns) and data masking (which can partially obscure data while still allowing access), leading candidates to mistakenly choose option C.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Apply policy tags with data masking policies to PII columns and assign the tag to the analyst role.
BigQuery's policy tags with data masking policies allow you to automatically mask sensitive columns (e.g., PII) at query time based on the user's role. You assign a masking policy to the policy tag, then attach that tag to the PII columns. By granting the 'analyst' role access to the tag with the masking rule applied, analysts see masked data, while 'admin' users (who have higher-level IAM permissions) see the full data without additional configuration.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Use VPC Service Controls to restrict access to the dataset.
Why it's wrong here
VPC Service Controls do not provide data masking capabilities.
- ✗
Create authorized views that exclude PII columns for the analyst role.
Why it's wrong here
Authorized views require creating separate views and do not automatically mask data.
- ✗
Use column-level access control via IAM roles to deny access to PII columns for analysts.
Why it's wrong here
Column-level access control only grants or denies access entirely, not masking.
- ✓
Apply policy tags with data masking policies to PII columns and assign the tag to the analyst role.
Why this is correct
Policy tags with masking policies can dynamically mask data based on user's role.
Go deeper
Related to this question
About these practice questions
This PCSE question is part of Courseiva's 960-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →
Same concept, more angles
1 more way this is tested on PCSE
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A company uses BigQuery to store sensitive data and wants to implement data masking using policy tags. They have three user groups: data_engineers (full access), data_analysts (masked PII), and data_scientists (masked financial data). Which THREE steps should they take?
hard- ✓ A.Publish the taxonomy to make the policy tags available for use.
- ✓ B.Create a taxonomy in Cloud Data Catalog with policy tags for PII and financial data.
- C.Apply only one policy tag per column.
- D.Enable Cloud Audit Logs to track policy tag usage.
- ✓ E.Define data masking rules using BigQuery's conditional access on the policy tags.
Why A: After creating a taxonomy with policy tags in Cloud Data Catalog, you must publish the taxonomy to make those policy tags available for use in BigQuery. Publishing associates the taxonomy with the project and allows BigQuery to enforce data masking rules based on the policy tags applied to columns.
JA
Written by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
This PCSE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCSE exam.