Google Cloud Professional Data Engineer · Free practice question 9 of 12
Integer-range partitioning on an ID
Queries on a BigQuery table at Garside Telecom almost always filter on account_id, an integer between 1 and 4,000,000, and the table has no useful date column. The team wants to prune data by account ranges. Which table design allows this?
- A.Ingestion-time partitioning with daily granularity
- B.Time-unit column partitioning on account_id
- C.Creating a separate table for each account
- D.Integer-range partitioning on account_id with a start, end and interval
Show answer and explanation
Correct answer: D. Integer-range partitioning on account_id with a start, end and interval
Why: Integer-range partitioning splits a table on an INTEGER column using a start, end and interval, so filters on account_id prune whole partitions. Ingestion time has nothing to do with account_id, and time-unit partitioning requires a DATE, TIMESTAMP or DATETIME column. A table per account would mean millions of tables.
More free Google Cloud Professional Data Engineer questions
- Sliding windows for moving averages
- Turbo replication on dual-region buckets
- Assured Workloads for sovereign controls
- Data Validation Tool after migration
- Pub/Sub Cloud Storage subscription archive
- Bigtable garbage collection by age
- Search indexes for log lookups
- Data Studio viewer's credentials
- Approximate distinct counts for dashboards
- Scheduled queries for a single SQL job
- Pub/Sub message storage policy regions