Associate Cloud Engineer ยท Compute Engine: choosing, launching and scaling
Disks for Compute Engine
Zonal and regional Persistent Disk, Hyperdisk, local SSD, boot vs data disks, performance and durability trade-offs, attaching and resizing disks.
Key points
- Persistent Disk and Hyperdisk are network-attached and durable: data survives VM stop or delete, volumes move between VMs, and they can be replicated across two zones (regional).
- Hyperdisk performance is independent of capacity.
- Local SSD is physically attached, fastest, and loses data when the VM stops, and it cannot be a boot disk.
- You pay for provisioned capacity.
Source: https://docs.cloud.google.com/compute/docs/disks
Practice questions
Which storage option loses its data when the VM stops?
- Regional Persistent Disk
- Hyperdisk
- Zonal Persistent Disk
- Local SSD
Show answer
Answer: D. Local SSD
Local SSD is temporary storage on the host. Persistent Disk and Hyperdisk are durable network volumes.
Which statements about Hyperdisk are correct?
- Its performance can be tuned independently of capacity
- Data survives when the VM stops
- It is physically attached to the host like Local SSD
- You pay only for bytes actually written
- Its data is erased whenever the VM stops
Show answer
Answer: A. Its performance can be tuned independently of capacity, B. Data survives when the VM stops
Hyperdisk is a durable network volume whose performance is set independently of its size. It is not host-attached and you are billed for provisioned capacity, not used bytes.
True or false: you are billed only for the data you actually write to a disk, not its provisioned size.
Show answer
Answer: False
False. You pay for provisioned capacity from creation until deletion, whether or not it is filled.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
