Quick Answer
The answer is a strong read, as it is the only read type in Cloud Spanner that guarantees the return of the most recent committed data. This is because strong reads enforce external consistency and linearizability, meaning the read operation accesses the current state of the database at the exact timestamp of the request, ensuring no stale or partially committed data is returned. On the Google Professional Cloud Database Engineer exam, this concept tests your understanding of Cloud Spanner’s consistency models, often appearing in scenarios where real-time accuracy is critical, such as financial transactions or inventory systems. A common trap is confusing stale reads (which trade freshness for lower latency) with strong reads, or assuming that read-your-writes consistency alone suffices. Remember the memory tip: “Strong is strong—it always gets the latest song,” reinforcing that strong reads always return the most recent committed data without compromise.
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.
You need to ensure that read operations on a Cloud Spanner database return the most recent committed data. Which read type should you use?
Read-only transaction
Why wrong: Read-only transactions default to strong but are more overhead than a simple strong read.
Stale read
Why wrong: Stale reads may return data that is up to a specified time interval old.
Partitioned read
Why wrong: Partitioned reads are for bulk reads and may use stale reads to prevent locking.
Strong read
Strong reads return the most recent committed data at read time.
Answer choices
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
Strong read
Strong read is the correct choice because it guarantees that read operations return the most recent committed data from Cloud Spanner. Unlike other read types, strong reads access the current state of the database at the time of the read, ensuring external consistency and linearizability, which is critical for applications requiring up-to-date data.
Key principle: Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Answer analysis
For each option: why learners choose it and why it is or isn't the right answer here.
Read-only transaction
Why it's wrong here
Read-only transactions default to strong but are more overhead than a simple strong read.
Stale read
Why it's wrong here
Stale reads may return data that is up to a specified time interval old.
Partitioned read
Why it's wrong here
Partitioned reads are for bulk reads and may use stale reads to prevent locking.
Strong read
Why this is correct
Strong reads return the most recent committed data at read time.
Related concept
Read the scenario before looking for a memorised answer.
Common exam traps
The trap here is that candidates often confuse read-only transactions with strong reads, assuming that any read-only operation automatically returns the latest data, whereas in Spanner, read-only transactions can be configured for stale reads unless explicitly set to strong.
Detailed technical explanation
Under the hood, Cloud Spanner uses TrueTime to assign globally consistent timestamps to transactions, enabling strong reads to achieve external consistency across regions. A strong read in Spanner is implemented by reading at the current TrueTime timestamp, which ensures that the read reflects all committed writes that occurred before that instant. In real-world scenarios, strong reads are essential for financial systems or inventory management where reading stale data could lead to incorrect decisions or duplicate transactions.
Key takeaway
Answer the scenario, not the keyword: identify the specific constraint before choosing the most familiar-sounding option.
Real-world example
A company's IT admin needs to give a contractor read-only access to production logs without sharing account credentials. Using role-based access control (RBAC) and temporary scoped permissions — not a permanent shared password — is the correct pattern. Questions like this test whether you can apply least-privilege access across cloud identity services.
What to study next
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Practise PCDE questions linked to Plan and manage database infrastructure.
Practise PCDE questions linked to Define data structures and implement SQL for Business Intelligence.
Practise PCDE questions linked to Design and implement database schemas.
Practise PCDE questions linked to Monitor and optimize database performance.
Practise PCDE questions linked to PCDE fundamentals.
Practise PCDE questions linked to PCDE scenario.
Practise PCDE questions linked to PCDE troubleshooting.
Practice this exam
Short sessions build daily habit. Longer sessions build exam-day stamina. Try a timed session to simulate real conditions.
FAQ
Plan and manage database infrastructure — This question tests Plan and manage database infrastructure — Read the scenario before looking for a memorised answer..
The correct answer is: Strong read — Strong read is the correct choice because it guarantees that read operations return the most recent committed data from Cloud Spanner. Unlike other read types, strong reads access the current state of the database at the time of the read, ensuring external consistency and linearizability, which is critical for applications requiring up-to-date data.
Identify which exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.
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 25, 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.