Question 354 of 503

Quick Answer

The answer is to cluster the `customers` table on `customer_id`. This is correct because join optimization via clustering physically co-locates rows sharing the same join key, enabling BigQuery to apply block-level pruning during the join. When the query filters `orders` to just 2 GB of data for today’s date, clustering `customers` on `customer_id` allows BigQuery to skip scanning the entire 2 TB dimension table, reading only the blocks that match the filtered customer IDs from `orders`. On the Google Professional Cloud Database Engineer exam, this tests your understanding that clustering on a join key reduces I/O more effectively than partitioning for dimension tables, especially when the dimension is large and frequently joined. A common trap is to partition `customers` by `customer_country`, but that still requires scanning all matching country blocks; clustering on the join key directly targets the data needed. Remember the mnemonic: “Join on the cluster, skip the bluster.”

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 large e-commerce platform uses BigQuery for business intelligence. They have a fact table `orders` (10 TB, partitioned by order_date, clustered by customer_id) and a dimension table `customers` (2 TB, not partitioned, not clustered). The BI team runs a daily dashboard query that joins these tables on customer_id and filters on order_date = CURRENT_DATE() and customer_country = 'US'. The query currently scans the full `customers` table and 2 GB of the `orders` table, taking 30 seconds. The business wants to reduce cost and latency. The `customers` table has 500 million rows and is updated incrementally every hour. Which action will most effectively reduce the amount of data scanned and query time?

Question 1hardmultiple choice
Full question →

Answer choices

Why each option matters

Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.

Correct answer & explanation

Cluster the `customers` table on customer_id.

Clustering the `customers` table on `customer_id` will physically co-locate rows with the same `customer_id`, allowing the query to use block-level pruning when joining with the filtered `orders` table. Since the query filters `orders` by `order_date = CURRENT_DATE()` (2 GB scanned) and then joins on `customer_id`, BigQuery can skip reading most of the `customers` table if it is clustered on the join key, drastically reducing the 2 TB full scan and lowering both cost and latency.

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.

  • Cluster the `customers` table on customer_id.

    Why this is correct

    Clustering by customer_id enables block-level pruning during the join, drastically reducing data scanned.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Denormalize customer country and other attributes into the `orders` table.

    Why it's wrong here

    Denormalization would increase storage by 10x and complicate hourly updates; clustering is more efficient.

  • Create a materialized view that joins `orders` and `customers` on customer_id.

    Why it's wrong here

    Materialized views require the base tables to be append-only; customers is updated incrementally, causing frequent refreshes and staleness.

  • Partition the `customers` table by customer_id.

    Why it's wrong here

    BigQuery does not support integer range partitioning on a column with high cardinality; only date/timestamp partitioning is allowed.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the misconception that partitioning is always the best optimization for large tables, but here partitioning by `customer_id` is invalid in BigQuery, and the real performance gain comes from clustering on the join key to enable block-level pruning.

Detailed technical explanation

How to think about this question

BigQuery clustering uses a sort-based approach to organize data into blocks that share a common range of cluster key values; when a query filters or joins on that key, the metadata (min/max per block) allows the engine to skip entire blocks that do not contain matching values. For a 500-million-row table, clustering on `customer_id` can reduce the scanned bytes from 2 TB to a few GB if the join keys from the filtered `orders` table are highly selective (e.g., only a few thousand distinct customers from today's orders). This is especially effective because the `orders` table is already partitioned by date and clustered by `customer_id`, so the join becomes a co-located, block-pruned operation.

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.

Related practice questions

Related PCDE practice-question pages

Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.

Practice this exam

Start a free PCDE practice session

Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.

FAQ

Questions learners often ask

What does this PCDE question test?

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: Cluster the `customers` table on customer_id. — Clustering the `customers` table on `customer_id` will physically co-locate rows with the same `customer_id`, allowing the query to use block-level pruning when joining with the filtered `orders` table. Since the query filters `orders` by `order_date = CURRENT_DATE()` (2 GB scanned) and then joins on `customer_id`, BigQuery can skip reading most of the `customers` table if it is clustered on the join key, drastically reducing the 2 TB full scan and lowering both cost and latency.

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 →

How Courseiva writes practice questions · Editorial policy

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.

Loading comments…

Sign in to join the discussion.

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.