Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
Worked example. The correct answer is already marked and every option is explained below, so there is nothing to select here. To answer questions yourself, start the free trial.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An e-commerce platform running a distributed microservices application on Google Kubernetes Engine with Cloud Service Mesh experiences cascading service timeouts and intermittent HTTP 503 errors across several dependent services.
As a DevOps engineer, you need to use Google Cloud's Logs Explorer diagnostic tools to:
StudyCerts
StudyCertsERROR severity entries occurred relative to normal traffic.Which workflow within Logs Explorer should you execute to diagnose and trace this failure?
Use the Log Scope selector to restrict logs to the Kubernetes cluster level; inspect the Log Search Summary pane to summarize payload strings; then use the spanId field to link all upstream and downstream service logs.
Inspect the Logs Histogram to identify the ERROR severity spike and drag over the time window to filter the range; use the Field Explorer to view the distribution of resource.labels.container_name and filter on the failing container; then select a failed log entry and filter by its trace field to view the correlated end-to-end request flow.
Navigate to Cloud Monitoring Metrics Explorer to chart log-based metric error counts; navigate to Error Reporting to group stack traces; then copy the Error Group ID into Logs Explorer to view all interrelated logs.
Configure a Log Router sink to export all logs to BigQuery; execute a SQL query grouping by severity and container name to isolate the error window; then query all logs sharing the same insertId across datasets.
Use the Log Scope selector to restrict logs to the Kubernetes cluster level; inspect the Log Search Summary pane to summarize payload strings; then use the spanId field to link all upstream and downstream service logs.
Inspect the Logs Histogram to identify the ERROR severity spike and drag over the time window to filter the range; use the Field Explorer to view the distribution of resource.labels.container_name and filter on the failing container; then select a failed log entry and filter by its trace field to view the correlated end-to-end request flow.
This workflow leverages the core diagnostic and analytical tools built natively into Google Cloud Logs Explorer: the Logs Histogram, the Log fields (Field Explorer) pane, and Distributed Tracing correlation using the trace context field.
DEFAULT, INFO, WARNING, ERROR, CRITICAL). Selecting or dragging across a specific bar or timeline segment zooms into that precise interval, automatically constraining the query time boundary.resource.labels.container_name or jsonPayload attributes, alongside counts and percentage distributions. Clicking on a high-error container name automatically appends the exact filter to the query editor.logging.googleapis.com/trace. Expanding a failed log entry and filtering by its trace field displays all chronologically ordered logs generated by every microservice participating in that specific transaction.This approach uses the integrated visual and indexing capabilities of the Logs Explorer interface directly, minimizing time to resolution (MTTR) during active incident troubleshooting.
Navigate to Cloud Monitoring Metrics Explorer to chart log-based metric error counts; navigate to Error Reporting to group stack traces; then copy the Error Group ID into Logs Explorer to view all interrelated logs.
Configure a Log Router sink to export all logs to BigQuery; execute a SQL query grouping by severity and container name to isolate the error window; then query all logs sharing the same insertId across datasets.