You configure a GCP budget with alert thresholds at 50%, 90%, and 100% of the budget amount. What happens when your spending reaches 90% of the budget?
Think about how alert thresholds work in GCP budgets.
GCP budget alerts notify you when spending reaches or exceeds configured thresholds. Since 90% is one of the thresholds, an alert is sent at that point.
You want to receive email notifications when your GCP budget reaches 80% and 100%. Which configuration correctly sets these alert thresholds?
Alert thresholds are decimal fractions representing percentages.
GCP budget alert thresholds are decimal values between 0 and 1 representing percentages. 0.8 means 80%, 1.0 means 100%. The email must be added under notifications to receive alerts.
You want to ensure only specific team members can create or modify budget alerts in your GCP project. Which IAM role should you assign to those team members?
Consider which role allows managing billing and budgets.
The roles/billing.admin role grants permissions to create and modify budgets and billing accounts. Other roles like viewer or billing.user do not have full budget management rights.
You manage multiple GCP projects and want to track combined spending with budget alerts. What is the best approach to configure this?
Think about how billing accounts relate to projects.
A single budget at the billing account level can include multiple projects, allowing combined spending tracking and alerts. Separate budgets per project do not provide combined totals automatically.
Your team receives too many budget alert emails for minor spending fluctuations. Which configuration change best reduces notification noise while keeping important alerts?
Consider how threshold levels affect alert frequency and automation options.
Raising alert thresholds reduces frequent minor alerts. Using Pub/Sub notifications enables automated handling, reducing email noise. Lowering thresholds or disabling alerts increases noise or risk.