- A
Cloud Logging — search logs for error messages across all 15 services.
Why wrong: Log searching finds errors after they occur but doesn't correlate cross-service request timelines or show which service hop added latency in a distributed trace.
- B
Cloud Trace — captures distributed request traces showing end-to-end latency across all microservices.
Cloud Trace shows the complete request journey: which service was called, in what order, and how long each call took. The Gantt-chart view immediately reveals the latency culprit service.
- C
Cloud Monitoring dashboards — create per-service CPU utilization graphs.
Why wrong: CPU graphs show resource utilization but don't correlate individual request flows across services or show which service contributed to a specific slow request.
- D
Security Command Center — scan for misconfigurations causing performance issues.
Why wrong: SCC identifies security findings and misconfigurations, not application performance issues or distributed request tracing.
How to Identify Which Microservice Causes Latency Using Cloud Trace
This GCDL practice question tests your understanding of scaling with google cloud operations. The scenario asks you to isolate a root cause — eliminate options that address a different problem before choosing. 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 company's application is composed of 15 microservices. When a performance issue occurs, the team struggles to determine which service is causing latency since request traces span multiple services. Which Google Cloud service helps identify which specific service in a microservices chain is causing slowdowns?
Quick Answer
The answer is Cloud Trace, which is the correct choice because it is Google Cloud’s distributed tracing service designed to capture end-to-end latency data as requests travel across multiple microservices. By visualizing the full path of a request through a chain of services, Cloud Trace reveals exactly where slowdowns occur, allowing you to identify which specific microservice is causing the latency. On the Google Cloud Digital Leader exam, this question tests your understanding of observability tools for microservices architectures, often appearing as a scenario where a team struggles to pinpoint performance bottlenecks in a multi-service application. A common trap is confusing Cloud Trace with Cloud Monitoring or Cloud Logging, but remember that only Cloud Trace provides distributed request traces showing latency per service hop. Memory tip: think “Trace the path, find the lag” — Cloud Trace maps the journey of each request to spotlight the slowest service.
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
Cloud Trace — captures distributed request traces showing end-to-end latency across all microservices.
Cloud Trace is designed specifically for distributed tracing in microservices architectures. It captures end-to-end latency data for each request as it traverses multiple services, allowing you to pinpoint which service in the chain is introducing the most delay. This directly addresses the problem of identifying the specific service causing slowdowns in a 15-service application.
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.
- ✗
Cloud Logging — search logs for error messages across all 15 services.
Why it's wrong here
Log searching finds errors after they occur but doesn't correlate cross-service request timelines or show which service hop added latency in a distributed trace.
- ✓
Cloud Trace — captures distributed request traces showing end-to-end latency across all microservices.
Why this is correct
Cloud Trace shows the complete request journey: which service was called, in what order, and how long each call took. The Gantt-chart view immediately reveals the latency culprit service.
Related concept
Read the scenario before looking for a memorised answer.
- ✗
Cloud Monitoring dashboards — create per-service CPU utilization graphs.
Why it's wrong here
CPU graphs show resource utilization but don't correlate individual request flows across services or show which service contributed to a specific slow request.
- ✗
Security Command Center — scan for misconfigurations causing performance issues.
Why it's wrong here
SCC identifies security findings and misconfigurations, not application performance issues or distributed request tracing.
Common exam traps
Common exam trap: answer the scenario, not the keyword
The trap here is that candidates confuse Cloud Logging (which shows error messages) with Cloud Trace (which shows latency timing), or assume CPU utilization graphs (Cloud Monitoring) can pinpoint request-level slowdowns, when only distributed tracing can reveal the exact service in the chain causing the delay.
Trap categories for this question
Command / output trap
Log searching finds errors after they occur but doesn't correlate cross-service request timelines or show which service hop added latency in a distributed trace.
Detailed technical explanation
How to think about this question
Cloud Trace uses the OpenTelemetry standard to instrument applications, collecting trace spans that include start and end timestamps, service names, and parent-child relationships. Under the hood, it applies a sampling rate (configurable, often 1-10 per second) to reduce overhead, and the Trace Explorer can visualize a waterfall chart showing each span's duration, making it easy to spot the service with the longest span. In a real-world scenario, if a request takes 5 seconds total, Cloud Trace can reveal that Service C (e.g., a database query) consumed 4 seconds, while others took milliseconds.
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.
- →
Scaling with Google Cloud operations — study guide chapter
Learn the concepts, then practise the questions
- →
Scaling with Google Cloud operations practice questions
Targeted practice on this topic area only
- →
All GCDL questions
1,000 questions across all exam domains
- →
Google Cloud Digital Leader study guide
Full concept coverage aligned to exam objectives
- →
GCDL practice test guide
How to use practice tests most effectively before exam day
Related practice questions
Related GCDL practice-question pages
Use these pages to review the topic behind this question. This is how one missed question becomes focused revision.
Why Cloud Technology Can Transform Business practice questions
Practise GCDL questions linked to Why Cloud Technology Can Transform Business.
Fundamental Cloud Concepts practice questions
Practise GCDL questions linked to Fundamental Cloud Concepts.
Google Cloud Security practice questions
Practise GCDL questions linked to Google Cloud Security.
How Google Cloud Resources Are Managed practice questions
Practise GCDL questions linked to How Google Cloud Resources Are Managed.
Google Cloud Products and Services practice questions
Practise GCDL questions linked to Google Cloud Products and Services.
Why cloud technology is transforming business practice questions
Practise GCDL questions linked to Why cloud technology is transforming business.
Google Cloud products, services, and solutions practice questions
Practise GCDL questions linked to Google Cloud products, services, and solutions.
Scaling with Google Cloud operations practice questions
Practise GCDL questions linked to Scaling with Google Cloud operations.
Trust and security with Google Cloud practice questions
Practise GCDL questions linked to Trust and security with Google Cloud.
GCDL fundamentals practice questions
Practise GCDL questions linked to GCDL fundamentals.
GCDL scenario practice questions
Practise GCDL questions linked to GCDL scenario.
GCDL troubleshooting practice questions
Practise GCDL questions linked to GCDL troubleshooting.
Practice this exam
Start a free GCDL 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 GCDL question test?
Scaling with Google Cloud operations — This question tests Scaling with Google Cloud operations — Read the scenario before looking for a memorised answer..
What is the correct answer to this question?
The correct answer is: Cloud Trace — captures distributed request traces showing end-to-end latency across all microservices. — Cloud Trace is designed specifically for distributed tracing in microservices architectures. It captures end-to-end latency data for each request as it traverses multiple services, allowing you to pinpoint which service in the chain is introducing the most delay. This directly addresses the problem of identifying the specific service causing slowdowns in a 15-service application.
What should I do if I get this GCDL 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 →
Keep practising
More GCDL practice questions
- A DevOps team wants to adopt GitOps practices for managing their Google Cloud infrastructure. Which combination of tools…
- A startup is building an application that sends daily promotional push notifications to millions of mobile users on both…
- An organization's leadership wants to foster a 'fail fast' culture to accelerate innovation. A cloud environment directl…
- A company's on-premises applications occasionally need more compute capacity than their own infrastructure can provide (…
- A digital media company hosts video content globally. They want to reduce origin server load and deliver content faster…
- A security audit finds that a company's application service accounts have been granted broad IAM roles (e.g., Storage Ad…
Last reviewed: Jun 11, 2026
This GCDL 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 GCDL 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.