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 maintains a central BigQuery dataset named source_sales in project corp-analytics-prod that contains detailed order information and customer personally identifiable information (PII). You need to publish a collection of curated analytical views that exclude sensitive PII to an external analytics partner group (partner-analysts@partner.com).
The implementation must satisfy the following requirements:
source_sales directly.source_sales without individual view authorization.Which configuration should you implement?
This approach attempts to share data across disparate regions by configuring individual authorized views while granting administrative privileges (roles/bigquery.admin) to the partner analyst group on the query project.
roles/bigquery.admin role grants complete administrative control over all BigQuery resources within the project, which is excessive for users who only need to run queries.roles/bigquery.admin exposes project administrative settings and dataset deletion privileges.This approach would only be relevant if the external group required full administrative control over their destination project and each view needed unique, isolated access control across distinct base tables within the same region.
This method keeps all views inside the primary source dataset and relies on dataset-level roles/bigquery.dataViewer along with row access policies on the source tables to regulate data visibility.
roles/bigquery.dataViewer at the source_sales dataset level allows the partner group to discover and read all existing tables and views within source_sales, violating the requirement to prevent direct access to underlying source data.bigquery.jobs.create), which prevents them from executing queries unless granted at the project level.dataViewer grants broad read permissions across all tables in that dataset.This pattern would be appropriate if internal users needed direct access to query the primary dataset while having their row visibility restricted dynamically by department or tenant identifier.
An authorized dataset allows all views (both existing and future) within a designated dataset to access data from a shared source dataset without needing separate authorizations for each view. Combining this with granular Identity and Access Management (IAM) roles enables secure, least-privilege data sharing with external or internal consumers.
source_sales: The partner analysts are not granted any IAM roles on the source_sales dataset or its tables. Because partner_views is configured as an authorized dataset on source_sales, BigQuery verifies authorization at the dataset boundary, keeping the underlying source tables completely shielded from the analysts.partner_views dataset on source_sales automatically grants access to all views defined within it, eliminating the operational overhead of authorizing individual views.roles/bigquery.user at the project level provides the necessary bigquery.jobs.create permission to run query jobs, while granting roles/bigquery.dataViewer strictly at the partner_views dataset level limits view/read access exclusively to the curated dataset.This architecture establishes a clean separation between data ownership and consumption. It minimizes administrative complexity compared to individual authorized views, strictly isolates base tables containing PII, and applies minimal required IAM permissions across project and dataset boundaries.
This strategy grants read access directly on the source_sales dataset while relying on policy tags and dynamic data masking in Data Catalog/Dataplex to mask sensitive PII values when queries are run.
roles/bigquery.dataViewer on source_sales gives the partner group direct access to query the base tables, directly violating the requirement to prevent analysts from querying source tables directly.source_sales to external users.roles/bigquery.user or roles/bigquery.jobUser on their project to execute query jobs; dataset permissions alone are insufficient.This design would be suitable if the external analysts were permitted to query the underlying base tables directly but needed specific columns (like credit card numbers or email addresses) dynamically masked at runtime based on IAM policy tags.
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