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 an enterprise analytics warehouse in BigQuery containing tables with sensitive personally identifiable information (PII), such as government identification numbers and contact details. You need to implement a scalable, fine-grained access control architecture that enforces column-level security.
The solution must satisfy the following requirements:
Which strategy should you implement?
BigQuery column-level security provides fine-grained access control to sensitive columns using policy tags within a hierarchical taxonomy. This mechanism verifies user access privileges at query time, preventing unauthorized identities from querying, projecting, or viewing sensitive column values while still allowing them to interact with unrestricted columns in the same table.
roles/bigquery.dataViewer) to query the table, but because they lack policy tag permissions, BigQuery blocks them from reading or filtering on protected columns. Compliance officers are granted the Data Catalog Fine-Grained Reader (roles/datacatalog.fineGrainedReader) role on the specific policy tags, allowing them to read raw PII values.bq CLI tool (bq update), or the tables.patch API method.This solution provides native, scalable access control without needing to build and maintain separate views or duplicate pipelines for different user roles. By using hierarchical taxonomies and the Data Catalog Fine-Grained Reader role, access governance remains maintainable and auditable as the data footprint grows.
In BigQuery, primary and foreign key constraints are informational metadata constraints that help the query engine optimize joins, but they are not enforced by BigQuery. Google Cloud Armor and network load balancing authorization policies protect HTTP(S) applications and web endpoints at the perimeter/network layer based on service accounts or resource tags.
You were optimizing complex relational joins between dimension and fact tables in BigQuery, or securing an external HTTP(S) application workload using Cloud Armor security policies.
This option proposes using standard GoogleSQL CREATE TABLE Data Definition Language (DDL) statements to assign policy tags to columns and granting administrative roles to analysts and standard dataset viewer roles to compliance officers.
CREATE TABLE do not support attaching Data Catalog policy tags directly within the column definition (policy tags must be configured via schema JSON updates, bq CLI, the tables.patch API, or the console).CREATE TABLE DDL.roles/datacatalog.categoryAdmin / roles/datacatalog.policyTagAdmin manages taxonomy structures but does not grant data read privileges.This approach would only be partially relevant if managing taxonomy metadata definitions via administrative service accounts rather than managing end-user data query permissions.
Authorized views allow you to share query results with specific users or groups without giving those users direct access to the underlying base tables and datasets.
You needed to share aggregated, static slices of data with external third parties who should have zero access to the underlying dataset and where centralized policy tag taxonomies are not required.
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