Quick Answer
The answer is to cluster the `sales_fact` table on `product_id`. This is correct because the join performance bottleneck stems from the massive shuffle required to match 25 million rows from `sales_fact` with the `products` table; clustering on the join key physically co-locates rows with the same `product_id` within each partition, drastically reducing data movement and enabling BigQuery to use more efficient join strategies like broadcast joins. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding that clustering optimizes join-heavy queries by minimizing shuffle, a common trap being to mistakenly repartition or add clustering to the small dimension table. The key insight is that clustering the large fact table on the join key—not the dimension table—directly addresses the data skew and shuffle cost. Memory tip: "Cluster the big table on the join key to keep data cozy and avoid the shuffle frenzy."
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.
You are a database engineer at a retail company. The company uses BigQuery for BI, with a fact table 'sales_fact' partitioned by order_date and containing 100 million rows. There is a dimension table 'products' with 10,000 rows. The BI team reports that the following query takes over 5 minutes to run: SELECT p.category, SUM(s.amount) FROM sales_fact s JOIN products p ON s.product_id = p.product_id WHERE s.order_date >= '2024-01-01' AND s.order_date < '2024-04-01' GROUP BY p.category. The table 'products' is not partitioned or clustered. 'sales_fact' is partitioned by order_date but not clustered. The query only scans 3 months of data (about 25 million rows). However, the join seems slow. What is the most likely cause and what single action would you take to improve performance?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Cluster the 'sales_fact' table on product_id
Clustering on the join key reduces shuffle and speeds up join.
Use a cross-join to avoid the join
Why wrong: Cross-join would be disastrously slow.
Add an index on 'products.product_id'
Why wrong: BigQuery does not use indexes.
Partition the 'products' table
Why wrong: Products table is small; partitioning won't help much.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Cluster the 'sales_fact' table on product_id
The query is slow because the join on `product_id` requires shuffling 25 million rows from `sales_fact` across nodes to match with `products`. Clustering `sales_fact` on `product_id` co-locates rows with the same `product_id` within each partition, reducing shuffle overhead and enabling more efficient broadcast or hash joins in BigQuery. This is the most impactful single action because it directly addresses the join performance bottleneck without changing the query logic.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Cluster the 'sales_fact' table on product_id
Why this is correct
Clustering on the join key reduces shuffle and speeds up join.
Clue confirmation
The clue word "most likely" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Use a cross-join to avoid the join
Why it's wrong here
Cross-join would be disastrously slow.
Add an index on 'products.product_id'
Why it's wrong here
BigQuery does not use indexes.
Partition the 'products' table
Why it's wrong here
Products table is small; partitioning won't help much.
Common exam traps
Google Cloud often tests the misconception that indexes or partitioning small tables solve join performance issues, when the real solution in BigQuery is clustering the large fact table on the join key to minimize data shuffling.
Detailed technical explanation
In BigQuery, clustering sorts data within each partition based on the specified column(s), allowing the query engine to use block-level pruning and more efficient join strategies like broadcast joins when one side is small. Without clustering, the join on `product_id` forces a full shuffle of the fact table rows, which is expensive even with partition pruning. In practice, clustering on high-cardinality join keys like `product_id` can reduce query costs by over 50% in large fact-to-dimension joins.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
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
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 — study guide chapter
Learn the concepts, then practise the questions
Define data structures and implement SQL for Business Intelligence practice questions
Targeted practice on this topic area only
All PCDE questions
503 questions across all exam domains
Google Professional Cloud Database Engineer study guide
Full concept coverage aligned to exam objectives
PCDE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCDE questions linked to Plan and manage database infrastructure.
Practise PCDE questions linked to Define data structures and implement SQL for Business Intelligence.
Practise PCDE questions linked to Design and implement database schemas.
Practise PCDE questions linked to Monitor and optimize database performance.
Practise PCDE questions linked to PCDE fundamentals.
Practise PCDE questions linked to PCDE scenario.
Practise PCDE questions linked to PCDE troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
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..
The correct answer is: Cluster the 'sales_fact' table on product_id — The query is slow because the join on `product_id` requires shuffling 25 million rows from `sales_fact` across nodes to match with `products`. Clustering `sales_fact` on `product_id` co-locates rows with the same `product_id` within each partition, reducing shuffle overhead and enabling more efficient broadcast or hash joins in BigQuery. This is the most impactful single action because it directly addresses the join performance bottleneck without changing the query logic.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
Yes — watch for: "most likely". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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 →
Last reviewed: Jun 30, 2026
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.