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.
A DevOps team is establishing automated cost governance for a sandbox Google Cloud project to prevent runaway expenses. The solution must satisfy the following technical and operational requirements:
Which configuration should the DevOps engineer implement?
MonitoringRule custom resource using PromQL expressions targeting invoice metrics, and configure an HTTP webhook notification channel pointing to the remediation runbook.A MonitoringRule custom resource is used in Google Distributed Cloud (GDC) environments to configure Prometheus/PromQL-based alerting rules against invoice line items and metering data in air-gapped or private cloud deployments.
MonitoringRule custom resources are specific to Google Distributed Cloud (GDC) and are not the standard management mechanism for public Google Cloud project billing budgets.sum(metering_invoice_line_item_total_cost...)) rather than using managed Cloud Billing budget objects.The workload were running inside a Google Distributed Cloud (GDC) air-gapped appliance where standard Google Cloud Billing APIs and Pub/Sub integrations could not be reached.
This configuration sets up a Cloud Billing budget with an attached Cloud Pub/Sub topic but deliberately removes all threshold alert rules in an attempt to suppress email notifications.
alertThresholdExceeded or forecastThresholdExceeded.The downstream Cloud Function was designed to manually calculate billing percentages from raw dollar values and the organization strictly prohibited the budget service from managing threshold evaluation logic.
Google Cloud Billing budgets allow organizations to track resource costs against defined monetary targets. When coupled with Cloud Pub/Sub, budget alerts become programmatic triggers that publish real-time budget status messages as structured JSON objects, enabling serverless automation like Cloud Functions or Cloud Run to act as automated remediation runbooks.
>100%) allows the system to extrapolate current consumption trends out to the end of the calendar month and trigger alerts before the allocation is fully depleted.google.billing.v1.CloudBilling).alertThresholdExceeded and forecastThresholdExceeded fields for downstream parsing.costAmount, budgetAmount, and current billing period dates.Cloud Billing budgets do not natively cap infrastructure or enforce hard billing limits out of the box. Using Pub/Sub programmatic notifications with threshold rules is the official, Google-recommended pattern for building automated cost capping, shutdown runbooks, and proactive alerting pipelines.
This option proposes relying on a built-in automated hard cap within the Cloud Billing budget user interface to stop resources once the budget amount is reached.
Google Cloud Billing featured an out-of-the-box infrastructure kill-switch setting within the budget configuration GUI that required no external message queue or serverless execution environment.
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