You are building an application that uses a distributed microservices architecture. You want to measure the performance and system resource utilization in one of the microservices written in Java. Wha

Question

Options

• AInstrument the service with Cloud Profiler to measure CPU utilization and method-level execution
• BInstrument the service with Debugger to investigate service errors.
• CInstrument the service with Cloud Trace to measure request latency.
• DInstrument the service with OpenCensus to measure service latency, and write custom metrics to

• A
  84% (41)
• B
  2% (1)
• C
  4% (2)
• D
  10% (5)

Explanation

Cloud Profiler is a statistical, always-on profiling service that continuously collects CPU and heap memory usage data and attributes it to specific methods and call stacks in the application code. It is purpose-built for performance analysis and supports Java natively. Option B (Cloud Debugger) captures application state at specific code locations to help debug errors - it does not measure performance. Option C (Cloud Trace) tracks distributed request latency across services but does not provide method-level CPU profiling. Option D (OpenCensus) can capture custom metrics and latency, but does not provide the automatic, low-overhead method-level CPU profiling that Cloud Profiler delivers out of the box.

No community discussion yet for this question.