The answer is to partition fact tables by date and cluster by frequently filtered columns, alongside denormalizing dimensions and using primary keys. This combination is correct because BigQuery’s architecture thrives on reducing data scanned: date partitioning limits queries to relevant time slices, while clustering on high-cardinality filter columns like customer_id or product_id further narrows I/O. Denormalizing dimensions avoids costly joins in BI tools, and defining primary keys—even though BigQuery doesn’t enforce them natively—enables the query engine to optimize join deduplication and MERGE operations, ensuring data integrity in your star schema. On the Google Professional Cloud Database Engineer exam, this tests your understanding that BigQuery is a columnar, serverless warehouse where traditional normalization hurts performance; a common trap is over-normalizing or forgetting that primary keys are advisory, not enforced. Memory tip: think “Partition to prune, cluster to sort, denormalize to skip the join.”
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 company uses BigQuery to run business intelligence reports. The data engineer needs to implement a star schema for a sales data warehouse. Which THREE are best practices when designing the tables?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "best"
Why it matters: Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Use a primary key on fact tables to enforce uniqueness
Option B is correct because in BigQuery, fact tables should have a primary key to enforce uniqueness of each sales transaction, preventing duplicate rows that would skew aggregations like SUM or COUNT. BigQuery does not enforce primary keys natively, but defining them in the schema (e.g., using PRIMARY KEY constraint in DDL) allows the query engine to optimize joins and deduplication, especially when using MERGE statements. This ensures data integrity in the star schema.
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.
✗
Use natural keys in dimension tables for simplicity
Why it's wrong here
Natural keys can change and cause issues; surrogate keys are preferred.
✓
Use a primary key on fact tables to enforce uniqueness
Why this is correct
Ensures each row is unique and allows efficient joins.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
Store pre-aggregated data in dimension tables
Why it's wrong here
Aggregated data should be in fact tables or separate aggregation tables.
✓
Denormalize dimension tables to include descriptive attributes
Why this is correct
Reduces number of joins needed for BI queries.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✓
Partition fact tables by date and cluster by frequently filtered columns
Why this is correct
Optimizes query performance and cost.
Clue confirmation
The clue word "best" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that dimension tables should be highly normalized or contain pre-aggregated data, but the PCDE exam emphasizes denormalizing dimensions for BI readability and storing aggregates only in fact tables or materialized views.
Detailed technical explanation
How to think about this question
In BigQuery, partitioning fact tables by date (e.g., using DATE or TIMESTAMP columns) reduces query costs by pruning partitions, while clustering on frequently filtered columns (e.g., product_id or region) improves scan efficiency through block-level metadata. Under the hood, BigQuery uses a columnar storage format (Capacitor) that benefits from clustering by co-locating similar values, reducing the number of blocks read. A real-world scenario: a sales fact table with 10 billion rows partitioned by day and clustered by customer_id can answer a query for a single customer's weekly sales in seconds instead of minutes.
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: Use a primary key on fact tables to enforce uniqueness — Option B is correct because in BigQuery, fact tables should have a primary key to enforce uniqueness of each sales transaction, preventing duplicate rows that would skew aggregations like SUM or COUNT. BigQuery does not enforce primary keys natively, but defining them in the schema (e.g., using PRIMARY KEY constraint in DDL) allows the query engine to optimize joins and deduplication, especially when using MERGE statements. This ensures data integrity in the star schema.
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.
Are there clue words in this question I should notice?
Yes — watch for: "best". Signals that multiple options may be partially correct. Choose the option that most directly solves the exact problem described, not the one that sounds most complete.
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. Which TWO are best practices for designing a star schema in BigQuery for BI? (Choose two.)
medium
✓ A.Store dimension attributes in a single denormalized dimension table instead of multiple normalized tables.
B.Partition fact tables by low-cardinality columns like gender.
C.Pre-aggregate all measures at every possible grain in the fact table.
D.Avoid using joins entirely by storing all data in one wide table.
✓ E.Use surrogate keys for dimension tables instead of natural keys.
Why A: Option A is correct because in BigQuery, storing dimension attributes in a single denormalized dimension table (star schema) reduces the number of joins required in BI queries, improving query performance and simplifying SQL. BigQuery's columnar storage and distributed architecture handle denormalized dimensions efficiently, avoiding the overhead of multiple normalized tables that would require complex joins and slow down analytical queries.
Variation 2. A company is designing a BigQuery data model for a business intelligence dashboard that shows sales by region and product. The data is refreshed daily. Which schema design is MOST cost-effective and performant for this use case?
easy
A.A table with nested repeated columns for regions and products within each sale.
✓ B.A star schema with a fact table for sales and separate dimension tables for region and product.
C.A fully normalized schema with separate tables for each attribute.
D.A single flat table containing all sales, region, and product columns.
Why B: Option B is correct because a star schema with a fact table for sales and dimension tables for region and product is optimized for analytical queries in BigQuery. Option A is wrong because a flat table with all columns leads to higher storage costs and slower queries due to scanning unnecessary columns. Option C is wrong because a wide table with nested columns is better for hierarchical data, not for simple dimensional analysis. Option D is wrong because a normalized schema with many joins is not ideal for BI queries and increases complexity.
Variation 3. Which TWO of the following are best practices when designing data structures for business intelligence in BigQuery?
easy
✓ A.Partition tables on a column that aligns with common filter criteria
B.Store raw logs directly in fact tables without any aggregation
C.Use NULLable columns extensively to save storage
D.Use a single wide table for all data to simplify schema
✓ E.Denormalize dimension attributes into fact tables to reduce joins
Why A: Partitioning tables on a column that aligns with common filter criteria (e.g., a date or timestamp column) allows BigQuery to prune partitions during query execution, drastically reducing the amount of data scanned and improving query performance and cost efficiency. This is a core best practice for optimizing BI workloads in BigQuery.
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.