Opentelemetry Cloud Trace Instrumentation Configuration

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.

Your DevOps team is instrumenting a distributed microservices application using OpenTelemetry SDKs to export span telemetry directly into Google Cloud Trace. Part of the application is deployed on a Google Kubernetes Engine (GKE) cluster configured with custom node access scopes, while legacy service components run in an on-premises data center.

All services must securely authenticate, correlate distributed calls, and successfully publish trace spans to Cloud Trace. Which configuration satisfies these requirements?

Assign the Cloud Trace User (roles/cloudtrace.user) role to the on-premises service account, configure GKE nodes with the https://www.googleapis.com/auth/cloud-platform.read-only scope, and configure OpenTelemetry to rely exclusively on custom baggage items for trace correlation.

Assign the Logs Writer (roles/logging.logWriter) role to the on-premises service account, configure GKE nodes with the https://www.googleapis.com/auth/monitoring.write scope, and export OpenTelemetry traces as JSON logs directly to Cloud Logging sinks.

Assign the Service Usage Admin (roles/serviceusage.serviceUsageAdmin) role to the on-premises service account, configure GKE nodes with the https://www.googleapis.com/auth/servicecontrol scope, and configure the OpenTelemetry SDK to write traces to BigQuery.

Assign the Cloud Trace Agent (roles/cloudtrace.agent) role to the on-premises service account using Application Default Credentials, ensure GKE nodes include the https://www.googleapis.com/auth/trace.append access scope, and configure OpenTelemetry context propagators for W3C TraceContext headers.

Professional Cloud DevOps Engineer

Opentelemetry Cloud Trace Instrumentation Configuration

Related questions