The correct answer is to change the primary key to include a hash prefix of the original key. This works because Cloud Spanner distributes data across splits based on the primary key’s leading column; without a hash prefix, monotonically increasing keys like timestamps cause all writes to target the same split, creating a hot spot that triggers read-write conflicts and aborts. Adding a hash prefix randomizes key distribution, spreading write contention across multiple splits and reducing latency. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding of Cloud Spanner’s split architecture and how to mitigate hot-spotting—a common trap is to suggest secondary indexes, which don’t affect row-level write distribution. Remember the mnemonic: “Hash the head to spread the load,” meaning hash the leading key column to avoid a single split bottleneck.
PCDE Monitor and optimize database performance Practice Question
This PCDE practice question tests your understanding of monitor and optimize database performance. 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.
Your Cloud Spanner database is experiencing a high volume of read-write conflicts, causing many aborts and high latency. You have already increased the compute capacity. Upon analyzing the schema, you find that most conflicts occur on a single table with frequent updates to the same row. What index or schema change would most effectively reduce contention?
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Change the primary key to include a hash prefix of the original key.
Option D is correct because adding a hash prefix to the primary key distributes writes across multiple splits, reducing hot-spotting on a single row. Cloud Spanner uses range-based splits; without a hash prefix, monotonically increasing keys cause all writes to target the same split, leading to read-write conflicts and aborts. A hash prefix randomizes the key distribution, spreading load across nodes and minimizing contention.
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.
✗
Enable batch writes in the client library to combine updates.
Why it's wrong here
Batch writes combine multiple updates but do not reduce row-level contention.
✗
Use a monotonically increasing timestamp as a prefix to the primary key.
Why it's wrong here
Monotonically increasing keys cause hotspotting on the last split, worsening contention.
✗
Add a secondary index on the most frequently updated column.
Why it's wrong here
Secondary indexes help reads but do not reduce write contention.
✓
Change the primary key to include a hash prefix of the original key.
Why this is correct
A hash prefix distributes writes evenly across splits, reducing row-level contention.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that secondary indexes or batching solve hot-spotting, when the root cause is key distribution; candidates must recognize that only changing the primary key structure (e.g., hash prefix) directly addresses split-level contention.
Detailed technical explanation
How to think about this question
Cloud Spanner splits data by primary key ranges; a hash prefix (e.g., SHA256 of the original key modulo N) ensures uniform distribution across splits, preventing a single split from becoming a bottleneck. This technique is analogous to sharding in NoSQL databases but applied within Spanner's distributed SQL model. In practice, choosing an appropriate hash bucket count (e.g., 1000) balances write throughput while still allowing efficient point lookups via the original key.
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.
Monitor and optimize database performance — This question tests Monitor and optimize database performance — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Change the primary key to include a hash prefix of the original key. — Option D is correct because adding a hash prefix to the primary key distributes writes across multiple splits, reducing hot-spotting on a single row. Cloud Spanner uses range-based splits; without a hash prefix, monotonically increasing keys cause all writes to target the same split, leading to read-write conflicts and aborts. A hash prefix randomizes the key distribution, spreading load across nodes and minimizing contention.
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 →
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.
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.