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 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?
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.This approach attempts to use logging and monitoring IAM roles and access scopes to stream trace payloads into Cloud Logging instead of using dedicated Cloud Trace APIs.
monitoring.write access scope authorizes Cloud Monitoring metric ingestion but does not provide authorization for the Cloud Trace API (trace.append).roles/logging.logWriter role does not grant trace publishing permissions (roles/cloudtrace.agent).The primary goal was centralized log aggregation where logs simply contain injected trace IDs for log-trace correlation in the Logs Explorer.
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.This configuration assigns an administrative API enablement role to workload service accounts, relies on Google Service Control infrastructure scopes, and attempts to route trace telemetry through BigQuery analytical sinks.
roles/serviceusage.serviceUsageAdmin) role allows enabling, disabling, and administering APIs across the GCP project. It violates the principle of least privilege and does not grant permissions to write trace data.servicecontrol scope is designed for internal Google service management communication and proxy integration, not for applications using OpenTelemetry SDKs to publish spans directly to Cloud Trace.You were automating infrastructure-as-code deployments to enable GCP APIs and establishing long-term offline analytical reporting pipelines for compliance auditing.
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.This configuration assigns read-oriented viewer permissions (roles/cloudtrace.user) to external service accounts, limits GKE node access to read-only platform APIs, and attempts to use OpenTelemetry Baggage instead of standard trace context propagation headers.
roles/cloudtrace.user) role provides read-only access to view and analyze traces in the Google Cloud console and API; it does not contain the cloudtrace.traces.patch permission required by application exporters to write span data.cloud-platform.read-only access scope explicitly prevents write operations, which will cause GKE workloads to fail when attempting to write telemetry spans to Cloud Trace endpoints.traceparent/tracestate) header mechanisms required to link distributed spans into a single trace graph.roles/cloudtrace.user is intended for human operators and dashboard tooling, not telemetry ingestion daemons.You were configuring a monitoring console dashboard or an external analytical reporting tool to query and visualize existing trace data without generating or exporting new traces.
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.This configuration establishes the necessary IAM authentication, platform authorization scopes, and OpenTelemetry context propagation protocols required to collect, stitch together, and export distributed traces to Google Cloud Trace from both Google Cloud Platform (GCP) and hybrid environments.
roles/cloudtrace.agent) IAM role, made discoverable through Application Default Credentials (ADC) via the GOOGLE_APPLICATION_CREDENTIALS environment variable or default file paths.https://www.googleapis.com/auth/trace.append scope to permit worker nodes to write telemetry spans to the Cloud Trace API endpoint.traceparent or B3) injected into and extracted from HTTP request headers to preserve Trace ID and Parent Span ID across network boundaries.roles/cloudtrace.agent role grants only the permissions needed to write trace data (cloudtrace.traces.patch), avoiding unnecessary administrative rights.This approach directly satisfies all security, networking, and tracing runtime constraints described in Google Cloud Observability best practices for hybrid deployments.
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