Examkin

Question

Difficulty: HardPlanning Database Options and Persistent Disk Types

An enterprise is deploying an application on Google Cloud Compute Engine that requires two distinct storage mechanisms: (1) a temporary session state cache requiring sub-millisecond latency and high IOPS where data persistence across VM stops/starts is not required, and (2) a relational database engine for order management requiring strict ACID compliance, regional high availability, automated backups, and minimal database administration overhead. Which TWO storage and database configurations should you select to meet these requirements? (Select TWO.)

  1. Attach a Local SSD volume to the Compute Engine instance for the session state cache.Answer
  2. Provision a Cloud SQL instance with High Availability (HA) enabled for the relational database.Answer
  3. C
    Deploy a Cloud Bigtable cluster for the order management relational database.
  4. D
    Deploy a self-managed MySQL database on a Spot Compute Engine instance using Standard Persistent Disk (pd-standard) for the order database.

Answer

Attaching a Local SSD volume for the temporary session cache and provisioning a Cloud SQL instance configured with High Availability for the order management database.
Local SSD is designed for ultra-high performance, low-latency scratch space or ephemeral caching where data does not need to survive instance termination. Cloud SQL provides a fully managed relational database with automated backups, patching, and regional high availability via active-standby replication.

Step-by-Step Solution

1
Analyze session cache requirements
Requirements call for sub-millisecond write latency, high IOPS, and ephemeral retention where persistence across VM restarts is unnecessary.
Local SSD provides maximum IOPS and lowest latency by mounting storage directly to the physical host, perfect for non-persistent caching.
2
Analyze database requirements
Requirements specify a managed relational database with strict ACID compliance, regional HA, automated backups, and zero OS maintenance overhead.
Cloud SQL provides managed relational engines (MySQL/PostgreSQL/SQL Server) with built-in regional failover and automated maintenance.
3
Evaluate and reject improper architectural choices
Cloud Bigtable lacks relational multi-table transactional features, and Spot VMs risk unannounced terminations causing database outage/corruption.
Matching storage engine characteristics to workload durability and query patterns is critical for availability and correctness.

Key Concept

Selecting GCP Database and Block Storage Options Based on Workload Latency, ACID, and Availability Requirements
Estimated Time:2m 0s
Rate this question

Topics

Planning Database Options and Persistent Disk Types

More questions from this topic