A company is planning the storage architecture for a self-managed relational database running on a Compute Engine virtual machine. The database workload requires SSD-level performance and lower latency than standard magnetic persistent disks, but the cloud engineering team wants a cost-effective option compared to high-performance SSD persistent disks (`pd-ssd`). The storage must persist independently of the VM instance lifecycle and provide standard zonal redundancy. Which storage option should the team select?
- Balanced persistent disk (`pd-balanced`)Answer
- BLocal SSD attached to a Spot Compute Engine VM instance
- CCloud Bigtable provisioned with a SSD storage cluster
- DCloud Storage Coldline bucket mounted using Cloud Storage FUSE
Answer
Balanced persistent disk (`pd-balanced`) is the recommended storage type because it offers SSD-backed performance at a lower cost point than `pd-ssd`, while maintaining persistent zonal durability independent of VM instance lifecycle.
Balanced persistent disk (`pd-balanced`) is specifically designed to bridge the gap between standard magnetic persistent disks (`pd-standard`) and high-performance SSD disks (`pd-ssd`). It provides SSD performance suitable for standard relational databases at a lower price point while ensuring data persistence independent of the Compute Engine VM lifecycle.
Step-by-Step Solution
Key Concept
Selecting persistent disk types based on database performance, durability, and cost constraints.
Estimated Time:1m 30s