nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #91

Your company processes IoT data at scale by using Pub/Sub, App Engine standard environment, and an application written in Go. You noticed that the performance inconsistently degrades at peak load…

The correct answer is D. Configure Cloud Profiler, and initialize the cloud.google.com/go/profiler library in the application. Cloud Profiler is Google's managed continuous profiling service, purpose-built for identifying performance bottlenecks in production code. It integrates natively with Go via the 'cloud.google.com/go/profiler' library, has minimal CPU and memory overhead (designed for always-on…

Submitted by javi_es· Apr 18, 2026Implementing service monitoring strategies

Question

Your company processes IoT data at scale by using Pub/Sub, App Engine standard environment, and an application written in Go. You noticed that the performance inconsistently degrades at peak load. You could not reproduce this issue on your workstation. You need to continuously monitor the application in production to identify slow paths in the code. You want to minimize performance impact and management overhead. What should you do?

Options

  • AUse Cloud Monitoring to assess the App Engine CPU utilization metric.
  • BInstall a continuous profiling tool into Compute Engine. Configure the application to send profiling
  • CPeriodically run the go tool pprof command against the application instance. Analyze the results
  • DConfigure Cloud Profiler, and initialize the cloud.google.com/go/profiler library in the application.

How the community answered

(36 responses)
  • A
    3% (1)
  • B
    3% (1)
  • C
    11% (4)
  • D
    83% (30)

Explanation

Cloud Profiler is Google's managed continuous profiling service, purpose-built for identifying performance bottlenecks in production code. It integrates natively with Go via the 'cloud.google.com/go/profiler' library, has minimal CPU and memory overhead (designed for always-on production use), and requires no additional infrastructure. Option A (CPU metrics) reveals utilization but not which code paths are slow. Option B installs profiling on Compute Engine, which is irrelevant since the app runs on App Engine and adds management overhead. Option C (manual pprof) requires manual, periodic effort and is not continuous.

Topics

#Cloud Profiler#Continuous Profiling#Go#Application Performance Monitoring

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice