FoundationCost

What are the main things that drive a cloud bill?

What they are really testing: Whether you have a mental model of cost categories, compute, storage, data transfer, managed services, rather than thinking the bill is just about servers.

A real interview question

What are the main things that drive a cloud bill?

What most people say

drag me

The cost is mostly from the servers you run.

Compute is one driver, but storage, data transfer (egress especially), and managed services are large and often surprising. Thinking the bill is just servers means you miss where a lot of real spend hides.

The follow-ups they ask next

  • Which cost driver surprises teams most often?

    Data transfer / egress: cross-AZ chatter, cross-region replication, and internet egress are billed but invisible until the invoice. Ingress is usually free, which lulls people into ignoring transfer costs.

  • Why does knowing the cost breakdown matter before optimizing?

    You optimize each category differently (rightsizing compute vs lifecycle for storage vs CDN/locality for egress). Optimizing the wrong category wastes effort; start from what actually dominates your bill.

What the interviewer is listening for

  • Names compute/storage/transfer/managed services
  • Flags egress as overlooked
  • Knows you optimize from the breakdown

What sinks the answer

  • "Just the servers"
  • Omits data transfer entirely
  • No notion of a cost breakdown

If you genuinely do not know

Say this instead of freezing. Reasoning out loud from what you do know beats silence every single time, and a good interviewer is listening for exactly that.

A cloud bill is driven by [compute (instances/containers/functions, size x time)], [storage (GB-month + IOPS, incl. snapshots/backups)], [data transfer (egress to internet and cross-region/AZ, the overlooked one, ingress usually free)], and [managed services (per request/GB/hour)]. Optimize from [the breakdown], since each category is optimized differently.

Keep going with cost

All 336 cloud engineer questions

Knowing the answer is not the same as recalling it under pressure

Sign in to send the questions you fumble to spaced recall, so they come back right before you would forget them, and learn the concepts behind them with hands-on labs.

Start free