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.
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?
Facade views are logical SQL views created on top of base storage tables in BigQuery that implement the classic facade design pattern. They present a stable, decoupled logical schema to downstream analytical tools while abstracting the underlying physical tables and storage complexity.
Implementing facade views establishes an abstraction boundary between physical storage and downstream consumption interfaces. This directly solves the challenge of evolving warehouse schemas in place while ensuring business continuity for analytics consumers.
This approach directly executes imperative Data Definition Language (DDL) and Data Manipulation Language (DML) scripts against physical BigQuery base tables during scheduled maintenance downtime.
The tables were strictly internal staging tables within an isolated ETL DAG with no direct downstream end-user or business intelligence dependencies.
This option rolls back downstream business intelligence workloads to the source on-premises data warehouse, isolating BigQuery so that table redesign can proceed without live consumer dependencies.
A catastrophic failure occurred during initial migration that necessitated an emergency rollback to legacy systems to restore business operations.
This approach shifts all schema transformations upstream into an external ETL (Extract, Transform, Load) compute layer before loading data into BigQuery, rather than performing ELT (Extract, Load, Transform) within the data warehouse.
The primary architectural goal was to offload intensive data parsing and enrichment from BigQuery storage compute to an external streaming processing framework like Apache Beam.
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