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 operates a hybrid cloud architecture comprising Google Cloud workloads and critical on-premises database clusters (such as Cassandra and Elasticsearch). You have been tasked with centralizing infrastructure and database metrics into Google Cloud Monitoring without modifying underlying application code.
After deploying BindPlane to collect telemetry from your on-premises servers, you observe that the volume of ingested metric data in Cloud Monitoring is exceeding budget thresholds. Your monitoring policy only requires performance metrics at a 5-minute granularity for standard operational dashboards, and several default component metrics are unnecessary for your operational alerting.
What should you do to optimize your hybrid metric pipeline and reduce ingestion costs?
Exporting telemetry via Cloud Logging sinks to BigQuery involves routing log records or event streams into analytical data warehouse tables where SQL queries can process, transform, and aggregate data.
You needed long-term analytical trend analysis and complex cross-system compliance reporting across months or years of historical operational log data.
OpenCensus is an open-source library and telemetry framework that allows developers to instrument application source code and export traces and metrics directly to various backends, such as the Cloud Monitoring API.
The goal was to write custom in-application business logic metrics or distributed tracing spans from custom microservices directly to the Monitoring API without utilizing an intermediary collector.
BindPlane is an OpenTelemetry-native telemetry pipeline and collector integrated with Google Cloud Observability that allows organizations to capture logs and metrics from hybrid, multi-cloud, and on-premises infrastructure into Google Cloud Monitoring without requiring direct code instrumentation.
external.googleapis.com or agent.googleapis.com namespaces in Cloud Monitoring.This approach directly targets the two primary levers for telemetry cost management in BindPlane—collection frequency and metric scope—while keeping the deployment fully configuration-based and compliant with the 5-minute reporting requirement.
Google Security Operations (SecOps) uses BindPlane agents and parsers to ingest syslog and security event data, normalizing raw logs into the Unified Data Model (UDM) for SIEM security analytics, threat detection, and event correlation.
The primary requirement was ingesting security audit logs from firewalls, identity providers, or proxy appliances into a centralized SIEM platform for security investigation.
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