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.
A DevOps engineer is troubleshooting missing telemetry and latency metrics in the Cloud Service Mesh dashboard for a microservice deployed on Google Kubernetes Engine (GKE). The mesh uses a managed control plane with distroless Envoy sidecar proxy containers.
The engineer suspects that the Envoy sidecar failed to receive its telemetry filter configuration from the control plane. However, executing kubectl exec directly into the istio-proxy container to run diagnostic commands fails because the distroless proxy image lacks utilities like curl and bash.
What should the engineer do to inspect the Envoy proxy configuration dump and verify that the telemetry filter is active?
Cloud Service Mesh sidecars frequently run on distroless container images to reduce attack surfaces and optimize container startup times. Because distroless images omit system utilities such as curl, sh, and bash, operators cannot execute interactive commands directly inside the container using standard kubectl exec workflows. Instead, Kubernetes provides ephemeral debug containers via kubectl debug, which attach a temporary container sharing the target container's process and network namespace.
By executing kubectl debug --image istio/base --target istio-proxy -it -n curl localhost:15000/config_dump, the engineer attaches a container containing essential networking tools (istio/base) directly to the istio-proxy container. This enables querying Envoy's local administration interface on port 15000 to extract the full active configuration dump. The engineer can then inspect the output specifically for the presence and configuration of the Google Cloud Observability filter (stackdriver or Google Cloud metrics filter).
localhost:15000.This approach directly solves the diagnostic limitation imposed by distroless containers while providing real-time visibility into Envoy's active filters without modifying deployment manifests or breaking security baselines.
Configuring Kubernetes Service ports without an explicit http- or grpc- prefix (or explicitly configuring them as raw TCP byte streams) causes Envoy to treat traffic strictly at Layer 4 (L4) rather than Layer 7 (L7).
The application utilized an unsupported Layer 7 protocol (such as Kafka, Cassandra, or raw database connections) that required raw Layer 4 TCP byte-stream pass-through.
The Istio Telemetry API provides declarative Custom Resources (Telemetry CRs) to configure access logging, metrics collection, and tracing behavior across workloads within the service mesh.
Telemetry custom resource in the root namespace (istio-system) is supported. Deploying multiple namespace-level or workload-level Telemetry CRs will result in secondary configurations being ignored.Telemetry CRs across multiple namespaces can prevent intended telemetry definitions from propagating correctly.Telemetry CRs if one is already deployed.localhost:15000 administration endpoint on the proxy.The goal was to configure global mesh-wide trace sampling or access log formatting across a self-managed in-cluster control plane supporting multiple hierarchical Telemetry CR definitions.
Querying Logs Explorer for trafficdirector.googleapis.com/events provides control plane audit and status logs detailing xDS client connection states, stream handshakes, node disconnections, and cross-region routing metadata.
/config_dump) or data-plane filter chains active on the sidecar.The engineer needed to verify whether xDS clients were rejecting discovery responses due to corrupted communication or missing interception port metadata (TRAFFICDIRECTOR_INTERCEPTION_PORT).
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