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 large on-premises data center environment—consisting of hundreds of virtualized Linux and Windows application servers alongside relational databases—to Google Cloud.
Executive leadership and finance stakeholders require a comprehensive Total Cost of Ownership (TCO) and Return on Investment (ROI) evaluation over a 5-year projection before approving the migration budget. The financial assessment must accurately account for on-premises operational overheads, dynamic resource right-sizing rather than static over-provisioned allocations, and cost-optimization strategies like long-term usage commitments.
Which approach should the cloud architect recommend to generate this financial assessment and demonstrate value to stakeholders?
Google Cloud Migration Center is a unified platform designed to accelerate cloud migration journeys by discovering on-premises assets, evaluating performance metrics, and estimating cloud infrastructure costs and Total Cost of Ownership (TCO).
Using Migration Center provides an automated, standardized, and data-backed financial model that directly aligns technical sizing with executive ROI requirements, avoiding under- or over-estimation of multi-year operational expenditures.
This approach relies on configuring Cloud Billing budget alerts and Active Assist recommenders in an unpopulated project to forecast long-term workload migration costs and automatic Sustained Use Discounts (SUDs).
Workloads were already migrated and running in Google Cloud, and the operations team needed to implement continuous spend governance and post-migration rightsizing.
This approach deploys a small-scale prototype utilizing Spot VMs (heavily discounted, preemptible compute instances) and linearly multiplies the observed monthly billing spend across all production workloads to estimate 5-year TCO.
The organization were scoping infrastructure specifically for stateless, fault-tolerant batch computing or transient development/testing workloads.
This approach relies on manual hardware inventory collection and direct 1:1 provisioning against on-demand list prices using the standalone Google Cloud Pricing Calculator, intentionally omitting data center overheads.
The goal were to perform a quick, informal spot check of raw compute list pricing for a single standalone application without building a comprehensive corporate business case.
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