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.
A gaming enterprise is architecting the data storage layer for a high-throughput telemetry ingestion pipeline on Google Cloud. The system must support two distinct downstream operational access patterns:
Which storage combination should the team select to serve as the optimal sinks for these workloads?
This configuration suggests using Cloud Pub/Sub to persist and look up real-time session states and Cloud Spanner as the historical analytical data warehouse sink.
Workload 1 was an asynchronous ingestion buffer between producers and consumers, and Workload 2 required globally consistent transactional reads and writes with relational semantics.
Pub/Sub is an entry point / messaging source and sink, not a persistent random-access database.
Cloud Bigtable is a sparsely populated, fully managed NoSQL database optimized for massive operational scale, low latency, and single-row key-based access patterns. BigQuery is a serverless, highly scalable enterprise data warehouse built on a columnar storage architecture (Capacitor) and decoupled compute infrastructure (Dremel).
Choosing Bigtable for key-value point access and BigQuery for analytical columnar aggregations aligns each workload with its optimized engine architecture, ensuring low latency for operations and cost-effective performance for big data analytics.
This option proposes using Cloud SQL relational database instances with read replicas for session states, and Cloud Bigtable as the analytical aggregation engine for petabyte-scale historical logs.
Workload 1 required strict relational schema constraints and multi-row ACID transactions with moderate throughput, while Workload 2 was restricted to simple time-series key-range scans.
Using Bigtable as a general-purpose enterprise data warehouse leads to complex, custom application logic and high operational overhead.
This option suggests using BigQuery for transactional, sub-10 millisecond single-row state lookups and Cloud Storage queried via BigLake external tables for petabyte-scale historical analytics.
The real-time workload required ad hoc analytical aggregations on streaming data rather than sub-10ms key-value point reads, and all historical data needed to be archived strictly in open object-storage file formats.
BigQuery is not an OLTP database and should not be used as an operational key-value store for session management.
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