GCP Professional Data Engineer Practice Question

A multinational company keeps all employee records in the BigQuery table hr.employee_raw. A second table, hr.region_map(user_email, country_code), lists which countries each HR analyst is allowed to see. HR analysts must be prevented from viewing rows outside their assigned countries, while the Finance team must retain unrestricted access to every row for global reporting. The engineering team wants to keep a single canonical table and create as few additional objects as possible. Which design should they implement?

  • Attach a row access policy to hr.employee_raw that filters rows by joining to hr.region_map, and grant this policy to the HR analyst group while assigning a separate TRUE policy to Finance users.

  • Apply a Data Catalog policy tag on the country_code column to hide the column from HR analysts, while granting Finance full access to the table.

  • Create a single authorized view that joins hr.employee_raw with hr.region_map filtering rows where hr.region_map.user_email = SESSION_USER(); grant HR analysts access to the view and allow Finance to query the base table.

  • Partition hr.employee_raw by country_code, copy each partition into its own dataset, and grant HR analysts access only to the datasets for their countries while Finance retains access to all datasets.

GCP Professional Data Engineer
Designing data processing systems
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