- A
Store all data in a single table using nested JSON arrays for product and store details
Why wrong: JSON arrays are not optimized for SQL aggregation and require complex parsing.
- B
Create a single wide table with all attributes (product, store, date, sales)
Why wrong: A single wide table causes data redundancy and poor query performance for BI aggregations.
- C
Create a fact table with foreign keys to dimension tables for product, store, and date
A star schema with fact and dimension tables is the standard for BI reporting, enabling fast aggregations.
- D
Use a fully normalized snowflake schema with separate tables for each level of hierarchy
Why wrong: Snowflake schemas require additional joins, reducing query performance for BI dashboards.
Quick Answer
The correct choice is to create a fact table with foreign keys to dimension tables for product, store, and date. This is the core of a star schema design for BI dashboards, where a central fact table stores quantitative measures—like sales amounts—and references surrounding dimension tables via foreign keys, enabling fast aggregation without redundant data. On the Google Professional Cloud Database Engineer exam, this concept tests your understanding of optimizing analytical queries in BigQuery or similar cloud data warehouses; a common trap is confusing star schemas with snowflake schemas, which add extra normalization and joins that degrade dashboard performance. Remember that star schemas prioritize query speed over storage efficiency, making them ideal for BI aggregation workloads. A simple memory tip: think of the fact table as the sun and dimension tables as orbiting planets—everything revolves around the central fact.
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. Compare every option against the stated constraints before choosing — the best answer satisfies all requirements, not just the most obvious one. 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 is designing a star schema for a BI dashboard that tracks sales performance. The dashboard needs to aggregate sales by product, store, and date. Which schema design is most appropriate?
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
Create a fact table with foreign keys to dimension tables for product, store, and date
Option C is correct because a star schema uses a central fact table with foreign keys to dimension tables, which is optimal for BI aggregation queries. Option A is wrong because a single wide table with all attributes leads to data redundancy and slower queries. Option B is wrong because a fully normalized schema (e.g., snowflake) introduces extra joins that can slow BI queries. Option D is wrong because storing data as JSON arrays in a single table is not suitable for efficient SQL aggregation.
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.
- ✗
Store all data in a single table using nested JSON arrays for product and store details
Why it's wrong here
JSON arrays are not optimized for SQL aggregation and require complex parsing.
- ✗
Create a single wide table with all attributes (product, store, date, sales)
Why it's wrong here
A single wide table causes data redundancy and poor query performance for BI aggregations.
- ✓
Create a fact table with foreign keys to dimension tables for product, store, and date
Why this is correct
A star schema with fact and dimension tables is the standard for BI reporting, enabling fast aggregations.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use a fully normalized snowflake schema with separate tables for each level of hierarchy
Why it's wrong here
Snowflake schemas require additional joins, reducing query performance for BI dashboards.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
- Use explanations to understand the rule behind the answer.
TExam Day Tips
- Underline the problem statement mentally.
- 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
An e-commerce site experiences heavy traffic on Black Friday and near-zero traffic during off-peak weeks. Rather than provisioning permanent large VMs, the team uses auto-scaling groups that add capacity automatically under load and reduce it overnight. Questions like this test whether you understand elasticity, availability zones, and cloud compute scaling patterns.
What to study next
Got this wrong? Here's your next step.
Identify which PCDE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
- →
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
Related PCDE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Plan and manage database infrastructure practice questions
Practise PCDE questions linked to Plan and manage database infrastructure.
Define data structures and implement SQL for Business Intelligence practice questions
Practise PCDE questions linked to Define data structures and implement SQL for Business Intelligence.
Design and implement database schemas practice questions
Practise PCDE questions linked to Design and implement database schemas.
Monitor and optimize database performance practice questions
Practise PCDE questions linked to Monitor and optimize database performance.
PCDE fundamentals practice questions
Practise PCDE questions linked to PCDE fundamentals.
PCDE scenario practice questions
Practise PCDE questions linked to PCDE scenario.
PCDE troubleshooting practice questions
Practise PCDE questions linked to PCDE troubleshooting.
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: Create a fact table with foreign keys to dimension tables for product, store, and date — Option C is correct because a star schema uses a central fact table with foreign keys to dimension tables, which is optimal for BI aggregation queries. Option A is wrong because a single wide table with all attributes leads to data redundancy and slower queries. Option B is wrong because a fully normalized schema (e.g., snowflake) introduces extra joins that can slow BI queries. Option D is wrong because storing data as JSON arrays in a single table is not suitable for efficient SQL aggregation.
What should I do if I get this PCDE question wrong?
Identify which PCDE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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 →
Last reviewed: Jun 24, 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.