The answer is that the descending timestamp in the primary key is causing hotspotting on the tablet leader for the most recent data. This occurs because Cloud Spanner uses the first column of the primary key to determine data distribution and splits; with (UserId, PostTimestamp DESC), all writes for the latest posts are concentrated on a single tablet leader, overwhelming it with both read and write traffic. On the Google Professional Cloud Database Engineer exam, this scenario tests your understanding of how primary key design directly impacts Spanner’s split and load-balancing behavior—a common trap is assuming a descending timestamp spreads writes evenly, when in fact it creates a hot spot at the “end” of the key space. Remember the memory tip: “First column splits, so avoid monotonic values at the head.” To fix this, consider using a hash prefix or a sharding column before the timestamp to distribute writes across multiple tablet leaders.
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.
You are designing a Cloud Spanner schema for a global social media application. The application reads the most recent 100 posts for a user's timeline. The Posts table has a primary key of (UserId, PostTimestamp DESC). You observe that queries for the timeline are hitting high read latency and the transaction abort rate is increasing. What is the most likely cause?
Clue words in this question
Noticing these words before you look at the options changes how you read each choice.
Clue: "most likely"
Why it matters: Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
Clue: "primary"
Why it matters: Asks for the main purpose or function, not a secondary benefit. Eliminate answers that describe side-effects or partial functions.
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
The descending timestamp in the primary key is causing hotspotting on the tablet leader for the most recent data.
The descending timestamp in the primary key causes all writes for the most recent posts to be concentrated on the same tablet leader, because Cloud Spanner uses the first primary key column for splitting and distributing data. This hotspotting leads to high read latency and increased transaction abort rates as the single leader becomes overloaded with both writes and reads for the latest data.
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.
✓
The descending timestamp in the primary key is causing hotspotting on the tablet leader for the most recent data.
Why this is correct
Frequent inserts to the same split (latest timestamp) cause contention.
Clue confirmation
The clue words "most likely", "primary" in the question point toward this answer.
Related concept
Read the scenario before looking for a memorised answer.
✗
The instance has too few nodes to handle the write volume.
Why it's wrong here
More nodes would spread load, but the underlying hotspot issue remains.
✗
The lack of a secondary index on UserId is forcing full table scans.
Why it's wrong here
UserId is the first part of the primary key, so scans are efficient.
✗
The table should be interleaved under a Users table.
Why it's wrong here
Interleaving does not prevent hotspotting.
Common exam traps
Common exam trap: answer the scenario, not the keyword
Google Cloud often tests the misconception that adding more nodes or secondary indexes solves all performance problems, when in fact the root cause is often a poorly designed primary key that creates hotspotting in Cloud Spanner's distributed architecture.
Detailed technical explanation
How to think about this question
Cloud Spanner splits data based on the first column of the primary key, and a descending timestamp as the second column causes all new writes to target the same split (the one handling the most recent timestamp). This creates a 'hotspot' on a single tablet server, leading to contention and aborts. In real-world scenarios, using a monotonically increasing value (like a timestamp) as the first or second column of a primary key is a common anti-pattern that must be avoided by using a hash prefix or a sharding column.
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: The descending timestamp in the primary key is causing hotspotting on the tablet leader for the most recent data. — The descending timestamp in the primary key causes all writes for the most recent posts to be concentrated on the same tablet leader, because Cloud Spanner uses the first primary key column for splitting and distributing data. This hotspotting leads to high read latency and increased transaction abort rates as the single leader becomes overloaded with both writes and reads for the latest data.
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.
Are there clue words in this question I should notice?
Yes — watch for: "most likely", "primary". Probability qualifier — the question wants the most probable cause or outcome, not a guaranteed one. Eliminate low-probability options.
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.