Professional Cloud DevOps Engineer
Prepare and test your skills
Prepare and test your skills
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 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?
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.