Question 169 of 503
Monitor and optimize database performancehardMultiple SelectObjective-mapped

Quick Answer

The answer is using secondary indexes to avoid full table scans, along with employing read-only transactions with strong consistency and designing your schema to minimize interleaved table lookups. Read-only transactions with strong consistency in Cloud Spanner use lock-free reads that return the most recent data without blocking writes, which directly reduces read latency because the system serves data from the current timestamp without waiting for write locks or replication delays. On the Google Professional Cloud Database Engineer exam, this concept tests your understanding of how Spanner separates read and write paths to optimize performance; a common trap is assuming all strongly consistent reads require locks, when in fact read-only transactions bypass them entirely. For memory, remember the mnemonic “SIL” — Secondary indexes, Interleaved table optimization, and Lock-free read-only transactions — as the three pillars for cutting read latency in Spanner.

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.

Which THREE actions can help reduce read latency in Cloud Spanner?

Question 1hardmulti select
Full question →

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 read-only transactions with strong consistency

Read-only transactions with strong consistency in Cloud Spanner use lock-free reads that return the most recent data without blocking writes. This reduces read latency because the system can serve the data directly from the current timestamp without waiting for write locks or replication delays, making it ideal for low-latency, strongly consistent reads.

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 read-only transactions with strong consistency

    Why this is correct

    Read-only transactions can execute faster without locks.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Increase the staleness allowed for read queries

    Why it's wrong here

    Stale reads may reduce latency but also reduce data freshness; not a best practice for reducing latency.

  • Structure tables with interleaved parent-child relationships

    Why this is correct

    Interleaving enables efficient join with local storage.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Use secondary indexes to avoid full table scans

    Why this is correct

    Indexes speed up data access.

    Related concept

    Read the scenario before looking for a memorised answer.

  • Batch multiple write operations into a single mutation

    Why it's wrong here

    Batch writes improve write performance, not read latency.

Common exam traps

Common exam trap: answer the scenario, not the keyword

Google Cloud often tests the distinction between read latency and write latency, so candidates may incorrectly choose batching writes (Option E) or increasing staleness (Option B) as read latency reducers, when in fact those affect write performance or trade off consistency for speed.

Detailed technical explanation

How to think about this question

Cloud Spanner uses TrueTime to assign globally consistent timestamps, and read-only transactions with strong consistency leverage this by reading from the current timestamp without acquiring locks. Interleaved tables store parent and child rows in the same split, enabling single-key reads to retrieve related data with minimal round trips. Secondary indexes allow point lookups or range scans without scanning the entire base table, significantly reducing I/O and latency for filtered queries.

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 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 exam domain this question belongs to, review the core concept, then practise similar questions from the same domain.

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.

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?

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: Use read-only transactions with strong consistency — Read-only transactions with strong consistency in Cloud Spanner use lock-free reads that return the most recent data without blocking writes. This reduces read latency because the system can serve the data directly from the current timestamp without waiting for write locks or replication delays, making it ideal for low-latency, strongly consistent reads.

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 →

How Courseiva writes practice questions · Editorial policy

Keep practising

More PCDE practice questions

Last reviewed: Jun 30, 2026

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.

Loading comments…

Sign in to join the discussion.

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.