Examkin

Question

Difficulty: MediumPlanning Database Options and Persistent Disk Types

An organization is planning the storage architecture for an enterprise application running on Compute Engine virtual machines. The workload has two distinct operational requirements:

1. A fully managed relational database that supports standard SQL and ACID transactions with automatic regional High Availability (HA) failover.
2. Extremely high-throughput, low-latency ephemeral scratch space attached directly to individual VM instances for temporary cache calculations, where data persistence after instance termination is not required.

Which TWO database and storage options should the Cloud Engineer select to satisfy these requirements? (Select TWO.)

  1. Provision Cloud SQL configured with High Availability (regional deployment)Answer
  2. Attach Local SSD storage to the Compute Engine instances for temporary scratch spaceAnswer
  3. C
    Provision Cloud Bigtable to handle the relational SQL transaction requirements
  4. D
    Use Standard Persistent Disks (pd-standard) on Spot VMs for ultra-low latency ephemeral scratch processing

Answer

The correct selections are Cloud SQL configured with High Availability (regional deployment) and Local SSD storage attached to the Compute Engine instances.
Cloud SQL with High Availability fulfills the relational SQL transaction requirement with regional automatic failover across zones. Local SSD provides physically attached block storage with maximum IOPS and lowest latency, ideal for ephemeral scratch processing where persistent disk durability is not required.

Step-by-Step Solution

1
Evaluate requirement 1: Relational SQL database with regional High Availability.
Cloud SQL provides standard relational database engines (PostgreSQL, MySQL, SQL Server) with built-in regional HA failover capability across zones.
Cloud SQL matches all requirements for managed relational SQL storage with High Availability.
2
Evaluate requirement 2: Ultra-fast ephemeral scratch space attached directly to VM instances.
Local SSDs are physically attached to the server host, delivering microsecond-level latency and high IOPS for non-persistent scratch data.
Local SSDs provide maximum performance for temporary caching/scratch space where data does not need to survive instance termination.

Key Concept

Selecting GCP Database and Block Storage Solutions Based on Workload Requirements
Rate this question

Topics

Planning Database Options and Persistent Disk Types

More questions from this topic