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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An e-commerce organization runs a distributed microservices application on Google Kubernetes Engine (GKE) managed with Cloud Service Mesh. Following a recent canary deployment, operations teams notice a distinct performance regression: overall transaction latency has doubled, and node CPU consumption has surged across backend workloads.
To remediate the issue and optimize the resource footprint before completing the rollout, the cloud architect needs to correlate end-to-end telemetry with granular code-level execution details.
Which approach should the architect use to diagnose the regression and identify the specific performance bottleneck?
Review proxyless gRPC environment variables in pod specifications, verify the GRPC_XDS_BOOTSTRAP path, and update Prometheus exporters across all client deployments
Inspect the istiod control plane logs using kubectl logs in the istio-system namespace, then double the GKE node pool instance count to absorb the increased CPU load
Use Cloud Trace and Cloud Service Mesh telemetry to identify the downstream service experiencing elevated round-trip times, then inspect Cloud Profiler flame graphs for that service to isolate CPU-intensive code paths introduced in the new release
Execute istioctl analyze -A across all cluster namespaces to detect mesh misconfigurations, then apply namespace label updates to adjust sidecar proxy CPU limits
Review proxyless gRPC environment variables in pod specifications, verify the GRPC_XDS_BOOTSTRAP path, and update Prometheus exporters across all client deployments
Inspect the istiod control plane logs using kubectl logs in the istio-system namespace, then double the GKE node pool instance count to absorb the increased CPU load
Use Cloud Trace and Cloud Service Mesh telemetry to identify the downstream service experiencing elevated round-trip times, then inspect Cloud Profiler flame graphs for that service to isolate CPU-intensive code paths introduced in the new release
This diagnostic strategy combines macro-level distributed tracing and mesh telemetry with micro-level continuous code profiling. Cloud Trace and Cloud Service Mesh provide visibility into distributed inter-service communication, while continuous code profiling measures CPU utilization and memory allocations at the function level inside running application containers.
Correlating service-level distributed telemetry with code profiling provides complete observability from the request lifecycle down to the CPU instruction level. This avoids guesswork and prevents unnecessary infrastructure over-provisioning.
Execute istioctl analyze -A across all cluster namespaces to detect mesh misconfigurations, then apply namespace label updates to adjust sidecar proxy CPU limits
StudyCerts
StudyCerts