- A
Set the maximum QPS to 1000 to avoid overloading the cluster.
Why wrong: Bigtable can handle millions of QPS; limiting QPS is not a design choice for taming load.
- B
Partition the data into separate tables for each month.
Why wrong: Multiple tables increase administrative complexity and do not improve read latency.
- C
Use a reverse timestamp in the row key so that recent data is at the beginning of the table.
Reversing the timestamp makes the most recent data appear first, speeding up reads for the last hour.
- D
Use a salting prefix on the row key to distribute writes across nodes.
Salting prevents hotspotting by distributing writes across multiple tablet servers.
- E
Design row keys to be as long as possible to avoid collisions.
Why wrong: Short row keys are preferred; long keys waste storage and memory.
Quick Answer
The correct answer is to use a salting prefix on the row key and reverse timestamps for the row key design. Salting distributes write load across Bigtable nodes by adding a hash prefix, preventing hotspotting when thousands of sensors write simultaneously. Reverse timestamps (e.g., `[salt][max_timestamp - timestamp]`) ensure that the most recent sensor readings appear first in lexicographic order, enabling low-latency scans for the last hour of data. On the Google Professional Cloud Database Engineer exam, this question tests your understanding of Bigtable’s key design principles for time-series workloads—specifically how to balance write throughput with read efficiency. A common trap is choosing to split data across multiple tables, which adds management overhead without solving hotspotting, or making row keys too long, which wastes memory. Remember the mnemonic: “Salt to scatter, reverse to recent.”
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 manufacturing company is deploying a time-series database for sensor data on Cloud Bigtable. They expect 100 TB of data per year and need low-latency reads on row keys within the last hour. Which TWO design choices should they make?
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 reverse timestamp in the row key so that recent data is at the beginning of the table.
Options A (salting) and D (reverse timestamp row keys) are correct. Salting distributes writes, and reverse timestamps allow recent data to appear first, improving read latency for recent rows. Option B is wrong because storing data across multiple tables adds overhead. Option C is wrong because row keys should not be too long. Option E is wrong because Bigtable is designed for high throughput; limiting to 1000 QPS is unnecessary.
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.
- ✗
Set the maximum QPS to 1000 to avoid overloading the cluster.
Why it's wrong here
Bigtable can handle millions of QPS; limiting QPS is not a design choice for taming load.
- ✗
Partition the data into separate tables for each month.
Why it's wrong here
Multiple tables increase administrative complexity and do not improve read latency.
- ✓
Use a reverse timestamp in the row key so that recent data is at the beginning of the table.
Why this is correct
Reversing the timestamp makes the most recent data appear first, speeding up reads for the last hour.
Related concept
Read the scenario before looking for a memorised answer.
- ✓
Use a salting prefix on the row key to distribute writes across nodes.
Why this is correct
Salting prevents hotspotting by distributing writes across multiple tablet servers.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Design row keys to be as long as possible to avoid collisions.
Why it's wrong here
Short row keys are preferred; long keys waste storage and memory.
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 cloud solutions architect for a retail company is evaluating services for a new workload. The correct answer here reflects best practice for the specific scenario described — not a general cloud recommendation. Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option. Cloud exam questions reward reading the constraint carefully: the same technology can be right or wrong depending on the use case.
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.
- →
Plan and manage database infrastructure — study guide chapter
Learn the concepts, then practise the questions
- →
Plan and manage database infrastructure 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?
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 a reverse timestamp in the row key so that recent data is at the beginning of the table. — Options A (salting) and D (reverse timestamp row keys) are correct. Salting distributes writes, and reverse timestamps allow recent data to appear first, improving read latency for recent rows. Option B is wrong because storing data across multiple tables adds overhead. Option C is wrong because row keys should not be too long. Option E is wrong because Bigtable is designed for high throughput; limiting to 1000 QPS is unnecessary.
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.