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.
A financial enterprise uses Google Cloud to store sensitive transactional records in a centralized BigQuery dataset. The organization plans to share specific aggregated metrics and filtered record subsets with external partner organizations through BigQuery Analytics Hub while enforcing strict governance and least-privilege access.
The security architecture must satisfy the following requirements:
Which combination of Identity and Access Management (IAM) and BigQuery governance mechanisms should you implement?
This architecture leverages BigQuery Analytics Hub combined with native BigQuery security primitives—specifically authorized views, row-level security (RLS), and column-level policy tags with dynamic data masking—to distribute governed data without exposing raw underlying storage.
row_access_policies) partition visibility by partner_tenant_id at query runtime.roles/bigquery.dataViewer) role and subscription permissions on the Analytics Hub listing allows them to discover the listing and provision a linked dataset inside their own project without granting IAM access to the provider's upstream datasets.This pattern adheres to Google Cloud security best practices by combining resource-level IAM boundaries with granular database engine security (column masking and row-level filtering). It prevents data replication drift while securing sensitive multi-tenant financial data under strict perimeter controls.
This configuration assigns elevated project-wide administrative privileges (BigQuery Admin or roles/bigquery.admin) to partner identities and exposes raw files using external BigQuery tables configured on Cloud Storage buckets.
roles/bigquery.admin grants broad permissions to modify, delete, or reconfigure all BigQuery datasets, tables, routines, and jobs across the publisher's project.bigquery.*) across the entire source Google Cloud project.This pattern would only be suitable for internal infrastructure administrators who require full management capabilities over BigQuery data warehouses and batch pipeline ingestion pipelines within an isolated non-production environment.
This proposal assigns the BigQuery Data Owner (roles/bigquery.dataOwner) role to external subscriber accounts and attempts to use Dataplex auto data quality scans to redact confidential fields during queries.
roles/bigquery.dataOwner compromises dataset ownership and security governance.This pattern would be relevant if designated internal data stewards needed full administrative ownership to manage dataset lifecycles and schedule quality monitoring checks across enterprise data lakes.
This approach grants the BigQuery Data Editor (roles/bigquery.dataEditor) role directly to external partners on the raw transactional dataset while using permissive VPC Service Controls ingress/egress rules to bridge communications.
roles/bigquery.dataEditor provides write and table modification permissions, violating read-only sharing requirements.This approach would be appropriate for internal ETL service accounts or operational microservices that must continuously write and update operational data within the same security domain.
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