Question 339 of 503
Plan and manage database infrastructuremediumMultiple SelectObjective-mapped

Quick Answer

The answer is to use interleaved tables for parent-child relationships to colocate data, as this is one of the three essential practices for Cloud Spanner schema design to ensure good performance. This works because interleaving physically stores child rows alongside their parent row on the same split, drastically reducing cross-node reads and write contention for hierarchical data like orders and line items. On the Google Professional Cloud Database Engineer exam, this concept tests your understanding of how Cloud Spanner’s distributed architecture handles locality; a common trap is assuming that foreign keys alone suffice for performance, but without interleaving, related data may scatter across nodes, causing latency spikes. The other two correct practices typically involve choosing primary keys to avoid hot spots and using monotonically increasing keys only with a hash prefix. A simple memory tip: “Interleave to retrieve, hash to distribute.”

PCDE Plan and manage database infrastructure Practice Question

This PCDE practice question tests your understanding of plan and manage database infrastructure. 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 database engineer is designing a schema for a Cloud Spanner database. Which three practices should they follow to ensure good performance? (Choose three.)

Question 1mediummulti select
Full question →

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 split points to distribute data across nodes.

Option A is correct because explicitly defining split points in Cloud Spanner allows you to control how data is distributed across nodes, which can prevent hot spots and improve read/write throughput. By specifying split boundaries, you ensure that frequently accessed data is spread evenly, avoiding performance bottlenecks.

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 split points to distribute data across nodes.

    Why this is correct

    Explicit splits help avoid hot spots.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use locking read (SELECT ... FOR UPDATE) for all transactional reads.

    Why it's wrong here

    Locking reads reduce concurrency.

  • Design primary keys to avoid monotonically increasing values near the beginning of the key.

    Why this is correct

    Monotonic keys cause hot spots on the first split.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use interleaved tables for parent-child relationships to colocate data.

    Why this is correct

    Interleaving reduces cross-node communication.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Create secondary indexes on every column to speed up queries.

    Why it's wrong here

    Too many indexes increase write amplification.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the misconception that all transactional reads require locking to ensure consistency, but Cloud Spanner's snapshot isolation provides serializable reads without locks, making SELECT ... FOR UPDATE an anti-pattern for most workloads.

Detailed technical explanation

How to think about this question

Cloud Spanner uses a distributed, strongly consistent storage system where data is partitioned into splits, each managed by a set of nodes. Manually defining split points (via the ALTER TABLE ... SPLIT BY statement) lets you align data distribution with access patterns, such as splitting by customer ID range to isolate high-traffic partitions. Interleaved tables (Option D) physically colocate parent and child rows within the same split, reducing cross-node reads for hierarchical queries, which is critical for low-latency joins.

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 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.

Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

Related practice questions

Related PCDE 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 PCDE 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 PCDE question test?

Plan and manage database infrastructure — This question tests Plan and manage database infrastructure — Read the scenario before looking for a memorised answer..

What is the correct answer to this question?

The correct answer is: Use split points to distribute data across nodes. — Option A is correct because explicitly defining split points in Cloud Spanner allows you to control how data is distributed across nodes, which can prevent hot spots and improve read/write throughput. By specifying split boundaries, you ensure that frequently accessed data is spread evenly, avoiding performance bottlenecks.

What should I do if I get this PCDE 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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More PCDE practice questions

Last reviewed: Jun 30, 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 PCDE 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 PCDE exam.