- A
Create a composite index with fields 'status' (ascending) and 'createdAt' (ascending).
This composite index configuration supports equality on 'status' and range on 'createdAt'.
- B
No index is needed; single-field indexes are automatically created.
Why wrong: Single-field indexes are automatic, but a composite index is required for queries on multiple fields.
- C
Create a composite index with fields 'createdAt' (ascending) and 'status' (ascending).
Why wrong: The order must place equality fields first. Reverse order would not support the query efficiently.
- D
Add an index exemption on the 'status' field to force index creation.
Why wrong: Index exemptions are for excluding specific fields from automatic indexing, not for creating composite indexes.
Question 668 of 1,000
PCDOE Manage Database Solutions Practice Question
This PCDOE practice question tests your understanding of manage database solutions. This is a configuration task: choose the command set that satisfies every stated requirement. Small differences — like 'secret' vs 'password' or 'transport input ssh' vs 'all' — change whether the answer is correct. 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 developer wants to add a composite index in Firestore to support a query that filters on two fields: 'status' (equality) and 'createdAt' (range). How should the index be configured?
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 composite index with fields 'status' (ascending) and 'createdAt' (ascending).
Option A is correct because Firestore requires a composite index when a query combines an equality filter on one field with a range filter on another. The index must list the equality field first ('status') followed by the range field ('createdAt'), with ascending order for both to support the range query efficiently. This matches the Firestore index definition rules for composite indexes.
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.
- ✓
Create a composite index with fields 'status' (ascending) and 'createdAt' (ascending).
Why this is correct
This composite index configuration supports equality on 'status' and range on 'createdAt'.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
No index is needed; single-field indexes are automatically created.
Why it's wrong here
Single-field indexes are automatic, but a composite index is required for queries on multiple fields.
- ✗
Create a composite index with fields 'createdAt' (ascending) and 'status' (ascending).
Why it's wrong here
The order must place equality fields first. Reverse order would not support the query efficiently.
- ✗
Add an index exemption on the 'status' field to force index creation.
Why it's wrong here
Index exemptions are for excluding specific fields from automatic indexing, not for creating composite indexes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the misconception that the order of fields in a composite index does not matter, but Firestore strictly requires the equality field to precede the range field to avoid a full collection scan.
Detailed technical explanation
How to think about this question
Under the hood, Firestore uses the composite index to perform a zigzag merge join between the equality and range conditions, scanning only the matching documents. The order of fields in the index determines the scan efficiency: the equality field first narrows the result set, then the range field orders the remaining documents. In real-world scenarios, such as querying for 'active' orders created in the last 7 days, this index structure ensures sub-second response times even with millions of documents.
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.
- →
Manage Database Solutions — study guide chapter
Learn the concepts, then practise the questions
- →
Manage 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?
Manage Database Solutions — This question tests Manage Database Solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Create a composite index with fields 'status' (ascending) and 'createdAt' (ascending). — Option A is correct because Firestore requires a composite index when a query combines an equality filter on one field with a range filter on another. The index must list the equality field first ('status') followed by the range field ('createdAt'), with ascending order for both to support the range query efficiently. This matches the Firestore index definition rules for composite indexes.
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.