Intrigued by the art of cloud architecture? Discover how to design, develop, and manage robust, secure, scalable, and dynamic solutions on Google Cloud as you prepare for the Professional Cloud Architect exam!
Prepare and test your skills
Prepare and test your skills
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.
Keep the momentum going with these hand-picked practice scenarios
Want more questions like this?
Get a free certification question every week.
Last updated
An enterprise is planning to migrate its on-premises analytics workloads and applications to Google Cloud. Executive leadership requires an architectural and operational framework that ensures long-term financial sustainability and clearly demonstrates business value.
The enterprise has specified several core requirements:
Which strategy should the Cloud Architect recommend to satisfy these business and financial requirements?
Rely on centralized IT chargeback calculations derived from monthly consolidated invoices and allocate cloud expenses evenly based on department employee headcount
Provision all workloads using static, over-provisioned Compute Engine virtual machines with committed use discounts (CUDs) to achieve predictable monthly spending without autoscaling
Enforce strict static project quotas across all projects and automatically disable Cloud Billing APIs whenever a department reaches a monthly expenditure threshold
Adopt cloud FinOps practices by implementing granular resource labeling for cost allocation, establishing unit costing tied to business KPIs, and setting up Cloud Billing budgets with automated alerts
Rely on centralized IT chargeback calculations derived from monthly consolidated invoices and allocate cloud expenses evenly based on department employee headcount
Provision all workloads using static, over-provisioned Compute Engine virtual machines with committed use discounts (CUDs) to achieve predictable monthly spending without autoscaling
Enforce strict static project quotas across all projects and automatically disable Cloud Billing APIs whenever a department reaches a monthly expenditure threshold
Adopt cloud FinOps practices by implementing granular resource labeling for cost allocation, establishing unit costing tied to business KPIs, and setting up Cloud Billing budgets with automated alerts
Cloud FinOps is an operational framework and cultural practice that brings financial accountability to the variable spend model of the cloud. It enables cross-functional teams (engineering, finance, and business) to make data-driven decisions that balance cost, speed, and quality. A foundational practice within FinOps is unit costing, which measures cloud infrastructure spend relative to discrete business outputs (such as cost per transaction, cost per active subscriber, or cost per analytics query), alongside structured resource labeling and proactive budget alerts.
StudyCerts
StudyCertscost-center, environment, business-unit) across Google Cloud resources allows organizations to categorize spending granularly in Cloud Billing reports and export data to BigQuery for automated chargeback or showback.This solution directly bridges technical architecture with financial governance. Rather than applying artificial technical constraints that stifle agility or relying on coarse, lagging financial models, FinOps and unit costing provide the exact mechanisms needed to track cloud efficiency against business growth in real time.