nerdexam
Google

PROFESSIONAL-CLOUD-DEVOPS-ENGINEER · Question #143

You support an e-commerce application that runs on a large Google Kubernetes Engine (GKE) cluster deployed on-premises and on Google Cloud Platform. The application consists of microservices that…

The correct answer is A. Use Stackdriver Kubernetes Engine Monitoring. To identify containers consuming the most CPU and memory in a GKE cluster, use the built-in Stackdriver Kubernetes Engine Monitoring, which provides out-of-the-box metrics for container resource utilization.

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

Question

You support an e-commerce application that runs on a large Google Kubernetes Engine (GKE) cluster deployed on-premises and on Google Cloud Platform. The application consists of microservices that run in containers. You want to identify containers that are using the most CPU and memory. What should you do?

Options

  • AUse Stackdriver Kubernetes Engine Monitoring.
  • BUse Prometheus to collect and aggregate logs per container, and then analyze the results in
  • CUse the Stackdriver Monitoring API to create custom metrics, and then organize your containers
  • DUse Stackdriver Logging to export application logs to BigQuery, aggregate logs per container,

How the community answered

(19 responses)
  • A
    95% (18)
  • C
    5% (1)

Why each option

To identify containers consuming the most CPU and memory in a GKE cluster, use the built-in Stackdriver Kubernetes Engine Monitoring, which provides out-of-the-box metrics for container resource utilization.

AUse Stackdriver Kubernetes Engine Monitoring.Correct

Stackdriver Kubernetes Engine Monitoring (now part of Google Cloud Operations Suite) is the native and integrated solution in GKE that provides detailed metrics, including CPU and memory usage, for clusters, nodes, pods, and individual containers, allowing for easy identification of high-resource consumers.

BUse Prometheus to collect and aggregate logs per container, and then analyze the results in

Prometheus is primarily a metrics collection system, not a log aggregator, and therefore stating it collects 'logs per container' for CPU and memory usage is incorrect.

CUse the Stackdriver Monitoring API to create custom metrics, and then organize your containers

While the Stackdriver Monitoring API allows for custom metrics, CPU and memory utilization for containers in GKE are standard metrics already collected by Stackdriver Kubernetes Engine Monitoring, making custom metric creation unnecessary.

DUse Stackdriver Logging to export application logs to BigQuery, aggregate logs per container,

Stackdriver Logging and BigQuery are used for analyzing logs, not for directly monitoring real-time CPU and memory *metrics* of containers, which are distinct from log data.

Concept tested: GKE monitoring, container resource usage

Source: https://cloud.google.com/stackdriver/docs/solutions/gke/kubernetes-engine-monitoring

Topics

#GKE Monitoring#Container Monitoring#Resource Utilization#Cloud Monitoring

Community Discussion

No community discussion yet for this question.

Sign up to join the discussion
Full PROFESSIONAL-CLOUD-DEVOPS-ENGINEER Practice