Prepare and test your skills
Prepare and test your skills
Free sample question, answered and explained below. The Professional Cloud Architect practice bank has 2,335 more like it. Try 10 free: instant score, no account.
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?
This traditional IT accounting method aggregates all enterprise cloud expenses into a single high-level monthly invoice and divides the total bill among departments proportionally based on the number of employees in each business unit.
The organization were distributing fixed, shared enterprise licensing costs (such as basic corporate email accounts) where usage is uniform and directly proportional to total employee count.
Effective cloud financial management requires tagging, labeling, and direct resource attribution to reflect actual consumption rather than arbitrary corporate allocation models.
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.
cost-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.
This approach relies on rigid operational guardrails by setting static resource quotas at the project level and programmatically disabling APIs or tearing down infrastructure when a financial limit is reached.
The organization required hard, non-negotiable financial cutoffs for unmonitored sandbox or disposable training environments where unexpected overruns must trigger complete workload termination regardless of uptime.
Cloud governance best practices emphasize observability and alerting over disruptive hard shutdowns. Automated alerting allows teams to remediate cost anomalies while maintaining critical application availability.
This strategy involves sizing virtual machines to match peak anticipated capacity and purchasing Committed Use Discounts (CUDs) to lock in lower hourly compute rates across a one-year or three-year term while deliberately avoiding autoscaling or managed serverless services.
The workload had completely constant, 24/7 steady-state compute demands with zero fluctuations, and the sole objective was price certainty on predictable compute infrastructure.
Modern cloud architectures achieve lower TCO by combining autoscaling with baseline Committed Use Discounts, ensuring resources scale dynamically while still benefiting from commitment-based discounts for steady-state workloads.
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