GCP Professional Data Engineer Practice Question

Your company publishes a BigQuery dataset through Analytics Hub. It contains the table customer_orders with a column market_segment (STRING). Subscribers belong to two Google Groups: [email protected] should only see rows where market_segment = "EU", whereas [email protected] must see every row. You want to share a single table, avoid duplicating data, and ensure that the correct rows are always filtered, even as new data is appended. What should you do?

  • Partition customer_orders by market_segment and grant partition-level IAM permissions to each group so that analysts can read only the EU partition.

  • Attach two row-level access policies to customer_orders: one that grants [email protected] access with FILTER USING (market_segment = "EU") and another that grants [email protected] access with FILTER USING (TRUE). Then publish the dataset.

  • Create a materialized view that filters market_segment = "EU" for the analysts group and share that view, while granting auditors direct access to the base table.

  • Copy customer_orders into two separate datasets, restrict each dataset with IAM so the analysts group sees the filtered copy and the auditors group sees the full copy, and publish two listings.

GCP Professional Data Engineer
Preparing and using data for analysis
Your Score:
Settings & Objectives
Random Mixed
Questions are selected randomly from all chosen topics, with a preference for those you haven’t seen before. You may see several questions from the same objective or domain in a row.
Rotate by Objective
Questions cycle through each objective or domain in turn, helping you avoid long streaks of questions from the same area. You may see some repeat questions, but the distribution will be more balanced across topics.

Check or uncheck an objective to set which questions you will receive.

Bash, the Crucial Exams Chat Bot
AI Bot