Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Associate Cloud Engineer practice bank has an additional 2,014 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
Your operations team is deploying applications to several Google Kubernetes Engine (GKE) clusters and needs to collect Prometheus metrics. The team wants a solution that minimizes administrative overhead by eliminating the need to manually scale, shard, or maintain Prometheus servers. Additionally, they require a fully supported Google Cloud experience that configures scraping through lightweight Kubernetes custom resources.
Which collection mode should you choose for Google Cloud Managed Service for Prometheus?
The Google Cloud Ops Agent is the primary telemetry collection agent installed directly on virtual machine operating systems within Compute Engine. It combines metric and log collection into a unified daemon and features built-in support to discover and scrape Prometheus exporters hosted on individual virtual machines.
PodMonitoring or ClusterPodMonitoring to discover dynamic container endpoints.This option would be correct if the scenario involved monitoring legacy enterprise applications running on standalone Compute Engine virtual machines that expose Prometheus metrics endpoints, rather than containerized microservices hosted on GKE.
Although the Ops Agent is the recommended solution for Compute Engine virtual machine monitoring, GKE environments have dedicated native collection mechanisms that integrate directly into Kubernetes API machinery.
Google Cloud Managed Service for Prometheus (GMP) offers managed collection as Google's recommended approach for Kubernetes environments, including Google Kubernetes Engine (GKE). In this mode, an in-cluster Kubernetes operator (gmp-operator) deploys and oversees collection infrastructure automatically, drastically reducing the day-to-day operational burden of monitoring containerized environments.
PodMonitoring and ClusterPodMonitoring.
prometheus-operator configurations.For Kubernetes workloads on GKE, managed collection provides the ideal balance between native Prometheus compatibility and cloud-managed simplicity. Unlike self-deployed alternatives that require manual capacity planning and infrastructure maintenance, managed collection automates operational toil while retaining complete support from Google Cloud engineers.
Self-deployed collection allows organizations to retain full ownership over their Prometheus deployment while using a drop-in binary replacement provided by Google Cloud Managed Service for Prometheus. Instead of upstream Prometheus writing to local disk, the custom binary streams scraped data to Google Cloud's managed backend while preserving traditional Prometheus configurations.
This approach would be the right choice if your organization had a complex, legacy Prometheus installation that heavily relies on existing upstream configurations or requires specialized capabilities like local metric aggregation to control cardinality before sending metrics to Google Cloud.
While self-deployed collection is valuable for gradual migrations or specialized setups running alongside upstream Prometheus, it re-introduces the maintenance complexity that fully managed GKE collection was designed to eliminate.
The OpenTelemetry Collector is a vendor-agnostic, open-source proxy agent capable of receiving, processing, and exporting telemetry data across multiple signals, including metrics, logs, and distributed traces. When integrated with Google Cloud Managed Service for Prometheus, it can scrape Prometheus endpoints using a Prometheus receiver and forward metrics to Cloud Monitoring.
PodMonitoring custom resources.The OpenTelemetry Collector would be the appropriate choice if your organization implemented a unified single-agent observability strategy requiring the simultaneous capture of distributed traces, application logs, and Prometheus metrics across hybrid cloud or multi-cloud environments.
While the OpenTelemetry Collector provides great power for cross-signal correlation and multi-cloud tracing, choosing it solely for standard Prometheus metric collection on GKE introduces unnecessary configuration overhead compared to managed collection.
Answer them yourself and get your score the moment you finish. No account needed.
Full access includes
Keep the momentum going with these hand-picked practice scenarios
Last updated