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 online retail platform running microservices on Google Kubernetes Engine (GKE) with Cloud Service Mesh triggers an alert due to a violation of its user-facing latency Service Level Objective (SLO).
A DevOps engineer investigates the incident in Cloud Monitoring Metrics Explorer and correlates the following multi-dimensional golden signal metrics across tiers:
https/total_latencies at the 95th percentile, with steady request volume.How should the DevOps engineer interpret these correlated metrics to identify the root cause of the degradation?
This option assumes that internal DNS or ServiceEntry resolution failures inside the mesh caused sidecars to fail connection routing, leading the load balancer to designate backend targets as INVALID_BACKEND.
NR for No Route) and immediate connection termination.Sidecar logs reported immediate DNS or NR lookup errors, the external load balancer returned INVALID_BACKEND, and backend CPU utilization remained near idle.
This option posits that an unhandled surge in inbound client requests overwhelmed the service mesh ingress layer, causing load balancing failures and misreported infrastructure saturation metrics.
https/request_count / Traffic), ruling out an unmanaged external traffic spike.NO_BACKEND_SELECTED or 503 Service Unavailable generated at the gateway, with a collapse or drop in backend CPU utilization as traffic fails to reach the backend.Traffic metrics demonstrated an exponential surge in request rate preceding the CPU saturation and latency spikes across all intermediary gateways.
Correlating golden signals across architectural boundaries allows engineers to trace the causal relationship between underlying infrastructure constraints and user-facing SLO degradation. When analyzing multi-tier distributed applications, saturation metrics (such as container CPU utilization) often represent the foundational catalyst for downstream performance anomalies.
https/total_latencies on the external load balancer.RESPONSE_FLAGS and upstream status codes with workload CPU reveals whether the proxy layer or application backend is failing.Analyzing telemetry in a structured top-down or bottom-up flow—connecting saturation, error rate, and latency—establishes a definitive causal chain. This accurately targets remediation efforts (such as horizontal pod autoscaling or query optimization) directly at the backend microservice.
This option presumes that a network bottleneck occurred at the Google Front End (GFE) proxy or client connection level, causing connection backpressure to propagate backward through the service mesh and overload backend processors.
https/total_latencies measures the time between when the proxy receives the request and when it finishes sending the response, including backend processing time. Frontend client round-trip time (RTT) is tracked separately via frontend RTT metrics.FRONTEND_5xx), not localized backend pod CPU exhaustion.Frontend RTT metrics showed massive anomalies while backend service latencies and CPU utilization remained healthy and low.
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