Cloud Digital Leader Practice Question: Google Cloud bills Compute Engine VMs per second…

Answer analysis

Option-by-option breakdown

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

• ✗

  4 minutes (rounded up to the nearest minute).

  Why it's wrong here

  Rounding up to the nearest minute is a granularity that some billing systems use, but Google Cloud's per-second billing model does not. For a VM that runs 3 minutes and 47 seconds, the actual billed time is 227 seconds, not 4 minutes. This option incorrectly assumes minute-level rounding, which would overcharge a workload that is already billed with sub-minute precision.

• ✓

  Exactly 3 minutes and 47 seconds of compute time.

  Why this is correct

  Per-second billing on Compute Engine means the charge is calculated for exactly 227 seconds (3 minutes and 47 seconds) of compute time. While there is a 1-minute minimum for many VM types, this workload exceeds that minimum, so the billed duration equals the actual runtime. No hourly or by-minute rounding is applied, making this the correct and precisely accurate option.

• ✗

  1 hour (traditional cloud billing minimum).

  Why it's wrong here

  The 1-hour minimum is a legacy billing model from traditional cloud providers (e.g., early AWS EC2), where any instance running less than a full hour is charged for a full hour. Google Cloud Compute Engine does not use hourly minimums for most VM workloads; it bills per second after a 1-minute minimum. Thus, a 3-minute, 47-second workload would cost exactly for that usage, not a full hour.

• ✗

  5 minutes (rounded up to the nearest 5-minute interval).

  Why it's wrong here

  Some cloud platforms (e.g., certain serverless or container-as-a-service products) bill in 5-minute increments, rounding up to the next interval. Google Cloud Compute Engine, however, uses per-second billing with a 1-minute minimum for standard virtual machines. This means there is no 5-minute rounding step; the charge is based on the precise number of seconds the VM ran, so this option is incorrect.

Go deeper

Related to this question