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 backend running on Google Cloud experiences periodic latency spikes during high-traffic sales events. When inspecting distributed trace waterfalls in Cloud Trace, the DevOps team identifies an elongated span corresponding to a database query operation within the ordering service.
You need to correlate this trace span with Cloud Logging entries and Cloud Monitoring metrics to determine whether the latency spike is caused by unoptimized application query logic or infrastructure-level resource constraints.
Which diagnostic workflow should you use?
compute.instances.hostError audit logs and run netstat -s on the database virtual machine to monitor TCP socket buffer overruns.This option searches Google Cloud Audit logs for Compute Engine host maintenance or system error events and evaluates Linux network socket buffer drops using operating system utilities.
compute.instances.hostError or compute.instances.OnHostMaintenance helps diagnose VM-level restarts, it does not analyze query execution performance or distinguish application SQL logic from memory contention.netstat -s requires direct operating system shell access, which is typically restricted or unavailable on managed database platforms like Cloud SQL.The trace waterfall revealed dropped inter-VM network connections or unexpected virtual machine restarts across raw Compute Engine instances during maintenance windows.
traceparent context header with custom StatsD agent metrics in Cloud Monitoring.This option modifies the service mesh configuration to replace standard W3C traceparent headers with custom StatsD agent metrics.
traceparent, x-cloud-trace-context, or x-b3-traceid) breaks the distributed trace graph, preventing Cloud Trace from linking spans across services.The application required exporting custom runtime business counters via a legacy third-party monitoring daemon rather than diagnosing trace waterfall latency.
httpRequest.cacheLookup=true, and scale the Cloud SQL database tier to Large to bypass infrastructure metrics analysis.This option filters Cloud Logging for CDN cache status fields (httpRequest.cacheLookup) and attempts to resolve latency by immediately increasing the database tier without root-cause validation.
httpRequest.cacheLookup and httpRequest.cacheHit fields are specific to Cloud CDN and external Application Load Balancer logs, which do not correlate with internal microservice database query spans.The latency were occurring on static frontend web assets served via Cloud CDN where cache miss rates needed evaluation against backend load.
This diagnostic approach correlates distributed tracing with Cloud Logging and Cloud Monitoring by linking the trace identifier across system logs and analyzing detailed resource consumption metrics in Cloud SQL Query Insights.
trace and spanId fields in structured log entries. Filtering logs by the trace ID from the slow waterfall span surfaces exact query timestamps, application context, and runtime warnings.tempdb), causing the span latency observed in Cloud Trace.This workflow systematically leverages native GCP observability integrations to disambiguate software inefficiencies from hardware resource bottlenecks without requiring intrusive manual debugging.
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