- A
Use the STORING clause to include frequently queried columns in the index
STORING clause avoids index join by storing additional columns in the index.
- B
Create a global secondary index on 'order_id'
Why wrong: order_id index does not help queries by customer_id.
- C
Partition the table by customer_id
Why wrong: Cloud Spanner does not support table partitioning; it uses splits automatically.
- D
Use the INTERLEAVE IN clause to create a local index
Why wrong: Local indexes are for interleaved tables; not applicable here without interleaving.
- E
Create a secondary index on 'customer_id'
An index on customer_id speeds up queries without full table scan.
Question 402 of 980
Design Scalable and Highly Available Cloud Database Solutions →mediumMultiple SelectObjective-mapped
PCD Practice Question: Design Scalable and Highly Available Cloud Database Solutions
This PCD practice question tests your understanding of design scalable and highly available cloud 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.
You are configuring a Cloud Spanner database for a financial application. You need to ensure that queries on the 'Orders' table by 'customer_id' are efficient without performing a full table scan. You also want to avoid index joins when possible. Which TWO actions should you take?
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
✓
Use the STORING clause to include frequently queried columns in the index
Option A is correct because the STORING clause in a Cloud Spanner secondary index allows you to include additional columns (e.g., frequently queried columns) directly in the index entries. This enables index-only scans, avoiding the need for an index join (back join) to fetch data from the base table, thus improving query efficiency. Option E is correct because creating a secondary index on 'customer_id' directly supports efficient point lookups and range scans on that column, preventing full table scans.
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 the STORING clause to include frequently queried columns in the index
Why this is correct
STORING clause avoids index join by storing additional columns in the index.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Create a global secondary index on 'order_id'
Why it's wrong here
order_id index does not help queries by customer_id.
- ✗
Partition the table by customer_id
Why it's wrong here
Cloud Spanner does not support table partitioning; it uses splits automatically.
- ✗
Use the INTERLEAVE IN clause to create a local index
Why it's wrong here
Local indexes are for interleaved tables; not applicable here without interleaving.
- ✓
Create a secondary index on 'customer_id'
Why this is correct
An index on customer_id speeds up queries without full table scan.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Cisco often tests the distinction between local (interleaved) and global secondary indexes, and candidates mistakenly assume that a local index on 'customer_id' (via INTERLEAVE IN) is optimal for single-table queries, but it actually requires the parent table to be the primary key and does not avoid index joins unless STORING is used.
Detailed technical explanation
How to think about this question
Cloud Spanner secondary indexes are global by default and stored separately from the base table, requiring a back join to retrieve non-indexed columns. The STORING clause (similar to PostgreSQL's INCLUDE or SQL Server's INCLUDE) stores the specified column values in the index leaf nodes, enabling index-only scans that eliminate the back join. This is particularly beneficial for high-throughput financial applications where reducing read latency and avoiding extra round trips between index and table storage is critical.
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.
- →
Design Scalable and Highly Available Cloud Database Solutions — study guide chapter
Learn the concepts, then practise the questions
- →
Design Scalable and Highly Available Cloud Database Solutions practice questions
Targeted practice on this topic area only
- →
All PCD questions
980 questions across all exam domains
- →
Google Professional Cloud Developer study guide
Full concept coverage aligned to exam objectives
- →
PCD practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related PCD practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Manage a Solution that Can Span Multiple Database Systems practice questions
Practise PCD questions linked to Manage a Solution that Can Span Multiple Database Systems.
Deploy Scalable and Highly Available Databases in Google Cloud practice questions
Practise PCD questions linked to Deploy Scalable and Highly Available Databases in Google Cloud.
Design Scalable and Highly Available Cloud Database Solutions practice questions
Practise PCD questions linked to Design Scalable and Highly Available Cloud Database Solutions.
Migrate Data Solutions practice questions
Practise PCD questions linked to Migrate Data Solutions.
Designing highly scalable, available, and reliable cloud-native applications practice questions
Practise PCD questions linked to Designing highly scalable, available, and reliable cloud-native applications.
Building and testing applications practice questions
Practise PCD questions linked to Building and testing applications.
Deploying applications practice questions
Practise PCD questions linked to Deploying applications.
Integrating Google Cloud services practice questions
Practise PCD questions linked to Integrating Google Cloud services.
Managing application performance monitoring practice questions
Practise PCD questions linked to Managing application performance monitoring.
PCD fundamentals practice questions
Practise PCD questions linked to PCD fundamentals.
PCD scenario practice questions
Practise PCD questions linked to PCD scenario.
PCD troubleshooting practice questions
Practise PCD questions linked to PCD troubleshooting.
Practice this exam
Start a free PCD 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 PCD question test?
Design Scalable and Highly Available Cloud Database Solutions — This question tests Design Scalable and Highly Available Cloud Database Solutions — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use the STORING clause to include frequently queried columns in the index — Option A is correct because the STORING clause in a Cloud Spanner secondary index allows you to include additional columns (e.g., frequently queried columns) directly in the index entries. This enables index-only scans, avoiding the need for an index join (back join) to fetch data from the base table, thus improving query efficiency. Option E is correct because creating a secondary index on 'customer_id' directly supports efficient point lookups and range scans on that column, preventing full table scans.
What should I do if I get this PCD 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 PCD 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 PCD 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.