professional-cloud-data-engineer
Prepare and test your skills
Prepare and test your skills
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 retail analytics platform stores multi-terabyte transactional order data in Google Cloud BigQuery. Historical workload analysis reveals two primary query patterns:
order_date, with selective filtering on customer_id and store_id.COUNT and SUM of sales_amount) grouped by order_date, store_id, and product_category throughout the business day, causing slot contention.The base table is configured with daily partition expiration to automatically purge data older than two years. You need to design a storage and query acceleration architecture that optimizes query pruning, accelerates dashboard rendering, minimizes slot consumption, and ensures analytical caches do not get completely invalidated when base table partitions expire.
Which architecture should you implement?
This architecture combines table partitioning, multi-column clustering, and an aligned partitioned materialized view in BigQuery to optimize both granular ad-hoc filtering and recurring aggregate dashboard queries while preserving compute resources.
order_date allows BigQuery to prune unneeded partitions during scans. Clustering by customer_id and store_id sorts the data blocks within each partition, allowing fine-grained block skipping during selective filtering.COUNT and SUM aggregations grouped by order_date, store_id, and product_category. When dashboards run, BigQuery uses smart tuning and incremental delta computation to serve results from precomputed storage rather than scanning raw base tables, drastically reducing slot consumption.order_date, the materialized view partitions align synchronously with base table partitions. When a base table partition expires, only that specific partition is dropped in the view, avoiding full view cache invalidation and expensive full refreshes.customer_id.This design targets both access tiers: selective base table scans benefit from partition pruning and clustering block-skipping, while repeated dashboard aggregations leverage zero-maintenance, partitioned materialized views.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.