Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Security Engineer practice bank has 1,343 more like it. Try 10 free: instant score, no account.
A security engineer is configuring column-level security in BigQuery to restrict access to sensitive personal data across an analytical data warehouse. The engineer has completed the following steps:
PII_Taxonomy with a policy tag named High_Sensitivity.High_Sensitivity policy tag.During validation, the engineer discovers that members of the data analytics group can still execute queries and read cleartext data from the tagged columns, even though they were never granted access to the policy tag.
What action must the security engineer take to ensure that column-level access control is actively enforced?
Column-level access control in BigQuery operates through a structured four-step workflow: creating taxonomies and policy tags, associating those policy tags with table column schemas, enabling enforcement on the taxonomy, and assigning appropriate IAM permissions to the policy tags. Policy tags attached to table schemas remain inert metadata until taxonomy enforcement is explicitly turned on.
roles/bigquery.dataViewer) will receive access denied errors at query time for protected columns unless they also hold the Data Catalog Fine-Grained Reader (roles/datacatalog.categoryFineGrainedReaderViewer) role on the specific policy tag.This solution completes the native BigQuery column-level security lifecycle without requiring data replication, architectural redesigns, or the maintenance of custom views.
Row-level access policies (RLS) in BigQuery use DDL filter predicates (such as SESSION_USER()) to restrict which horizontal rows or records a user can view within a table based on user or group identity.
The requirement were to restrict data analysts to seeing only rows corresponding to their specific geographical region or department rather than protecting sensitive column fields across all rows.
Authorized views allow query access to aggregated or filtered data in a view without granting users direct read access to the underlying base tables or source dataset.
The organization needed to share specific aggregated query results or transformed projections with external partners without provisioning policy tag taxonomies or granting underlying dataset permissions.
The BigQuery Data Policy Admin (roles/bigquery.dataPolicyAdmin) role provides administrative privileges to create, update, and delete masking rules and data policies. The CREATE TABLE DDL statement creates new BigQuery tables.
roles/bigquery.dataPolicyAdmin gives analysts administrative control over data policies, which undermines security rather than enforcing read restrictions.CREATE TABLE DDL statement; policy tags must be set via schema JSON definitions, API calls, or console operations.bq CLI (bq update), schema modification in the Google Cloud console, or the tables.patch REST API.A governance administrator needed IAM permissions to manage and delete data masking policies programmatically via the BigQuery Data Policy API.
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