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 has deployed Google Cloud Managed Service for Prometheus using managed collection on a Google Kubernetes Engine (GKE) cluster. You need to confirm that application targets are healthy and actively sending metrics by evaluating the standard up metric using Prometheus Query Language (PromQL). In addition, you want to view the resulting time-series chart directly within the Google Cloud console and add it to a custom dashboard.
What should you do?
kubectl port-forward session to the Prometheus server pod on port 9090, and access the local Expression Browser.kubectl port-forward DoesIn traditional self-managed Prometheus architectures, the Prometheus server hosts a built-in web interface called the Expression Browser. Operators commonly use kubectl port-forward to map a local workstation port to port 9090 of the Prometheus pod, enabling access to a simple web GUI for ad-hoc debugging and graphing.
localhost outside of the Google Cloud console.This approach would be suitable in an unmanaged, on-premises Kubernetes environment where external cloud services are unavailable and an engineer requires a temporary debugging session directly against a standalone Prometheus instance.
To use dedicated third-party dashboards with Managed Service for Prometheus, organizations typically connect Grafana using the Cloud Monitoring data source plugin or query frontend proxy, rather than relying on ephemeral local Expression Browsers.
up, and run the search.Cloud Logging Logs Explorer is a dedicated analysis interface in the Google Cloud console designed to search, filter, and inspect structured and unstructured log records. It operates using the Logging query language, which is optimized for querying text payloads, log fields, timestamps, and resource labels across collected log streams.
up into Logs Explorer will result in syntax errors.resource.type="k8s_container" AND textPayload =~ "error").This approach would be appropriate if you needed to search for stdout/stderr application error traces, debug container startup failures via Kubernetes container logs, or extract custom counter metrics from text logs using Log-based Metrics.
A common point of confusion is mixing the separate pillars of observability—metrics and logs. In Google Cloud Observability, metric analysis belongs in Cloud Monitoring (Metrics Explorer), while log record inspection belongs in Cloud Logging (Logs Explorer).
up, and execute the query.Google Cloud Managed Service for Prometheus automatically ingests metric data into Google's globally distributed time-series datastore, Monarch. Because it shares the backend storage architecture with Cloud Monitoring, Google provides native support for Prometheus Query Language (PromQL) directly inside the Google Cloud console. Within Cloud Monitoring, tools such as Metrics Explorer and dashboard chart builders allow engineers to query and visualize ingested Prometheus time series without needing to deploy or maintain self-hosted query engines.
up query immediately scans Monarch to return the health status of scraped targets. If targets are successfully reporting, the query evaluates to 1, generating an instant visual time-series chart.
Using Cloud Monitoring Metrics Explorer with the PromQL editor provides a serverless, out-of-the-box observability experience. It eliminates the overhead of managing local query infrastructure, simplifies verification of newly deployed workloads, and seamlessly integrates metric visualizations into persistent Cloud Monitoring dashboards.
promtool query instant up, and export the text stream to Cloud Monitoring.promtool and Pod Terminal Execution Doespromtool is an open-source command-line utility bundled with standard Prometheus installations. It is primarily used for offline linting of configuration files, validating Prometheus alerting rules, and performing ad-hoc instant queries against a locally running Prometheus HTTP server. Accessing a pod terminal involves using kubectl exec to enter a running container on a Google Kubernetes Engine (GKE) cluster.
promtool does not communicate with Cloud Monitoring APIs to generate dashboard widgets, store visualizations, or link to persistent charts.promtool running locally inside a pod cannot query global Monarch storage.pods/exec).This approach would be correct if a developer needed to perform automated CI/CD linting on Prometheus alerting rule YAML files or test rule syntax prior to committing changes to a Git repository.
In Google Cloud Managed Service for Prometheus, the query plane is centralized in the cloud backend. Querying individual cluster pods ignores the managed architecture that separates local scraping from global query evaluation.
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