Cloud Trace Observability Finops Cost Governance

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 dozens of microservices across multiple Google Cloud projects managed by separate product engineering teams. During a recent financial review, the FinOps team discovered that observability spend has increased dramatically, driven by high volumes of custom Cloud Trace spans and untracked shared monitoring telemetry.

You need to establish a FinOps governance strategy that controls distributed tracing costs while preserving end-to-end performance diagnostic visibility, enables precise chargeback attribution to individual development teams, and provides proactive financial alerting.

Which combination of actions should you implement?

Increase Prometheus metric scraping intervals to 60 seconds, configure continuous 24/7 profiling across all pod replicas using Cloud Profiler, and use the Google Cloud Pricing Calculator to manually produce team chargeback invoices.

Configure exclusion filters in Cloud Logging log sinks for root trace spans, establish BigQuery project-level query quotas to cap telemetry ingestion, and create alert policies on log-based metrics with Unspecified Resource types.

Configure sampling and rate-limiting strategies in application OpenTelemetry tracers for custom spans, enforce standardized resource labeling via infrastructure as code, export Cloud Billing data to BigQuery to build Looker Studio chargeback dashboards, and configure Cloud Billing budget alerts.

Disable custom OpenTelemetry instrumentation across all services, rely exclusively on default platform traces, stream audit logs to Cloud Storage, and use Cloud Monitoring Uptime Checks to monitor monthly APM spend.

Professional Cloud DevOps Engineer

Cloud Trace Observability Finops Cost Governance

Related questions