Courseiva
mediumMultiple ChoiceObjective-mapped

Google ACE Practice Question: A Go service is consuming significantly more CPU…

A Go service is consuming significantly more CPU than expected. The team suspects an inefficient function but doesn't know which one. Which Cloud Operations tool identifies CPU hotspots in production code?

⚠ Common exam trap

Google Cloud often tests the distinction between latency-focused tools (Trace) and resource-usage-focused tools (Profiler), and the trap here is that candidates confuse 'slow function' (latency) with 'CPU-hungry function' (resource consumption), leading them to pick Cloud Trace instead of Cloud Profiler.

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 Profiler

Cloud Profiler is the correct tool because it continuously gathers CPU and heap usage data from production services using statistical sampling, then presents a flame graph or call tree that pinpoints which functions consume the most CPU. Unlike debugging or tracing tools, Profiler is designed specifically for identifying performance bottlenecks like CPU hotspots with minimal overhead, making it ideal for diagnosing an inefficient function in a Go service running in production.

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 Debugger

    Why it's wrong here

    Cloud Debugger is meant for inspecting live application state by setting snapshots or log points at specific lines of code, which pauses execution only for that snapshot. It has no sampling profiler and cannot attribute CPU consumption to individual functions over time, so it is not the tool for CPU profiling.

  • Cloud Trace

    Why it's wrong here

    Cloud Trace is a distributed tracing tool that measures latency of requests as they flow through services, producing trace spans and waterfall diagrams. While it can highlight slow operations and service boundaries, it does not sample CPU usage or map CPU time to the internal functions of a single process, so it cannot pinpoint which function burns CPU.

  • Cloud Profiler

    Why this is correct

    Cloud Profiler is the correct choice because it continuously samples production applications with low overhead, recording call stacks and generating flame graphs. Those flame graphs visually rank functions by CPU utilization, letting you identify exactly which code paths consume the most CPU even in a distributed environment.

  • Cloud Monitoring custom dashboards

    Why it's wrong here

    Cloud Monitoring custom dashboards are aggregates of metric time series like system CPU utilization, memory, or request counts, viewed per resource or group. They lack the per-function call-stack granularity needed to see which internal functions are eating CPU, so they only show high-level resource usage, not code-level hotspots.

Go deeper

Related to this question

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 →

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.