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.
An e-commerce checkout service deployed on Google Cloud experiences periodic latency spikes and intermittent transaction failures. While inspecting distributed trace waterfalls in Cloud Trace, a DevOps engineer observes the following behavior across slow requests:
StudyCerts
StudyCertsInventoryService.reserveStock shows normal execution time (40 ms), but its child span for Cloud Spanner database operations shows long duration (over 3,800 ms).serviceruntime.googleapis.com rate limiting warnings and thread pool exhaustion.What is the primary root cause indicated by this trace waterfall and span metadata analysis?
Client-side connection pool exhaustion occurs when application instances exhaust their configured maximum pool of database client sessions or TCP connections. In distributed tracing, this manifests as high total span latency for database operations even when the remote database itself executes queries swiftly.
db.connection_wait_ms vs db.execution_time_ms) pinpoints whether latency is in-flight or on-node.Evaluating span metadata and comparing individual child span durations against backend resource utilization is the definitive method to isolate client connection pool bottlenecks from true database performance degradation.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.