Home › GCP Data Engineer › cloudcomputing › gcpdestorage › Which BigQuery storage optimisation should a Dat…
Which BigQuery storage optimisation should a Data Engineer apply IN ADDITION to partitioning, to physically co-locate rows by a high-cardinality column (e.g. user_id) for faster filtered scans?
ACloud Memorystore
BClustering on one to four columns
CCloud DNS
DDisabling clustering entirely
Answer & Solution
Correct answer: B. Clustering on one to four columns
Clustering co-locates rows by column value (per PDE §3.2). The other options don't optimize.
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 to a large fact table queWhich 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