Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
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 platform running a microservices architecture on Google Kubernetes Engine (GKE) with Cloud Service Mesh experiences intermittent HTTP 500 errors and latency spikes during peak shopping periods.
The operations team must determine whether the failures originate from proxy routing issues or unhandled application code exceptions, while also identifying latency bottlenecks across downstream microservice calls.
Which systematic diagnostic procedure should the team use to isolate the root cause?
Google Cloud Observability—encompassing Cloud Logging, Cloud Trace, and Error Reporting—provides a unified telemetry framework designed to diagnose distributed systems. In service mesh environments, sidecar and ingress proxies generate structured access logs, application runtimes report exceptions, and distributed tracing tracks RPC latencies across microservice boundaries.
StudyCerts
StudyCertsRESPONSE_FLAGS (e.g., UF for upstream connection failure, UT for upstream timeout) and RESPONSE_CODE. When RESPONSE_FLAGS is empty or unset (-) while RESPONSE_CODE is 500, the error originates directly from the backend application rather than proxy-level routing.This multi-tiered observability approach systematically addresses every level of the failure domain—infrastructure and networking at the proxy layer, application logic via error reporting, and inter-service performance via distributed tracing.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.