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 architecting a multi-tiered data storage and analytics platform on Google Cloud to handle hundreds of terabytes of transactional log data. The solution must satisfy the following architectural requirements:
customer_id, store_id, and product_category.Which multi-tiered storage and processing architecture should you implement?
customer_id and clustering by event timestamp. Create BigQuery standard (logical) views to serve executive dashboard aggregations.This approach relies on keeping all raw files permanently in Cloud Storage Standard and querying them on demand using BigQuery external tables with standard logical views.
customer_id exceeds BigQuery table partitioning limits and degrades query performance.This design would only be appropriate for one-time, ad hoc exploration of external data where storage cost is not a factor and data volumes are too low to justify native ingestion.
customer_id and clustered by event timestamp, and use scheduled queries to refresh a summary aggregation table every 5 minutes.This configuration attempts to land all incoming streaming/batch data immediately into Cloud Storage Archive class and uses BigLake external tables alongside a scheduled query pipeline targeting a custom partition schema.
customer_id is an anti-pattern due to cardinality constraints; partitioning in BigQuery must be configured on date/timestamp, ingestion time, or integer ranges.This approach would only be valid if the logs were static compliance dumps that would never be processed or accessed except during disaster recovery audits.
customer_id, and build BigQuery BI Engine SQL views for real-time aggregation.This option relies exclusively on BigQuery as the raw ingestion sink, using manual yearly extract jobs to move data to Cloud Storage Standard and querying an unpartitioned table with BI Engine.
This pattern would be suitable for a small-scale application with low data volume where all historical records are frequently queried and automated tiering is unnecessary.
customer_id, store_id, and product_category. Create BigQuery Materialized Views for executive summary metrics.This architecture establishes an end-to-end multi-tiered storage strategy by integrating Cloud Storage for scalable, tiered data lifecycle management with BigQuery native storage optimized through date partitioning, multi-column clustering, and materialized views.
customer_id, store_id, and product_category (up to four columns) collocates related data into organized storage blocks, dramatically improving filter and aggregation performance.This architecture pairs the ideal services for each access pattern: Cloud Storage provides unbounded, tiered, cost-effective object storage, while BigQuery native tables with partitioning, clustering, and materialized views deliver maximum query performance and minimal query execution overhead.
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