Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
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?
GRPC_XDS_BOOTSTRAP path, and update Prometheus exporters across all client deploymentsConfiguring GRPC_XDS_BOOTSTRAP and OpenTelemetry environment variables (OTEL_RESOURCE_ATTRIBUTES) ensures that proxyless gRPC microservices can communicate with the Cloud Service Mesh control plane and export telemetry metrics properly to monitoring backends.
GRPC_XDS_BOOTSTRAP points gRPC clients and servers to the Traffic Director/Cloud Service Mesh control plane configuration.The microservices were completely failing to emit metric data or were reporting unknown topology attributes in the Cloud Monitoring and Cloud Service Mesh dashboards.
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.
istioctl analyze -A across all cluster namespaces to detect mesh misconfigurations, then apply namespace label updates to adjust sidecar proxy CPU limitsistioctl analyze Is and Doesistioctl analyze is a static configuration analysis tool that inspects live Kubernetes clusters or local configuration files for structural errors, missing resource definitions, and invalid Cloud Service Mesh / Istio custom resource definitions (such as missing namespace injection labels or broken VirtualService routing rules).
[IST0102] when namespace injection is omitted).The canary deployment completely failed to route traffic due to a misconfigured mesh routing manifest or missing sidecar proxy injection labels.
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 loadThis approach checks the istiod control plane logs for synchronization failures and attempts to mitigate elevated CPU utilization by horizontally scaling the underlying GKE compute infrastructure.
istiod) handles configuration distribution and certificate management; it does not process application data plane traffic or capture code-level regressions.istiod logs reveal control plane sync issues, validation webhook timeouts, and discovery errors, but lack application call-path data.The service mesh control plane was failing to push dynamic endpoint discovery updates to sidecars due to resource exhaustion on the istiod pods.
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