Question 303 of 1,000
Design and Plan Database SolutionshardMultiple SelectObjective-mapped

PCDOE Secondary index 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. A key principle to apply: secondary index. 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 Cloud Spanner database for a global supply chain application. The schema includes a table 'Shipments' with columns: shipment_id (INT64), created_at (TIMESTAMP), origin (STRING), destination (STRING), status (STRING). The application frequently queries for shipments by origin and status. Which three design choices optimize query performance? (Choose THREE.)

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 in the index to include frequently accessed columns.

Option B is correct because the STORING clause in a Cloud Spanner secondary index allows you to include additional columns (such as 'destination' or 'status') in the index storage, enabling index-only scans that avoid fetching rows from the base table. This reduces read latency and resource consumption for queries that frequently access those columns along with the indexed keys. Option C is correct because interleaving an 'OrderItems' table under 'Shipments' places child rows physically close to parent rows, improving join performance by reducing round trips and allowing efficient row scans. Option D is correct because a secondary index on (origin, status) directly supports the frequent queries filtering on those columns, enabling fast lookups without scanning the entire table. Options A and E are incorrect: Cloud Spanner does not support traditional partitioning by region, and monotonically increasing primary keys cause hotspotting at the leader, reducing write throughput.

Key principle: Secondary index

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

  • Partition the table by region to limit scans.

    Why it's wrong here

    Spanner does not support user-defined partitioning.

  • Use the STORING clause in the index to include frequently accessed columns.

    Why this is correct

    Reduces additional reads.

    Related concept

    Secondary index

  • Interleave an 'OrderItems' table under 'Shipments' for join performance.

    Why this is correct

    Interleaving improves read locality.

    Related concept

    Secondary index

  • Create a secondary index on (origin, status) for efficient filtering.

    Why this is correct

    Index speeds up queries.

    Related concept

    Secondary index

  • Use a monotonically increasing integer primary key for high write throughput.

    Why it's wrong here

    Causes hotspots.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the misconception that Cloud Spanner supports traditional partitioning or that monotonically increasing keys are safe for distributed databases, leading candidates to select options that would actually degrade performance.

Detailed technical explanation

How to think about this question

Cloud Spanner's secondary indexes are global and strongly consistent, meaning they are updated synchronously with the base table. The STORING clause materializes the specified columns into the index's data blocks, which allows the query to be satisfied entirely from the index without a back-join to the base table — this is similar to a covering index in other databases but with Spanner's distributed architecture. In a global supply chain application, this can dramatically reduce cross-region reads when the index is co-located with the querying region.

KKey Concepts to Remember

  • Secondary index
  • Interleaved table
  • STORING clause

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

Secondary index

Real-world example

How this comes up in practice

A startup's cloud architect reviews their monthly bill and notices costs are higher than expected for a long-running batch job. Switching from on-demand instances to Reserved Instances — or using Spot/Preemptible VMs — can reduce compute costs by up to 72 %. Questions like this test whether you understand the tradeoffs between commitment, flexibility, and cost across cloud pricing models.

What to study next

Got this wrong? Here's your next step.

Review secondary index, then practise related PCDOE questions on the same topic to reinforce the concept.

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.

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 — Secondary index.

What is the correct answer to this question?

The correct answer is: Use the STORING clause in the index to include frequently accessed columns. — Option B is correct because the STORING clause in a Cloud Spanner secondary index allows you to include additional columns (such as 'destination' or 'status') in the index storage, enabling index-only scans that avoid fetching rows from the base table. This reduces read latency and resource consumption for queries that frequently access those columns along with the indexed keys. Option C is correct because interleaving an 'OrderItems' table under 'Shipments' places child rows physically close to parent rows, improving join performance by reducing round trips and allowing efficient row scans. Option D is correct because a secondary index on (origin, status) directly supports the frequent queries filtering on those columns, enabling fast lookups without scanning the entire table. Options A and E are incorrect: Cloud Spanner does not support traditional partitioning by region, and monotonically increasing primary keys cause hotspotting at the leader, reducing write throughput.

What should I do if I get this PCDOE question wrong?

Review secondary index, then practise related PCDOE questions on the same topic to reinforce the concept.

What is the key concept behind this question?

Secondary index

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More PCDOE practice questions

Last reviewed: Jul 4, 2026

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.

Loading comments…

Sign in to join the discussion.

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.