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.
You are conducting a stakeholder and user-centric analysis for an enterprise migrating its legacy data warehouse to Google Cloud. Through your analysis, you have documented the following requirements and constraints:
How should you design the initial phase of the migration to satisfy these stakeholder requirements?
Federated querying allows a data warehouse engine (like BigQuery) to query data stored in external systems (such as Cloud SQL, Cloud Storage, or external databases) without actually moving or copying the data into the warehouse's native storage.
The stakeholders required real-time access to operational data that could not be moved due to strict data residency or compliance constraints, and they were willing to accept degraded query performance.
A full migration strategy involves moving an entire vertical slice of a data architecture to the cloud simultaneously. This means the upstream data pipelines (extract and transform), the storage layer (schema and data), and the downstream consumers (dashboards and apps) are all migrated before the legacy system is deprecated.
The scenario stated that the data engineering team had immediate capacity to rebuild the pipelines, or if the legacy data warehouse hardware was failing and needed to be immediately decommissioned across all layers.
An Extract, Load, and Transform (ELT) pattern changes the data processing paradigm. Instead of transforming data in an external tool before loading it (ETL), raw data is loaded directly into the target data warehouse (BigQuery), and transformations are executed using the warehouse's native SQL compute engine.
The primary stakeholder requirement was to modernize the data architecture to reduce reliance on external ETL tools, and the organization had allocated the necessary time and engineering resources to execute a complete pipeline rewrite.
Offloading a use case is an iterative migration strategy where downstream consumption (like querying and reporting) is moved to the new cloud data warehouse first, while the upstream data ingestion and transformation pipelines remain temporarily anchored to the legacy system. Data is synchronized between the legacy system and the new environment to keep it fresh.
When stakeholder needs conflict—such as the business demanding immediate performance while engineering requires time to rebuild pipelines—an iterative offloading approach is the only way to satisfy both parties. It bridges the gap between current technological constraints and desired user workflows.
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