Home › GCP Data Engineer › cloudcomputing › gcpdestorage › Which BigQuery storage optimisation should a Dat…
Which BigQuery storage optimisation should a Data Engineer apply to a large fact table queried by date range — to scan only matching partitions and reduce cost?
ADisabling indexing globally
BStoring the table as a single partition with no pruning
CCloud DNS
DPartitioning the table by ingestion-time or a DATE/TIMESTAMP column
Answer & Solution
Correct answer: D. Partitioning the table by ingestion-time or a DATE/TIMESTAMP column
Date partitioning enables partition pruning (per PDE §3.2). The other options don't reduce scan cost.
Related questions
Which BigQuery feature lets a Data Engineer SHARE a curated table or view with EXTERNAL orWhich GCP service is the unified data-fabric for governance + discovery + lineage across BWhich Cloud Storage feature should a Data Engineer use to automatically move blobs older tWhich BigQuery storage optimisation should a Data Engineer apply IN ADDITION to partitioniWhich GCP service should a Data Engineer choose as an in-memory cache (Redis or Memcached)Which GCP service should a Data Engineer choose as a serverless document database with reaWhich GCP service should a Data Engineer choose as a managed RDBMS for general-purpose MySWhich GCP service should a Data Engineer choose as a managed Postgres-compatible RDBMS wit