- A
Use a hash prefix in the primary key to distribute writes across splits.
Hashing prevents sequential writes from hitting the same split.
- B
Use a timestamp prefix in the primary key to sort by time.
Why wrong: Timestamp prefix causes all recent writes to go to the same split, creating a hotspot.
- C
Use interleaved tables to keep related rows together.
Why wrong: Interleaving helps with reads but can concentrate writes on a single split.
- D
Design the schema so that hot rows are split into multiple rows with different keys.
Spreading a hot logical row across multiple physical rows reduces write pressure.
- E
Decrease the number of splits by using a less granular primary key.
Why wrong: Fewer splits increase contention because all writes go to fewer nodes.
Quick Answer
The answer is to design the schema so that hot rows are split into multiple rows with different keys. This approach directly reduces write contention by distributing incoming writes across many distinct rows, preventing a single row from becoming a bottleneck under high traffic. In Cloud Spanner, contention occurs when multiple transactions try to modify the same row simultaneously, causing retries and latency; splitting the hot row into separate keys spreads the write load across different splits, improving throughput. On the Google Professional Cloud Database Engineer exam, this concept tests your understanding of schema design for distributed databases, often appearing as a trap where monotonically increasing keys or timestamp prefixes are mistakenly chosen because they seem logical but actually cause hotspotting. A common memory tip is to think of a busy checkout line: splitting one long line into multiple shorter lines reduces congestion, just as splitting a hot row into multiple keys reduces write contention.
PCDE Design and implement database schemas Practice Question
This PCDE practice question tests your understanding of design and implement database schemas. 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.
Which TWO schema design practices help reduce write contention in Cloud Spanner?
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 a hash prefix in the primary key to distribute writes across splits.
Options A and D are correct. Option A: Using a monotonically increasing primary key causes hotspotting; instead, use a hash prefix. Option D: Splitting hot rows into multiple rows with different keys spreads writes. Option B is wrong because interleaving can increase contention if parent is hot. Option C is wrong because decreasing splits reduces parallelism. Option E is wrong because timestamp prefix causes hotspotting.
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 a hash prefix in the primary key to distribute writes across splits.
Why this is correct
Hashing prevents sequential writes from hitting the same split.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Use a timestamp prefix in the primary key to sort by time.
Why it's wrong here
Timestamp prefix causes all recent writes to go to the same split, creating a hotspot.
- ✗
Use interleaved tables to keep related rows together.
Why it's wrong here
Interleaving helps with reads but can concentrate writes on a single split.
- ✓
Design the schema so that hot rows are split into multiple rows with different keys.
Why this is correct
Spreading a hot logical row across multiple physical rows reduces write pressure.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Decrease the number of splits by using a less granular primary key.
Why it's wrong here
Fewer splits increase contention because all writes go to fewer nodes.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Many certification questions include familiar terms but test a specific constraint. Read the exact wording before choosing an answer that is generally true but wrong for this case.
Detailed technical explanation
How to think about this question
This question should be treated as a scenario, not a definition check. Identify the problem, the constraint and the best action. Then compare each option against those facts.
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.
- Use explanations to understand the rule behind the answer.
TExam Day Tips
- Underline the problem statement mentally.
- 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 PCDE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
- →
Design and implement database schemas — study guide chapter
Learn the concepts, then practise the questions
- →
Design and implement database schemas practice questions
Targeted practice on this topic area only
- →
All PCDE questions
503 questions across all exam domains
- →
Google Professional Cloud Database Engineer study guide
Full concept coverage aligned to exam objectives
- →
PCDE practice test guide
How to use practice tests most effectively before exam day
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.
Plan and manage database infrastructure practice questions
Practise PCDE questions linked to Plan and manage database infrastructure.
Define data structures and implement SQL for Business Intelligence practice questions
Practise PCDE questions linked to Define data structures and implement SQL for Business Intelligence.
Design and implement database schemas practice questions
Practise PCDE questions linked to Design and implement database schemas.
Monitor and optimize database performance practice questions
Practise PCDE questions linked to Monitor and optimize database performance.
PCDE fundamentals practice questions
Practise PCDE questions linked to PCDE fundamentals.
PCDE scenario practice questions
Practise PCDE questions linked to PCDE scenario.
PCDE troubleshooting practice questions
Practise PCDE questions linked to PCDE troubleshooting.
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?
Design and implement database schemas — This question tests Design and implement database schemas — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Use a hash prefix in the primary key to distribute writes across splits. — Options A and D are correct. Option A: Using a monotonically increasing primary key causes hotspotting; instead, use a hash prefix. Option D: Splitting hot rows into multiple rows with different keys spreads writes. Option B is wrong because interleaving can increase contention if parent is hot. Option C is wrong because decreasing splits reduces parallelism. Option E is wrong because timestamp prefix causes hotspotting.
What should I do if I get this PCDE question wrong?
Identify which PCDE exam domain this question belongs to, then review the specific concept being tested. Practise related questions in that domain and focus on understanding why each wrong answer is tempting — not just why the correct answer is right.
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: Jun 24, 2026
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.
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.