The answer is to partition by date and cluster by region. This combination directly addresses the dashboard’s most common query patterns: filtering on a specific date range and a specific region. Partitioning by a DATE or TIMESTAMP column enables BigQuery to perform partition pruning, scanning only the relevant daily partitions instead of the entire table, which drastically reduces data processed and cost. Clustering by region then sorts the rows within each partition, allowing for efficient block-level pruning when the region filter is applied, further minimizing scanned bytes. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding of how partitioning and clustering work together to optimize different filter dimensions—a common trap is clustering on the same column used for partitioning, which provides no additional benefit. Remember the memory tip: “Partition for range, cluster for filter”—partitioning handles broad time-based scans, while clustering fine-tunes selective lookups within those slices.
PCDE Practice Question: Define data structures and implement SQL for Business Intelligence
This PCDE practice question tests your understanding of define data structures and implement sql for business intelligence. Read the scenario carefully and evaluate each option against the stated constraints before committing to an answer. After answering, compare your reasoning against the explanation and wrong-answer breakdown below. Once you have made your selection, read the full explanation to reinforce the concept and understand why each distractor is designed to mislead on exam day.
A BI team is designing a BigQuery table for a sales dashboard that queries daily sales by product category and region. The dashboard often filters on a specific date range and a specific region. Which combination of partitioning and clustering should be used?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Partition by date, cluster by region
Partitioning by date (e.g., on a DATE or TIMESTAMP column) allows BigQuery to prune entire partitions when the dashboard filters on a specific date range, reducing the amount of data scanned. Clustering by region then sorts the data within each partition by region, enabling efficient block-level pruning when the dashboard filters on a specific region. This combination optimizes both the date range and region filters, which are the most common query patterns for this sales dashboard.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
✗
Partition by region, cluster by date
Why it's wrong here
Partitioning by region may lead to many small partitions and does not optimize date range filters.
✗
Use only clustering on date and region without partitioning
Why it's wrong here
Without partitioning, all partitions are scanned, even if clustering helps to skip blocks, it's less efficient.
✓
Partition by date, cluster by region
Why this is correct
Partitioning by date fine-tunes the scan to the date range; clustering by region organizes data to skip irrelevant blocks.
Related concept
Read the scenario before looking for a memorised answer.
✗
Partition by month, cluster by date
Why it's wrong here
Clustering by date when date is also part of partitioning adds redundancy and does not help with region filtering.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that partitioning can be applied to any column type (like region) or that clustering alone is sufficient for date range filtering, leading candidates to overlook the mandatory requirement that partitioning must be on a DATE, TIMESTAMP, or integer column and that clustering complements but does not replace partitioning for range-based pruning.
Detailed technical explanation
How to think about this question
Under the hood, BigQuery uses columnar storage and a distributed file system; partitioning physically separates data into separate storage blocks (partitions) based on the partition key, while clustering sorts data within each partition based on the clustering columns. When a query filters on a specific date range, BigQuery uses the partition filter to skip entire partitions (pruning), and then within the remaining partitions, it uses the clustering metadata to skip blocks that don't match the region filter. A real-world scenario: a dashboard querying sales for the last 7 days in 'US-East' would scan only the 7 daily partitions and within those, only the blocks sorted for 'US-East', dramatically reducing bytes billed.
KKey Concepts to Remember
Read the scenario before looking for a memorised answer.
Find the constraint that changes the correct option.
Eliminate answers that are true in general but not in this case.
TExam Day Tips
→Watch for words such as best, first, most likely and least administrative effort.
→Review why wrong options are wrong, not only why the correct option is correct.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
How this comes up in practice
A cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
What to study next
Got this wrong? Here's your next step.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Define data structures and implement SQL for Business Intelligence — This question tests Define data structures and implement SQL for Business Intelligence — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Partition by date, cluster by region — Partitioning by date (e.g., on a DATE or TIMESTAMP column) allows BigQuery to prune entire partitions when the dashboard filters on a specific date range, reducing the amount of data scanned. Clustering by region then sorts the data within each partition by region, enabling efficient block-level pruning when the dashboard filters on a specific region. This combination optimizes both the date range and region filters, which are the most common query patterns for this sales dashboard.
What should I do if I get this PCDE question wrong?
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
What is the key concept behind this question?
Read the scenario before looking for a memorised answer.
About these practice questions
Courseiva creates original exam-style practice questions with explanations and wrong-answer analysis. It does not publish real exam questions, exam dumps, or protected exam content. Learn why practice questions differ from exam dumps →
These questions test the same concept from different angles. Work through them to make sure you can recognise it however the exam phrases it.
Variation 1. A BI team runs a daily query on a BigQuery table 'events' partitioned by event_date. The query filters on event_date = CURRENT_DATE() and counts rows by event_type. The query is slow. Upon review, the table has 500 partitions but clustering is not set. Which action reduces query cost and latency?
medium
A.Recreate the table with only the last 30 days of data
B.Use a wildcard table for daily ingestion
C.Increase the partition expiration to 365 days
✓ D.Add clustering on event_type
Why D: Adding clustering on `event_type` physically co-locates rows with the same event type within each partition. This allows BigQuery to use block-level pruning when reading data, drastically reducing the number of bytes scanned for the COUNT(*) GROUP BY query. Since the query already filters on a single partition (`event_date = CURRENT_DATE()`), the performance bottleneck is scanning all rows in that partition; clustering eliminates that overhead without changing the table's structure or retention.
Variation 2. A data engineer is designing a BigQuery schema for a time-series dataset of IoT sensor readings. The queries will filter primarily on a timestamp column and also on sensor_id. To optimize query performance and cost, which table design is best?
easy
✓ A.Partition by timestamp, cluster by sensor_id
B.Partition by sensor_id, cluster by timestamp
C.Partition by timestamp, cluster by timestamp
D.No partitioning, cluster by timestamp
Why A: Partitioning by timestamp allows BigQuery to prune entire partitions when queries filter on the timestamp column, reducing the amount of data scanned and thus lowering cost and improving performance. Clustering by sensor_id further organizes data within each partition, enabling block-level pruning for queries that filter on sensor_id. This combination optimizes for the primary filter (timestamp) and secondary filter (sensor_id) without the overhead of excessive partitions.
Last reviewed: Jun 30, 2026
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
This PCDE practice question is part of Courseiva's free Google Cloud certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the PCDE exam.
Question Discussion
Share a tip, memory trick, or ask about the reasoning behind this question. Do not post real exam questions, leaked content, braindumps, or copyrighted exam material. Comments are moderated and may be removed without notice.
Sign in to join the discussion.