- A
Use Cloud SQL instead of Firestore for this relationship
Why wrong: The question asks about Firestore modeling; migrating is not a modeling approach.
- B
Create a top-level collection 'Orders' and use reference fields to link to customers
Why wrong: This requires multiple reads to get a customer's orders (like a join), which is less efficient.
- C
Store orders as a nested array within the customer document
Embedding orders (as subcollection or array) allows fetching all orders in one document read, which is efficient for this access pattern.
- D
Create separate collections for customers and orders, and use composite indexes for queries
Why wrong: This still requires multiple queries or a collection group query, which is more expensive and slower than embedding.
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 legacy application from a relational database to Cloud Firestore. The existing schema has a Customers table and an Orders table with a foreign key. The application often shows orders for a customer. What is the recommended data modeling approach in Firestore?
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
Store orders as a nested array within the customer document
Option C is correct because Cloud Firestore is optimized for denormalized, document-based data models. Storing orders as a nested array within the customer document allows the application to retrieve all orders for a customer with a single document read, which is efficient for the common query pattern of 'showing orders for a customer.' This approach avoids the need for joins or multiple queries, aligning with Firestore's strengths in read-heavy, hierarchical data access.
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 Cloud SQL instead of Firestore for this relationship
Why it's wrong here
The question asks about Firestore modeling; migrating is not a modeling approach.
- ✗
Create a top-level collection 'Orders' and use reference fields to link to customers
Why it's wrong here
This requires multiple reads to get a customer's orders (like a join), which is less efficient.
- ✓
Store orders as a nested array within the customer document
Why this is correct
Embedding orders (as subcollection or array) allows fetching all orders in one document read, which is efficient for this access pattern.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Create separate collections for customers and orders, and use composite indexes for queries
Why it's wrong here
This still requires multiple queries or a collection group query, which is more expensive and slower than embedding.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates often default to relational normalization (separate collections with references or indexes) without considering Firestore's document-based nature, where denormalization and embedding are recommended for common read patterns to avoid multiple queries.
Detailed technical explanation
How to think about this question
Under the hood, Firestore charges per document read, write, and delete, so embedding orders as a subcollection or nested array minimizes reads for the frequent 'get customer with orders' operation. However, be cautious with nested arrays: if orders exceed the 1 MiB document size limit or require atomic updates to individual orders, a subcollection (e.g., 'customers/{id}/orders') is a better choice. In real-world scenarios, this trade-off is critical for applications with high write throughput on orders, as embedding can cause document contention.
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: Store orders as a nested array within the customer document — Option C is correct because Cloud Firestore is optimized for denormalized, document-based data models. Storing orders as a nested array within the customer document allows the application to retrieve all orders for a customer with a single document read, which is efficient for the common query pattern of 'showing orders for a customer.' This approach avoids the need for joins or multiple queries, aligning with Firestore's strengths in read-heavy, hierarchical data access.
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.