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.
An enterprise data lake integrates Google Cloud Storage and BigQuery data assets governed by Dataplex. A data engineer needs to enforce row-level security on a centralized transactions table so regional analysts can only view data corresponding to their assigned region.
A junior administrator recommends granting the Filtered Data Viewer (roles/bigquery.filteredDataViewer) IAM role directly to the regional analyst user groups at the BigQuery dataset level, and then executing CREATE ROW ACCESS POLICY DDL statements for each region.
Why does this approach violate Google Cloud security best practices, and what is the correct implementation?
BigQuery Admin role to regional groups and use CREATE OR REPLACE ROW ACCESS POLICY to rotate access.CREATE OR REPLACE DoThe BigQuery Admin (roles/bigquery.admin) role grants full administrative permissions over all BigQuery resources in a project or dataset. CREATE OR REPLACE modifies existing SQL DDL objects.
BigQuery Admin to regular regional sales analysts gives them the power to delete datasets, create tables, alter security policies, and bypass row filters.CREATE OR REPLACE on the last remaining policy on a table can momentarily expose unfiltered data to a wider-than-intended audience.CREATE OR REPLACE when modifying the last active policy.You were provisioning permissions for data platform administrators tasked with managing metadata definitions and security schemas.
Filtered Data Viewer at the dataset level blocks BigQuery table pruning; principals must instead be granted BigQuery Data Viewer at the dataset level and assigned negative IAM condition tags.This option suggests granting the standard BigQuery Data Viewer (roles/bigquery.dataViewer) role at the dataset level and using negative IAM condition tags (e.g., evaluating when a tag is not present) to restrict regional data.
You were controlling table-level or dataset-level access policies based on organizational resource taxonomy tags rather than filtering internal table rows.
Filtered Data Viewer role requires uniform bucket-level access on Cloud Storage; you should instead configure fine-grained object ACLs on Cloud Storage and sync permissions using Dataplex.Cloud Storage supports Uniform Bucket-Level Access (which unifies permissions under IAM) and legacy Fine-Grained Access Controls (which allow per-object Access Control Lists).
Filtered Data Viewer role operate independently of Cloud Storage object ACLs.You were securing unstructured data directly in standalone Cloud Storage buckets outside of Dataplex without using BigLake or BigQuery SQL governance.
Filtered Data Viewer via IAM at the dataset level allows principals to view rows permitted by all row-level policies in that dataset; principals must only be granted access by listing them directly within each DDL CREATE ROW ACCESS POLICY statement.Filtered Data Viewer Role IsThe Filtered Data Viewer (roles/bigquery.filteredDataViewer) is a specialized, system-managed role in BigQuery designed strictly for row-level security access control. When a row access policy is created on a table, BigQuery automatically and implicitly grants this role to the principals specified in the policy definition.
Granting the role manually through IAM at the dataset or project level is a major security anti-pattern because it circumvents row filter scoping, allowing grantees to query data permitted across any row access policy in that resource scope. The optimal and supported method is to manage grantees strictly through SQL DDL CREATE ROW ACCESS POLICY ... ON table_name GRANT TO ('group:...') FILTER USING (...) statements.
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