Cloud Digital Leader Practice Question: A business analyst needs to understand why cloud…

Answer analysis

Option-by-option breakdown

For each option: why learners choose it and why it is or isn't the right answer here.

• ✗

  Cloud providers bill different resources differently to maximize revenue by charging the highest rates for the most-used services

  Why it's wrong here

  Choosing a billing meter is a cost-accounting decision based on how a resource is physically consumed, not a revenue-maximization tactic. Virtual machines are metered per second of uptime because they dedicate CPU and memory that could otherwise be sold, whereas storage is metered per GB-month because the cost is the sustained occupation of disk space, independent of how often the data is read or written. If providers were purely maximizing revenue, they would use opaque or inflated meters; instead, the units directly mirror infrastructure expenses such as compute cycles and persistent capacity.

• ✓

  Cloud resources are billed based on their natural unit of consumption: compute time for VMs (per second running) and data volume over time for storage (per GB-month) — matching billing to how each resource is actually consumed

  Why this is correct

  This is the correct explanation. Billing models match consumption patterns: VMs consume CPU/memory as long as they run (time-based), while storage accumulates data that persists over time (data×time). This measured service model ensures billing is proportional to actual resource use.

• ✗

  Storage is charged per GB-month because cloud providers cannot measure storage usage per second accurately

  Why it's wrong here

  Cloud providers have the telemetry to track storage writes and reads with millisecond precision, so accuracy is not the constraint. The GB-month is a deliberate unit because storage is a stateful resource: its cost comes from maintaining data at rest, consuming disk capacity and redundancy overhead continuously, regardless of access activity. A per-second meter would be meaningless for idle data that still incurs cost, so the GB-month measure correctly represents the area under the curve of allocated capacity over elapsed time.

• ✗

  The billing difference is a temporary situation; cloud providers are working toward a single universal billing unit for all services

  Why it's wrong here

  Different billing units are a permanent, purposeful aspect of cloud pricing, not a transitional inconsistency. Compute is metered per second because virtual machines consume CPU and memory continuously while running, whereas storage is metered per GB-month because the cost driver is persistent data occupying capacity over time. A single universal unit would obscure these distinct consumption patterns, and no serious industry effort exists to force one; such a change would reduce billing transparency and make usage less accurately reflected.

Go deeper

Related to this question