Examkin

Question

Difficulty: MediumPlanning Database Options and Persistent Disk Types

Match each Google Cloud storage option or persistent disk type to its primary architectural capability and ideal workload scenario.

  • Cloud SpannerFully managed relational database providing global scale, high availability, and strong ACID consistency across regions.
  • Cloud BigtablePetabyte-scale NoSQL database designed for high-throughput, low-latency analytical and operational workloads such as IoT time-series.
  • Local SSDHost-attached block storage offering maximum IOPS and microsecond latency, but with ephemeral data that does not persist across VM stops.
  • Balanced Persistent Disk (pd-balanced)Cost-effective network-attached persistent block storage balancing performance and price for general enterprise application boot disks.

Answer

Cloud Spanner pairs with the global relational database capability; Cloud Bigtable pairs with the petabyte-scale NoSQL capability; Local SSD pairs with the high-performance host-attached ephemeral block storage; and Balanced Persistent Disk pairs with the cost-effective network block storage option.
Each service targets distinct operational constraints: Cloud Spanner supports globally scalable relational transactions; Cloud Bigtable handles massive NoSQL telemetry and time-series throughput; Local SSD provides maximum IOPS with host-bound ephemerality; and Balanced Persistent Disk offers durable network block storage optimized for cost-performance balance.

Step-by-Step Solution

1
Identify relational database requirements requiring global consistency
Matched Cloud Spanner to global relational database with strong ACID consistency.
Cloud Spanner is uniquely engineered to scale relationally across regions without sacrificing ACID consistency.
2
Identify massive-scale NoSQL key-value and time-series requirements
Matched Cloud Bigtable to petabyte-scale NoSQL low-latency workloads.
Cloud Bigtable handles high-throughput key-value write/read operations required by time-series data.
3
Differentiate persistent network block storage from ephemeral host-attached block storage
Matched Local SSD to non-persistent host-attached storage and pd-balanced to persistent network storage.
Local SSD is physically bound to the host hypervisor and loses data on VM stop, whereas persistent disks are network-attached and retain data.

Key Concept

GCP Database & Block Storage Selection Criteria
Estimated Time:1m 30s
Rate this question

Topics

Planning Database Options and Persistent Disk Types

More questions from this topic