Courseiva
mediumMultiple ChoiceObjective-mapped

Google ACE Practice Question: A microservices application has intermittent high…

A microservices application has intermittent high latency. The team wants to identify which specific service-to-service call in the request chain is causing the slowdown. Which Cloud Operations tool is designed for this?

⚠ Common exam trap

Google Cloud often tests the distinction between tools that monitor aggregate metrics (Cloud Monitoring) versus tools that trace individual request paths (Cloud Trace), and the trap here is that candidates confuse Cloud Profiler's code-level profiling with distributed tracing, leading them to pick D instead of C.

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

Cloud Trace is designed to capture latency data for individual service-to-service calls in a distributed request chain. It provides end-to-end tracing by collecting trace spans from each microservice, allowing you to pinpoint which specific call is causing the slowdown. This makes it the correct tool for identifying the exact service-to-service latency bottleneck.

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 Monitoring Metrics Explorer

    Why it's wrong here

    Cloud Monitoring Metrics Explorer is incorrect because it visualizes time-series metrics such as request latency, error counts, or resource utilization aggregated across many requests and instances. While it can reveal that overall latency increased at a certain time, it cannot break down a single request's path or show which specific service call in the chain was slow, because the metric data lacks per-request span causality.

  • Cloud Logging log viewer

    Why it's wrong here

    Cloud Logging log viewer is incorrect because logs record discrete events at specific points in time; without each service explicitly logging trace IDs and precise timestamps for every inbound and outbound call, correlating a single request across services is impractical. Even with such logs, manually stitching together call sequences and computing per-hop durations is fragile and error-prone compared to Cloud Trace's automatic span correlation.

  • Cloud Trace

    Why this is correct

    Cloud Trace is the correct choice because it captures end-to-end request latency as distributed traces, recording each span with its duration and parent-child relationships across services. This lets you follow a single user request through the entire service chain and identify exactly which downstream call added the most delay, rather than merely showing aggregate trends or isolated logs.

  • Cloud Profiler

    Why it's wrong here

    Cloud Profiler is incorrect because it performs continuous, low-overhead sampling of CPU and heap memory usage within a single application process. It is designed to identify performance hotspots inside one service's code, not to correlate timing across separate services in a request path, so it cannot reconstruct the multi-service call chain needed to pinpoint where latency is introduced.

About these practice questions

This ACE question is part of Courseiva's 769-question bank — original exam-style content with full explanations and wrong-answer analysis, never real exam questions or exam dumps. Learn why practice questions differ from exam dumps →

How Courseiva writes practice questions · Editorial policy

JA

Written by Johnson Ajibi, MSc IT Security

Senior Network & Security Engineer · founder of Courseiva

This ACE 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 ACE exam.