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 analytics team maintains an interactive executive dashboard that frequently executes heavy aggregate calculations across a multi-terabyte transactional table in BigQuery. The table continuously receives new streaming appends throughout the day, and dashboard users are experiencing slow query performance and high computational costs from repeated aggregate calculations.
The team needs to reduce query latency and computational load by precalculating common aggregations while ensuring queries automatically serve real-time, consistent data without requiring any modifications to the dashboard SQL queries.
Which strategy should the team implement?
A scheduled query in BigQuery uses the BigQuery Data Transfer Service to run batch SQL statements on a recurring schedule (e.g., hourly or daily), writing precalculated aggregate results into a separate destination summary table.
The dashboard only needed historical or end-of-day reporting, where data staleness is acceptable, and where downstream queries could be manually pointed to a dedicated static aggregate table.
BigQuery external tables allow users to query data stored directly in Cloud Storage files (such as Parquet, ORC, or CSV) using external object metadata and Hive partitioning layouts without loading the data into native BigQuery storage.
The primary requirement was long-term cold storage cost optimization in an open data lake format where query speed and real-time dashboard responsiveness were not critical.
A BigQuery materialized view is a precomputed view that periodically or incrementally evaluates and stores the results of a query definition for improved performance and efficiency. Unlike standard virtual views, materialized views persist precalculated results—such as aggregated metrics, filters, and complex joins—directly in BigQuery storage, avoiding redundant query execution over massive underlying datasets.
Materialized views provide the best balance of precalculated performance gains, real-time consistency on streaming base data, and zero-maintenance transparency for downstream visualization tools.
A standard logical view in BigQuery is a virtual query definition that does not persist precalculated data to disk. Whenever a user or dashboard queries a standard view, BigQuery executes the underlying SQL statement on demand against the base tables.
The goal was simply to centralize shared SQL business logic, enforce column-level security masks, or simplify query syntax without any requirement to improve compute performance or persist precomputed calculations.
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