A financial services organization is building a decentralized data mesh architecture on Google Cloud. Multiple domain teams need to expose curated analytical data products to downstream business analysts across the enterprise. The enterprise architecture board has defined the following technical and regulatory constraints: Downstream business analysts must query aggregated business metrics and sanitized virtual tables without having direct read permissions to the underlying sensitive base datasets. The security and compliance teams require minimal administrative overhead and must avoid managing individual view authorizations as dozens of new analytical views are published. Data domain infrastructure deployments must prevent configuration drift using infrastructure as code (IaC) templates. Which technical requirement and access pattern should the data engineering team implement to satisfy these business objectives?

Create curated views inside a dedicated dataset and configure that dataset as a BigQuery Authorized Dataset with access to the underlying source dataset, provisioning the resources via Terraform modules.: What BigQuery Authorized Datasets are BigQuery Authorized Datasets allow data product owners to authorize an entire dataset containing multiple views or user-defined functions (UDFs) to access source data stored in a separate, restricted dataset. This enables domain teams to publish virtual consumption interfaces without granting consumers direct access to raw, underlying data. How it meets the requirements Sanitized virtual tables without base table permissions: Analysts are granted read permissions (roles/bigquery.dataViewer) only on the consumption dataset containing the views. When analysts execute queries against these views, the authorization is evaluated via the dataset-level authorization grant, allowing access to the underlying base tables without exposing the underlying base tables directly. Minimal administrative overhead at scale: Authorizing an entire dataset automatically extends authorization to any new view created within that dataset. This eliminates the need to configure and maintain authorization grants for each view individually as new data products are deployed. Immutable infrastructure without configuration drift: Composable Terraform modules allow the platform team to codify the dataset creation, view definitions, and IAM authorization policies into declarative source-controlled templates. Key advantages Decentralized governance: Simplifies consumption interfaces across independent data mesh domains. Scalable authorization: Automatically applies authorization to newly created views without manual intervention. Zero-trust data isolation: Guarantees consumers only see permitted transformations, satisfying strict financial regulatory constraints. IaC reproducibility: Prevents configuration drift and enforces baseline security guardrails during deployment. Why this is optimal Using Authorized Datasets combined with Terraform modules provides the exact abstraction layer required for decentralized data product consumption interfaces while keeping management overhead low and maintaining rigorous access boundaries.

Implement Bigquery Authorized Datasets Data Mesh | Professional Cloud Data Engineer

AdvancedProfessional Cloud Data Engineer

A SaaS organization is redesigning its analytics platform on Google Cloud to handle a projected tenfold increase in tenant onboarding and raw data volume. Currently, ingestion workloads, storage, and customer-facing analytical queries share resources in a monolithic project, leading to severe compute contention, complex schema maintenance, and quota bottlenecks. You need to design a scalable, modular architecture that leverages BigQuery's separation of storage and compute to isolate compute resource allocation across tenant tiers while allowing storage and analytical pipelines to scale independently. Which architectural approach should you recommend?

Mapping current and future business requirements to the architecture

AdvancedProfessional Cloud Data Engineer

An enterprise is modernizing its enterprise data warehouse by migrating workloads to Google Cloud BigQuery. During the migration lifecycle, the data engineering team needs to evolve several core dataset schemas, implement table optimizations such as partitioning and clustering, and restructure underlying tables to support emerging analytics use cases. However, numerous downstream business intelligence (BI) dashboards, reporting applications, and automated query jobs are already actively reading from the existing table structures. The business requires that underlying schema refactoring and performance optimizations occur without causing operational disruption or requiring immediate query rewrites across downstream consumers. Which architectural pattern should the data engineering team implement to satisfy these requirements?

Mapping current and future business requirements to the architecture

AdvancedProfessional Cloud Data Engineer

A media and analytics organization needs to ingest large volumes (over 150 TiB) of raw video assets and recurring batch exports stored across on-premises POSIX file systems into Google Cloud Storage. The organization has an active high-bandwidth Cloud Interconnect connection and requires a solution that: Automates recurring batch synchronization from the on-premises file systems to regional Cloud Storage buckets Scales transfer throughput across available network capacity while minimizing operational maintenance Maintains data integrity by automatically validating checksums between source files and destination objects Which batch transfer solution should the organization implement?

Data acquisition and import

AdvancedProfessional Cloud Data Engineer

An enterprise data analytics team is redesigning their batch processing architecture. Every night, multi-terabyte structured datasets from operational databases and Cloud Storage are ingested, requiring complex multi-table joins and analytical aggregations before being delivered to reporting dashboards in BigQuery. The existing pipeline runs programmatic ETL transformations entirely on Apache Spark within Cloud Dataproc clusters. However, resource-intensive shuffle operations during large-scale joins frequently cause cluster memory bottlenecks and lead to inflated compute costs. Which architectural approach should the team implement to optimize performance and reduce compute costs?

Defining data transformation and orchestration logic

AdvancedProfessional Cloud Data Engineer

A data engineering team is designing a multi-terabyte dataset in BigQuery to support recurring BigQuery ML model training and batch prediction workloads (ML.PREDICT). The workloads have the following operational characteristics: Model training queries regularly filter transactions over sliding time windows based on a transaction_timestamp column. Batch inference queries frequently filter and aggregate features on a high-cardinality customer_id column within specific time windows. Data engineers need upfront query cost estimates before executing training queries to prevent budget overruns. Which table design strategy in BigQuery should the team implement to optimize query performance and minimize data processing costs?

Preparing data for feature engineering, training and serving machine learning models (e.g., BigQueryML)

IntermediateProfessional Cloud Architect

GKE Enterprise Fleets and Config Sync

Flexibility of cloud resources

Professional Cloud Data Engineer

Implement Bigquery Authorized Datasets Data Mesh

Related questions

GKE Enterprise Fleets and Config Sync

Professional Cloud Data Engineer

Implement Bigquery Authorized Datasets Data Mesh

What BigQuery Authorized Datasets are

How it meets the requirements

Key advantages

Why this is optimal

Related questions

GKE Enterprise Fleets and Config Sync

What BigQuery Authorized Datasets are

How it meets the requirements

Key advantages

Why this is optimal