Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud DevOps Engineer practice bank has 1,455 more like it. Try 10 free: instant score, no account.
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:
ERROR severity entries occurred relative to normal traffic.Which workflow within Logs Explorer should you execute to diagnose and trace this failure?
This option suggests using Log Scope boundaries, searching for payload text summaries, and filtering by the spanId field to trace requests across microservices.
spanId represents a single segment or sub-operation within a trace. While a trace ID remains constant across all microservices involved in handling a single external request, each service or hop generates a distinct spanId. Filtering by a single spanId isolates only that specific sub-operation, missing the upstream and downstream cascading log events.spanId scopes to a local execution unit or RPC call.trace scopes to the entire distributed transaction graph across all involved microservices.You were isolating the exact execution duration of a single local database query or remote procedure call that had already been pinpointed within a distributed trace.
This option involves switching between Cloud Monitoring Metrics Explorer, Error Reporting, and Logs Explorer to monitor aggregate error counts and group application exceptions.
trace) links all HTTP access logs, application messages, and proxy logs across distinct microservice boundaries.You were investigating an unhandled programming language exception or uncaught runtime panic that occurred in a single monolithic backend service.
This option relies on routing logs to BigQuery via a Log Router sink and running analytical SQL queries to compute aggregations and correlate log records.
insertId: The insertId field is a unique per-entry identifier assigned by Google Cloud Logging to deduplicate individual log lines. It is unique to a single log entry and cannot be used to trace multi-step request paths across multiple services.insertId guarantees entry uniqueness and prevents duplicate ingestion, whereas trace represents the distributed transaction ID.You needed to perform an extensive post-incident review across months of log data using complex relational joins, aggregations, and long-term trend analysis.
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.
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 Validated