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.
Your enterprise runs a distributed microservices platform on Google Kubernetes Engine (GKE) configured with Cloud Service Mesh using a managed control plane. You are tasked with instrumenting telemetry to capture distributed traces and proxy access logs across all communicating services, exporting them directly to Google Cloud Observability.
During implementation, your team needs to ensure all mesh workloads send telemetry without conflicting configurations across application namespaces. What should you do?
Telemetry custom resources specifying the stackdriver provider in every workload namespace.This option attempts to configure distributed tracing and proxy telemetry at the individual namespace level by creating multiple Telemetry custom resources across different application namespaces.
In Cloud Service Mesh with a managed control plane, namespace-scoped or multiple Telemetry custom resources are not supported for mesh configuration. When multiple Telemetry custom resources are deployed across different namespaces in a managed control plane cluster, only the first resource applied takes effect, while subsequent namespace-scoped configurations are ignored.
You were running an unmanaged, self-hosted in-cluster Istio deployment where namespace-level and workload-level Telemetry custom resources are fully evaluated hierarchically.
This option deploys an OpenTelemetry Collector DaemonSet on each node and uses Pod annotations to scrape Prometheus metrics and receive exported telemetry.
While open-source telemetry collectors can be deployed in Kubernetes, Cloud Service Mesh proxies natively integrate with Google Cloud Observability APIs for trace collection and proxy logging. Setting up an unmanaged OpenTelemetry DaemonSet adds infrastructure management overhead and does not leverage the native managed telemetry configuration supported by Cloud Service Mesh.
Telemetry CR.You were required to export all telemetry out of Google Cloud to an external, on-premises observability backend or a third-party APM vendor requiring an OpenTelemetry collector pipeline.
EnvoyFilter resource in each workload namespace to inject custom Lua filters that push metrics and traces to Cloud Logging.This option attempts to use the low-level EnvoyFilter networking API and custom Lua scripts to intercept proxy traffic and push custom log and trace payloads to Google Cloud.
Using EnvoyFilter with custom Lua scripting is an anti-pattern for standard telemetry collection in Cloud Service Mesh. The Telemetry API already provides high-level, declarative, and first-party native integration with Google Cloud Observability. Custom Lua scripting introduces unnecessary complexity, higher proxy CPU overhead, and potential breakage during control plane version upgrades.
EnvoyFilter patches can break across Envoy and control plane version updates.stackdriver provider.You had a specialized requirement to transform proprietary HTTP headers or redact custom payload elements before logs leave the proxy that could not be achieved via the standard Telemetry API.
Telemetry custom resource referencing the stackdriver provider in the root istio-system namespace.The Istio Telemetry API (telemetry.istio.io/v1alpha1) allows administrators to configure distributed tracing, access logging, and metrics collection for Envoy proxies across the service mesh.
istio-system).stackdriver provider within the root Telemetry custom resource instructs all Envoy sidecar proxies to export distributed tracing and access telemetry directly to Google Cloud Observability (Cloud Trace and Cloud Logging).istio-system prevents conflicts caused by multiple custom resources, ensuring consistent telemetry behavior across all workloads.Deploying a single Telemetry resource in istio-system aligns with Google Cloud architecture best practices for managed control planes, avoiding ignored configurations while ensuring seamless distributed trace collection across microservices.
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