Scaling with Google Cloud Operations practice questions

OpEx cloud spending is variable: it rises and falls with consumption, so cost control becomes a continuous activity rather than an annual approval.

The shift to OpEx removes the big up-front purchase but makes the bill variable. Anyone can create resources on demand, so spend can grow quickly between reviews. Finance therefore needs ongoing visibility and forecasting. Depreciation, purchase approvals and refresh contracts all belong to the CapEx model the company has left.

1. Note that the bill now changes with usage each month.
2. Recall that variable spend needs ongoing monitoring and forecasting.
3. Reject options that describe owning and buying hardware.
4. Choose continuous tracking and forecasting.

Exam tip: OpEx is flexible but variable: cost control moves from one annual decision to continuous tracking.

Total cost of ownership (TCO) counts every cost of running a system over its life, not just the purchase price: facilities, power, cooling, staff, maintenance and hardware refresh.

An on-premises TCO includes the indirect costs of owning infrastructure: the building, power and cooling, and the staff who maintain and refresh hardware. These are easy to miss when comparing a server quote with a cloud price. The remaining options are real costs, but of the cloud alternative, so they belong on the other side of the comparison.

1. Identify which side of the comparison is being asked about: on-premises.
2. Recall that TCO includes indirect costs, not only purchase prices.
3. Separate on-premises costs from Google Cloud charges.
4. Choose the two on-premises running costs.

Exam tip: TCO is purchase price plus everything it takes to run the system: facilities, power, cooling, staff and refresh.

A fair TCO comparison counts every on-premises cost of ownership and prices the cloud for how resources will really be used.

Two facts combine. First, on-premises TCO includes facilities, power, cooling, staff and hardware refresh, not only the server price. Second, cloud cost depends on consumption: an estimate that runs every VM at peak size around the clock pays for capacity that elastic, right-sized resources would not use. A commitment discount lowers the price of that idle capacity but does not remove it, and dropping staff costs hides a real on-premises cost.

1. Check what the on-premises estimate leaves out.
2. Check what the cloud estimate assumes about usage.
3. Recall that TCO includes indirect costs and that cloud costs follow consumption.
4. Choose the option that corrects both estimates.

Exam tip: Compare full on-premises TCO with cloud costs sized to real usage, or the comparison is skewed.

Google-recommended cloud financial governance (FinOps) makes cost a shared responsibility of a cross-functional team: finance, technology and business.

In the cloud, spending decisions are spread across everyone who creates resources. Google's guidance is a FinOps model in which a cross-functional team brings finance, technology and business together, so the people who spend, the people who pay and the people who measure value decide together. A single department, or teams working with no shared view, lacks either control of usage or the financial context.

1. Note that no one owns cloud spend.
2. Recall that cloud spending decisions are spread across many teams.
3. Recall Google's FinOps guidance: shared, cross-functional ownership.
4. Choose the cross-functional team.

Exam tip: Cloud costs are managed best by a cross-functional FinOps team, not by one department alone.

Financial governance in the cloud gives each team visibility of, and accountability for, the costs it creates, while a central function sets guardrails.

Spend rises here because the teams creating resources never see the bill. Google's FinOps guidance is to make costs visible to the teams that drive them and hold them accountable, with central guardrails such as budgets. Central approvals sacrifice agility, a single shared project removes the per-team view, and flat cuts act without information.

1. Identify the root cause: the teams that spend cannot see their costs.
2. Recall that FinOps pairs visibility with accountability.
3. Reject options that slow teams or hide per-team costs.
4. Choose per-team visibility and accountability.

Exam tip: Teams that create cloud costs should see them and own them.

Controlling cloud costs takes people (roles and accountability), process (routines such as reviews and forecasting) and technology (tools such as budgets and billing reports).

The three parts work together. People are the roles and owners, such as a FinOps lead. Technology is the tooling, such as budgets, alerts and billing reports. Process is the agreed way of working that connects them, such as a regular review of spend against forecast.

1. Recall the three parts: people, process and technology.
2. Classify each option as a role, a routine or a tool.
3. Choose the routine.

Exam tip: People own the costs, process sets the routine, technology provides the data and alerts.