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 checkout flow spans three microservices instrumented with OpenTelemetry: frontend-service, payment-service, and inventory-service. Users intermittently experience 504 Gateway Timeout errors during high-traffic flash sales.
You examine Cloud Trace in the Google Cloud console and observe the following pattern on failing requests:
frontend-service: /checkout) has a duration of 30,000 ms.payment-service: /charge) executes concurrently and completes successfully in 250 ms.inventory-service: /reserve) remains active for 29,750 ms before returning an HTTP 500 error status.You need to isolate the critical path bottleneck and determine the root cause of the failure using integrated Google Cloud Observability tooling.
What should you do?
This option attempts to find error causes by executing broad, unindexed full-text queries across all container logs in Cloud Logging.
The application were completely uninstrumented with distributed tracing or lacked structured logging integrations.
payment-service: /charge) as the critical path bottleneck because financial transactions must complete first, and query Prometheus metrics for database lock contention.This option focuses troubleshooting on the payment-service based on an assumed business criticality rather than actual span duration data.
payment-service ignores the clear telemetry showing that inventory-service stalled the request and returned the 500 error.payment-service operated well within acceptable bounds.The payment span exhibited high latency or returned error codes, and the inventory span had completed instantaneously.
inventory-service: /reserve) as the critical path bottleneck, and navigate to the Logs & Events tab within the Trace details panel to inspect correlated log entries for the failing span.In distributed tracing, the critical path represents the sequence of dependent operations that determines the minimum total duration of the end-to-end transaction. When parent spans wait on child operations, the slowest sequential child span directly dictates the total latency. Using Google Cloud Trace, developers can drill down directly from a specific span in the Trace details panel to correlated application logs via the Logs & Events tab.
/charge finishes in 250 ms, /reserve consumes 29,750 ms of the 30,000 ms root span before timing out and failing, pinpointing inventory-service as the blocking bottleneck.trace_id and span_id contexts without manual querying.inventory-service that triggered the HTTP 500.This option assumes the issue stems from service mesh control plane management (istiod) rather than application or data plane behavior.
inventory-service and executed for 29,750 ms before returning an application-level HTTP 500 error.istiod manages configuration distribution, service discovery, and certificate issuance, not request-level database execution.Envoy proxies failed to receive cluster configuration updates or proxy discovery service (PDS/EDS) sync errors were occurring mesh-wide.
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