A retail enterprise manages dozens of Google Cloud projects across multiple autonomous development teams. To implement FinOps governance, the central FinOps team needs to enforce cost allocation by ensuring all new resources are tagged with required environment and cost-center labels. Additionally, they want to establish proactive threshold alerts when project expenditures reach 80% and 100% of budgeted limits without abruptly interrupting running production workloads. Which architectural approach best meets these cost governance requirements?
- Enforce mandatory resource labeling using Organization Policies with tag/label constraints, and configure Cloud Billing budgets with threshold rules at 80% and 100% sending email and Pub/Sub notifications.Cevap
- BAssign the Owner primitive IAM role to project leads so they can manually audit resource tags, and set hard quotas that terminate virtual machines when budget thresholds are reached.
- CPurchase 3-year standard Committed Use Discounts across all resources to cap monthly spending, and set up Cloud Monitoring metric alerts for CPU utilization.
- DDeploy a dedicated GKE cluster running custom scripts that continuously poll project resources and immediately delete any untagged resources upon detection.
Cevap
Enforce mandatory resource labeling using Organization Policies with tag/label constraints, and configure Cloud Billing budgets with threshold rules at 80% and 100% sending email and Pub/Sub notifications.
Combining GCP Organization Policies for tag enforcement with Cloud Billing budget threshold alerts provides automated governance and cost visibility. Organization policies natively block non-compliant provisioning, while Cloud Billing budgets inform teams at 80% and 100% thresholds without risking unexpected production service outages.
Adım Adım Çözüm
Anahtar Kavram
FinOps Governance: Resource Labeling Enforcement and Billing Budget Alerts
Tahmini Süre:1m 30s