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 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?
This solution establishes a comprehensive FinOps and APM optimization architecture by combining application-level telemetry control with Google Cloud billing automation and metadata governance.
team, cost_center, service) via Terraform and exporting Cloud Billing data to BigQuery allows organizations to build detailed Looker Studio reports that break down observability and infrastructure costs by team.This approach directly targets the source of high APM costs (unbounded custom span generation) without eliminating diagnostic capabilities, while leveraging native Google Cloud billing analytics tools to create transparent, automated chargeback reporting.
This option completely disables custom in-process trace instrumentation, redirects Cloud Audit Logs into Cloud Storage buckets, and attempts to use Cloud Monitoring Uptime Checks for financial tracking.
The organization only required high-level availability monitoring for public websites with zero budget for custom distributed tracing or detailed APM analytics.
This option increases Prometheus metric scraping intervals to lower metric ingestion volume, forces continuous profiling across all container instances, and suggests using the Pricing Calculator for billing chargebacks.
The primary goal was adjusting Prometheus metric storage costs and manually forecasting annual capacity budgets for static infrastructure.
This option attempts to filter distributed trace spans through Cloud Logging sinks, sets BigQuery query quotas to limit ingestion, and builds log-based metric alerting using unspecified resource scopes.
The workload was suffering specifically from runaway interactive BigQuery query costs run by data analysts rather than APM observability spend.
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