Prepare and test your skills

Prepare and test your skills

Free sample question with answers and detailed explanation below. The Cloud Digital Leader practice bank has an additional 3,070 practice questions.Try 10 free realistic questions: instant score, no credit card, and no account required.
A financial services company is evaluating the five-year Total Cost of Ownership (TCO) of migrating its on-premises data center and self-hosted databases to Google Cloud managed services such as Cloud SQL. Currently, the finance team's TCO model only compares two factors:
Based on this initial comparison, the finance team concludes that remaining on-premises is less expensive.
Which additional cost components must the company include in its TCO analysis to accurately determine the long-term financial impact?
A comprehensive Total Cost of Ownership (TCO) evaluation is a financial assessment that accounts for both the direct and indirect expenses of owning, operating, and maintaining IT infrastructure over a specific timeframe (typically three to five years). When comparing an on-premises data center against Google Cloud, an accurate TCO model must look beyond initial hardware price tags to include ongoing facility expenses and hidden operational overhead.
Cloud SQL automate these tasks, shifting valuable engineering time away from infrastructure maintenance.Comparing only upfront hardware CapEx against monthly cloud OpEx creates a flawed financial baseline because Google Cloud pricing already bundles power, cooling, physical rack maintenance, and automated management into a single transparent bill. Including these indirect and operational on-premises costs ensures an apples-to-apples comparison that accurately reflects long-term Total Cost of Ownership.
Committed Use Discounts (CUDs) are optional billing discount programs offered by Google Cloud that provide significant price reductions in exchange for a commitment to use a minimum level of resources or spend a minimum amount over a one-year or three-year term. They are designed to optimize ongoing operational expenditures (OpEx) for predictable workloads.
Compute Engine or managed databases in Cloud SQL.Compute Engine hardware quantities in a region (resource-based CUDs) or commit to a minimum monetary spend on eligible services (spend-based CUDs).This option would be appropriate if the question asked how an organization with predictable, steady-state workloads could reduce its projected Google Cloud OpEx and lower its five-year cloud TCO through optional commitment-based pricing.
When using tools like the Google Cloud Migration Center or Quick TCO Estimator, administrators can toggle different CUD plans (such as a 1-year or 3-year commitment) to see how discounted billing rates improve long-term savings compared to on-premises infrastructure.
Cloud network cost modeling is the process of estimating expenses related to data movement, connectivity, and traffic management within a cloud environment. Unlike traditional environments where organizations buy and install physical networking gear, cloud networking operates on a consumption-based operational expenditure (OpEx) model.
Cloud Load Balancing or Cloud VPN.This option would be relevant if the organization were building a new on-premises data center or setting up equipment inside a third-party colocation facility, where purchasing and installing physical routers, switches, and cabling requires an upfront capital expenditure.
A major driver of the shift from CapEx to OpEx during cloud migration is the transformation of networking expenses. Instead of paying large upfront sums for networking hardware that depreciates over time, organizations pay only for the bandwidth and virtual networking services they actively consume.
Ingress traffic refers to any network data that enters a Google Cloud environment from an external source, such as the public internet, an on-premises data center, or another cloud provider. Understanding how cloud providers bill for directional data flow is an important part of modeling cloud networking operational expenditures (OpEx).
Cloud Load Balancing, Cloud CDN, and Google Cloud Armor—charge based on the volume of ingress traffic they inspect or process.This option would be relevant if it referred to network egress traffic leaving Google Cloud or data transfers between different regions, and the question asked which often-overlooked cloud networking cost should be factored into a multi-region cloud architecture estimate.
Because ingress traffic is free for most services, moving large datasets into Google Cloud during an initial migration does not incur inbound bandwidth penalties from Google Cloud, helping keep migration-phase TCO low.
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