Bigquery Schema Evolution Facade Views Compatibility

Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.

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?

Execute procedural DDL scripts during off-peak maintenance windows to alter base table columns and force schema updates directly.

Re-architect the data pipelines into an Extract-Transform-Load (ETL) pattern outside of BigQuery to transform data prior to ingestion.

Migrate all downstream BI consumers back to querying the legacy on-premises warehouse until physical BigQuery table refactoring is complete.

Create facade views in BigQuery on top of the underlying physical tables to abstract structural changes from downstream consumers.

Professional Cloud Data Engineer

Bigquery Schema Evolution Facade Views Compatibility

Related questions