Question

Difficulty: HardPlanning Database Options and Persistent Disk Types

Match each Google Cloud database or persistent storage option to the enterprise workload requirement that best aligns with its architectural characteristics and performance capabilities.

  • Cloud SpannerA globally distributed, horizontally scalable relational database requiring strict multi-region ACID compliance and SQL querying.
  • Cloud BigtableA low-latency NoSQL wide-column database optimized for high-throughput streaming ingest, IoT data, and time-series analytics.
  • Local SSDUltra-high performance block storage physically attached to the host server node, providing sub-millisecond latency for ephemeral scratch space.
  • Cloud SQLA fully managed regional relational database service supporting standard MySQL, PostgreSQL, or SQL Server engines with high availability options.

Answer

Cloud Spanner matches globally distributed relational ACID workloads; Cloud Bigtable matches low-latency high-throughput NoSQL analytics; Local SSD matches host-attached ephemeral scratch storage; Cloud SQL matches managed regional relational DB engines.
Each GCP storage and database service addresses distinct architectural requirements across scalability, relational model support, access latency, and data persistence guarantees.

Step-by-Step Solution

1
Analyze global multi-region relational requirements.
Identify Cloud Spanner as the sole option supporting horizontal scaling with multi-region relational ACID transactions.
Standard regional engines cannot scale horizontally across regions while preserving synchronous relational transactions.
2
Evaluate high-throughput NoSQL time-series requirements.
Identify Cloud Bigtable for key-value wide-column workloads needing single-digit millisecond latency.
Cloud Bigtable provides seamless scaling for heavy streaming reads and writes.
3
Assess host-attached block storage performance and persistence.
Identify Local SSD as ephemeral block storage physically linked to the hypervisor host.
Local SSDs deliver highest IOPS and lowest latency but lose data if the instance stops.
4
Identify regional managed relational database solutions.
Match Cloud SQL to regional transactional workloads running MySQL, PostgreSQL, or SQL Server engines.
Cloud SQL simplifies operational overhead for standard relational database engines within a region.

Key Concept

Planning Database Options and Persistent Disk Types based on scale, transaction model, latency, and data persistence.
Rate this question