- A
Store each entity in a separate table and use secondary indexes.
Why wrong: Bigtable does not support secondary indexes natively (until recently, but still not recommended for joins).
- B
Denormalize orders, customers, and products into a single table with a composite row key.
Denormalization avoids joins and aligns with Bigtable's access patterns.
- C
Use Cloud SQL as a lookup table for joins.
Why wrong: Cross-service joins introduce latency and complexity.
- D
Keep the normalized structure and use MapReduce to perform joins.
Why wrong: MapReduce is not real-time and adds latency; Bigtable is designed for direct access.
PCDOE Design and Plan Database Solutions Practice Question
This PCDOE practice question tests your understanding of design and plan database solutions. 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 team is migrating a relational database to Bigtable. The existing schema uses foreign keys to join orders, customers, and products. Which data model approach is most suitable for Bigtable?
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
Denormalize orders, customers, and products into a single table with a composite row key.
Bigtable is a wide-column NoSQL database optimized for high-throughput, low-latency access, and it does not support SQL-style joins or secondary indexes in the traditional relational sense. Denormalizing orders, customers, and products into a single table with a composite row key (e.g., customer_id#order_id#product_id) allows all related data to be co-located and retrieved with a single row scan, eliminating the need for joins and aligning with Bigtable's key-value access pattern.
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 each entity in a separate table and use secondary indexes.
Why it's wrong here
Bigtable does not support secondary indexes natively (until recently, but still not recommended for joins).
- ✓
Denormalize orders, customers, and products into a single table with a composite row key.
Why this is correct
Denormalization avoids joins and aligns with Bigtable's access patterns.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use Cloud SQL as a lookup table for joins.
Why it's wrong here
Cross-service joins introduce latency and complexity.
- ✗
Keep the normalized structure and use MapReduce to perform joins.
Why it's wrong here
MapReduce is not real-time and adds latency; Bigtable is designed for direct access.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that relational concepts like normalization and joins can be directly applied to NoSQL databases, when in fact Bigtable requires denormalization and careful row key design to achieve performance.
Detailed technical explanation
How to think about this question
In Bigtable, data is stored in sorted key-value pairs, and a composite row key like 'customer_id#order_id#product_id' leverages lexicographic ordering to group related rows together, enabling efficient range scans. For example, scanning all orders for a specific customer becomes a simple prefix scan on the row key, which is O(log n) per lookup. This denormalization trade-off is common in NoSQL systems to avoid the distributed join overhead that would otherwise require scatter-gather operations across multiple nodes.
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 company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
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.
- →
Design and Plan Database Solutions — study guide chapter
Learn the concepts, then practise the questions
- →
Design and Plan Database Solutions practice questions
Targeted practice on this topic area only
- →
All PCDOE questions
1,000 questions across all exam domains
- →
Google Professional Cloud DevOps Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDOE practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCDOE practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Design and Plan Database Solutions practice questions
Practise PCDOE questions linked to Design and Plan Database Solutions.
Manage Database Solutions practice questions
Practise PCDOE questions linked to Manage Database Solutions.
Migrate Database Solutions practice questions
Practise PCDOE questions linked to Migrate Database Solutions.
Design for Reliability, Scalability, and Disaster Recovery practice questions
Practise PCDOE questions linked to Design for Reliability, Scalability, and Disaster Recovery.
Bootstrapping a Google Cloud organization for DevOps practice questions
Practise PCDOE questions linked to Bootstrapping a Google Cloud organization for DevOps.
Managing service incidents practice questions
Practise PCDOE questions linked to Managing service incidents.
Managing Google Cloud costs practice questions
Practise PCDOE questions linked to Managing Google Cloud costs.
Building and implementing CI/CD pipelines practice questions
Practise PCDOE questions linked to Building and implementing CI/CD pipelines.
Implementing service monitoring strategies practice questions
Practise PCDOE questions linked to Implementing service monitoring strategies.
Optimizing service performance practice questions
Practise PCDOE questions linked to Optimizing service performance.
PCDOE fundamentals practice questions
Practise PCDOE questions linked to PCDOE fundamentals.
PCDOE scenario practice questions
Practise PCDOE questions linked to PCDOE scenario.
Practice this exam
Start a free PCDOE 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 PCDOE question test?
Design and Plan Database Solutions — This question tests Design and Plan Database Solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Denormalize orders, customers, and products into a single table with a composite row key. — Bigtable is a wide-column NoSQL database optimized for high-throughput, low-latency access, and it does not support SQL-style joins or secondary indexes in the traditional relational sense. Denormalizing orders, customers, and products into a single table with a composite row key (e.g., customer_id#order_id#product_id) allows all related data to be co-located and retrieved with a single row scan, eliminating the need for joins and aligning with Bigtable's key-value access pattern.
What should I do if I get this PCDOE 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 →
Last reviewed: Jul 4, 2026
This PCDOE 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 PCDOE 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.