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 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:
InventoryService.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?
Database storage saturation occurs when a managed database instance exceeds its allocated storage boundaries or throughput capacity limits, causing the storage subsystem to throttle write operations and transaction commit logs.
spanner.googleapis.com/instance/storage/utilization rather than client thread blocking.The span metadata revealed that actual query execution or two-phase commit phases took several seconds while storage utilization metrics were approaching 100% capacity.
VPC network delays occur when transit hops, firewall processing, or cross-region network congestion cause transmission delays between compute instances and Google Cloud managed service APIs.
FirstByteLatency / network transmission span).The span attributes indicated low client acquisition wait times and low Spanner execution times, but high network round-trip latency and elevated TCP retransmissions.
Cloud Trace ingestion quota limits apply when an application emits more trace spans per second or month than allowed by the project quota, leading to HTTP 429 response codes on the cloudtrace.googleapis.com API.
serviceruntime.googleapis.com/api/request_count with response_code = 429 for cloudtrace.googleapis.com.The issue was missing child spans or unrecorded transactions in Cloud Trace accompanied by 429 errors from the trace exporter.
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.
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