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 enterprise data warehouse in BigQuery contains sensitive customer records stored in a base dataset named customer_master. A data analytics and visualization team needs to query aggregated summary metrics using a business intelligence (BI) dashboard without being granted direct read access to the underlying raw tables in customer_master.
You need to implement a secure, least-privilege architecture using BigQuery native controls that allows the BI team and their visualization tool to run these queries successfully.
Which combination of steps should you perform?
customer_analytics. Authorize the view to access the customer_master dataset. Grant the BI team the roles/bigquery.user role on the project and the roles/bigquery.dataViewer role on the customer_analytics dataset.BigQuery Authorized Views allow data administrators to share query results and aggregated subsets of data with specific principals or visualization tools without providing them direct access to the underlying source tables or datasets. Security is maintained through Google Cloud's Identity and Access Management (IAM) and BigQuery's dataset authorization framework.
customer_analytics) and granting the view authorization on the source dataset (customer_master) allows BigQuery to read base table data on behalf of the authorized view. The analysts never receive permissions on customer_master.roles/bigquery.user role at the project level gives analysts the necessary bigquery.jobs.create permission to execute interactive queries and run reporting jobs.roles/bigquery.dataViewer on the customer_analytics dataset (or directly on the view) enables analysts and BI connectors to read the view definition and its query output without exposing raw source tables.This approach adheres strictly to the principle of least privilege. The data analysts can execute queries and view authorized output, but cannot view, query, or enumerate raw records in the source dataset.
customer_analytics. Authorize the view to access customer_master. Grant the BI team the roles/bigquery.dataViewer role on both customer_master and customer_analytics.This option creates an authorized view in an external dataset but grants the roles/bigquery.dataViewer role across both the base dataset and the view dataset, while omitting project-level job creation permissions.
roles/bigquery.dataViewer on customer_master allows members of the BI team to directly query and inspect sensitive base tables, defeating the purpose of creating an authorized view.roles/bigquery.user or roles/bigquery.jobUser, meaning they lack the bigquery.jobs.create permission required to submit queries or drive visualization dashboards.roles/bigquery.dataViewer) do not grant compute/job execution permissions in BigQuery.This would only work if queries were always submitted through a third-party service account executing jobs in a different project, but it would still unnecessarily over-grant access to customer_master.
customer_master dataset. Grant the BI team the roles/bigquery.dataViewer role on customer_master and the roles/bigquery.jobUser role on the project.This configuration creates a standard logical view within the same dataset that holds the raw data (customer_master) and grants dataset-level reader permissions alongside job execution permissions.
roles/bigquery.dataViewer directly on customer_master gives the BI analysts read access to all tables and views within that dataset, completely exposing the raw, sensitive customer records.roles/bigquery.dataViewer on a dataset can execute SELECT * on any base table inside it.This approach would only be appropriate in non-sensitive environments where all analysts are fully trusted to inspect all underlying base tables directly.
customer_analytics. Apply a row access policy on the base tables using GRANT TO ("group:bi-team@example.com") FILTER USING (TRUE). Grant the BI team roles/bigquery.dataOwner on customer_analytics.This option sets a row access policy with a TRUE filter on the source table for the BI team and assigns the administrative roles/bigquery.dataOwner role on the analytics dataset.
FILTER USING (TRUE) explicitly permits the grantee to see every single row of the base table, failing to mask sensitive details unless combined with other complex transforms.roles/bigquery.dataOwner over-privileges the BI team by allowing them to delete datasets, update dataset ACLs, and alter metadata rather than merely reading aggregated metrics.customer_master prevents the view from accessing base table data when unprivileged users query it.TRUE filter in row-level security is intended for administrative or service account bypasses that legitimately require full table access.roles/bigquery.dataOwner violates the principle of least privilege for read-only visualization users.The BI team were data administrators who required full administrative ownership over the analytics dataset and uninhibited access to all underlying rows for data pipeline maintenance.
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