Question

Difficulty: MediumPlanning Database Options and Persistent Disk Types

An organization is migrating an enterprise resource planning (ERP) relational database to a Compute Engine virtual machine on Google Cloud. The workload requires reliable, cost-effective SSD-backed performance with consistent IOPS for standard transactional operations. Additionally, the disk volume must automatically replicate data across two zones in the same region to ensure high availability during a zonal outage. Which block storage disk type should you select to meet these requirements?

  1. Regional Balanced Persistent Disk (pd-balanced)Answer
  2. B
    Local SSD
  3. C
    Regional Standard Persistent Disk (pd-standard)
  4. D
    Zonal Extreme Persistent Disk (pd-extreme)

Answer

Regional Balanced Persistent Disk (pd-balanced)
Regional Balanced Persistent Disk (pd-balanced) delivers cost-effective SSD-based performance suitable for enterprise relational database workloads while providing synchronous cross-zone replication within a region for high availability.

Step-by-Step Solution

1
Analyze storage performance requirements
Relational ERP database workloads require solid-state drive (SSD) performance rather than standard hard disk drives (HDD).
Standard HDDs (pd-standard) lack sufficient sequential and random IOPS required for database read/write queries.
2
Evaluate availability and replication needs
The scenario requires automatic synchronous data replication across two zones within the same region.
Regional Persistent Disks synchronously replicate block data across two zones in a region, whereas Zonal persistent disks reside in a single zone.
3
Balance cost versus high-performance specifications
Balanced Persistent Disk (pd-balanced) offers an optimal tradeoff of SSD-backed IOPS and cost efficiency.
Extreme Persistent Disk (pd-extreme) is over-provisioned for standard ERP baseline operations and lacks regional replication options.

Key Concept

Selecting persistent disk options based on performance, cost, and high availability replication requirements
Estimated Time:1m 30s
Rate this question