Google ACE Practice Question: Ensuring Successful Operation of a Cloud Solution
You need to collect and analyze latency traces for a microservices application running on GKE. You want to identify which services are contributing to overall latency. Which Google Cloud service should you enable and use?
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 a distributed tracing service that collects latency data from applications and provides tools to analyze performance bottlenecks.
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
Why it's wrong here
Cloud Logging centralizes log data from applications and services, allowing you to search, filter, and view log entries, but it does not natively correlate logs into request-level latency traces. Without trace context propagation, you cannot see the hierarchical sequence of spans across microservices or the duration of each downstream call. Even if you embed latency numbers in log messages, you lose the automatic parent-child relationships and waterfall visualization that Cloud Trace provides.
- ✗
Cloud Profiler
Why it's wrong here
Cloud Profiler performs continuous, low-overhead statistical profiling to show CPU and memory consumption per function or method within a service, helping identify performance bugs and inefficiencies. However, it is per-process and does not follow a request across service boundaries, nor does it record the time spent in each microservice call along the path. Therefore Profiler cannot produce the distributed latency breakdown needed to analyze microservice trace data.
- ✗
Cloud Monitoring
Why it's wrong here
Cloud Monitoring ingests time-series metrics, creates dashboards, and triggers alerts based on thresholds, and it can display aggregated latency metrics like p50 or p99 for services. Yet these metrics are aggregated and cannot reconstruct an individual request's path or show exactly which downstream service introduced the delay. For granular, per-request span analysis with causal dependencies, Cloud Trace is required rather than a metrics-only view.
- ✓
Cloud Trace
Why this is correct
Cloud Trace is the Google Cloud service specifically designed for distributed tracing: it captures spans from instrumented applications or via OpenTelemetry, groups them into traces for each request, and renders a waterfall view showing where time is spent across microservices. It supports latency distribution analysis, allows comparison of recent traces, and can identify bottleneck services and anomalously slow requests. Thus it directly answers the need to collect and analyze latency traces.
Go deeper
Related to this question
Learn chapter
Google Cloud Platform Overview
Key term
Service
A service is a software component or system that performs a specific function and is available to be used by other programs or users over a network.
Key term
Trace
A trace is a record of the path and timing of a request or operation as it moves through components in a system, used to monitor performance and troubleshoot issues.
About these practice questions
Courseiva writes every ACE question from scratch — 769 in total, each with an explanation and a wrong-answer breakdown. None are copied from real exams or dumps. Learn why practice questions differ from exam dumps →
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.