The answer is to partition the table by month on order_date. Partitioning physically separates data into monthly segments, so when a query filters by a time range, BigQuery prunes irrelevant partitions and scans only the necessary data—directly addressing the slow performance caused by scanning 500 million rows. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding of when to use partitioning versus clustering: partitioning reduces scan cost by eliminating entire date ranges, while clustering sorts data within partitions for finer-grained filtering. A common trap is choosing clustering alone, which still scans all partitions if no partition filter is applied. Remember the memory tip: “Partition to prune, cluster to sort”—for time-based filters on massive tables, always partition first.
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.
Exhibit
Refer to the exhibit.
bq query --use_legacy_sql=false 'SELECT DATE_TRUNC(order_date, MONTH) as month, SUM(revenue) as total_revenue FROM mydataset.orders WHERE order_date BETWEEN "2023-01-01" AND "2023-12-31" GROUP BY month'
The query returns results but takes a long time. The orders table has 500M rows with order_date as a timestamp and revenue as float. How can the query be optimized?
Refer to the exhibit.
bq query --use_legacy_sql=false 'SELECT DATE_TRUNC(order_date, MONTH) as month, SUM(revenue) as total_revenue FROM mydataset.orders WHERE order_date BETWEEN "2023-01-01" AND "2023-12-31" GROUP BY month'
A
Add a clustering key on order_date.
Why wrong: Clustering does not enable partition pruning.
B
Partition the table by month on order_date.
Partition pruning limits data scanned to relevant months.
C
Use a wildcard table over multiple date-sharded tables.
Why wrong: Wildcard tables require sharded tables; not applicable here.
D
Use a materialized view that caches the query result.
Why wrong: Materialized view still scans all partitions if not partitioned.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Partition the table by month on order_date.
Partitioning the table by month on order_date (Option B) is correct because it physically separates the data into monthly partitions, allowing the query engine to prune partitions that do not match the query's time range. This dramatically reduces the amount of data scanned, which is the primary cause of slow performance on a 500M-row table. In BigQuery, partitioning by a timestamp column like order_date is a native, cost-effective optimization that directly addresses the scan bottleneck.
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.
✗
Add a clustering key on order_date.
Why it's wrong here
Clustering does not enable partition pruning.
✓
Partition the table by month on order_date.
Why this is correct
Partition pruning limits data scanned to relevant months.
Related concept
Read the scenario before looking for a memorised answer.
✗
Use a wildcard table over multiple date-sharded tables.
Why it's wrong here
Wildcard tables require sharded tables; not applicable here.
✗
Use a materialized view that caches the query result.
Why it's wrong here
Materialized view still scans all partitions if not partitioned.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often confuse clustering with partitioning, assuming that sorting data (clustering) provides the same scan reduction as physically separating data (partitioning), but clustering only improves block pruning within already-scanned data, not the initial scan elimination.
Detailed technical explanation
How to think about this question
Under the hood, BigQuery partitions are stored in separate storage blocks with independent metadata, enabling the query engine to skip entire partitions during the table scan phase. For a 500M-row table partitioned by month, a query filtering on a single month will scan roughly 1/12th of the data (assuming uniform distribution), reducing both cost and latency proportionally. A real-world scenario where this matters is a time-series analysis on historical order data: without partitioning, every query must scan all 500M rows, even if the user only needs the last 30 days.
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 startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.
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 the table by month on order_date. — Partitioning the table by month on order_date (Option B) is correct because it physically separates the data into monthly partitions, allowing the query engine to prune partitions that do not match the query's time range. This dramatically reduces the amount of data scanned, which is the primary cause of slow performance on a 500M-row table. In BigQuery, partitioning by a timestamp column like order_date is a native, cost-effective optimization that directly addresses the scan bottleneck.
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 →
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.