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 runs a central analytics warehouse in BigQuery with predictable, 24/7 business intelligence queries and continuous data transformations across multiple departments. The company stores 600 TB of uncompressed data that achieves a high compression ratio in BigQuery columnar storage, with minimal daily table modifications or data overwrites.
The chief financial officer (CFO) requires predictable monthly compute expenses and wants to minimize the overall total cost of ownership (TCO) for both query compute and storage.
Which combination of BigQuery compute and storage billing models should the data engineering team implement?
This configuration uses BigQuery on-demand compute pricing (charging per TiB of data scanned by queries) regulated by administrative custom query quotas, alongside the physical storage billing model.
The organization ran infrequent, bursty, or unpredictable ad hoc queries where slots would sit idle most of the day, making slot commitments economically inefficient.
While configuring physical storage billing is appropriate for highly compressed data, pairing it with on-demand compute fails the CFO's requirement for financial predictability in high-throughput enterprise pipelines.
This solution pairs BigQuery capacity-based compute pricing (using slot reservations and optional commitments) with the physical (compressed) storage billing model at the dataset level to provide cost predictability and optimize total storage expenditure.
Steady-state 24/7 analytical workloads suffer from unbounded cost volatility and high unit costs under on-demand scanning models. Similarly, highly compressible data with low mutation rates is financially penalized under logical storage billing. Choosing capacity reservations alongside physical storage delivers both maximum cost governance and lowest overall TCO.
This option couples capacity-based compute reservations with BigQuery's default logical storage billing model, which bills storage based on uncompressed data volume.
The workload involved high-frequency updates, large partition overwrites, or massive daily churn that generated large volumes of time travel and fail-safe physical data exceeding the cost benefit of physical compression savings.
Capacity-based compute satisfies the predictability requirement, but leaving storage on the logical model leaves significant cost savings unrealized for compressible, low-mutation analytical warehouses.
This approach relies on default BigQuery settings: on-demand compute billing (metered per TiB scanned) with daily quota limits, combined with default logical storage billing (metered on uncompressed data volume).
The workload consisted of low-volume, highly sporadic querying on small, uncompressed datasets where slot commitments and billing configuration changes would introduce unnecessary administrative overhead.
Using default on-demand compute and logical storage across high-throughput enterprise workloads is one of the most common causes of cost overruns and budget volatility in BigQuery deployments.
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