Examkin

Question

Difficulty: HardPlanning Database Options and Persistent Disk Types

For a multi-tier enterprise architecture migration to Google Cloud, evaluate the data access patterns and performance requirements of each workload component below. Match each requirement to the most appropriate and cost-effective Google Cloud database service or block storage configuration.

  • A mobile client backend needing scalable hierarchical document storage, real-time live synchronization, offline data handling, and ACID transaction support across multiple collections.Firestore in Native mode
  • An IoT streaming engine requiring single-digit millisecond latency for massive throughput writes and key-range scans across petabytes of time-series metric data.Cloud Bigtable
  • A batch log aggregation VM performing high-volume sequential disk write operations where cost per gigabyte and sustained sequential throughput are prioritized over high random IOPS.Standard Persistent Disk (pd-standard)
  • A cluster of web server Compute Engine VMs requiring high-performance shared block storage mounted simultaneously to all instances in read-only mode to access static application binary data.SSD Persistent Disk (pd-ssd) mounted in ReadOnly mode

Answer

The correct pairings match mobile document sync requirements to Firestore in Native mode, high-throughput IoT time-series data to Cloud Bigtable, sequential batch logging to Standard Persistent Disk (pd-standard), and multi-instance shared read-only block storage to SSD Persistent Disk (pd-ssd) in ReadOnly attachment mode.
Firestore in Native mode provides flexible, hierarchical document storage with built-in client SDK offline sync and multi-document transactions. Cloud Bigtable delivers ultra-low latency write throughput for petabyte-scale time-series and IoT metrics. Standard Persistent Disk (pd-standard) minimizes costs for sequential disk operations like log aggregation. SSD Persistent Disk (pd-ssd) supports concurrent multi-VM attachment when accessed strictly in ReadOnly mode.

Step-by-Step Solution

1
Analyze document model, mobile client sync, offline support, and multi-collection ACID requirement.
Identifies Firestore in Native mode as the tailored database option for mobile backends requiring document synchronization.
Cloud SQL and Cloud Spanner are relational DBs, while Bigtable lacks mobile client synchronization SDKs and offline capabilities.
2
Analyze high-throughput, low-latency, petabyte-scale write and key-scan pattern for IoT metrics.
Identifies Cloud Bigtable as the optimal wide-column NoSQL service.
Cloud Bigtable scales seamlessly to petabytes and is specifically optimized for high-write time-series and key-range queries.
3
Analyze sequential write workload prioritized by cost per GB over random IOPS.
Identifies Standard Persistent Disk (pd-standard) as the correct block storage type.
HDD-backed standard disks offer the lowest cost per GB for sequential access workloads such as batch log ingestion.
4
Analyze requirement for high-performance block storage attached to multiple VMs simultaneously.
Identifies SSD Persistent Disk (pd-ssd) configured in ReadOnly mode.
Persistent Disks can be attached to multiple Compute Engine instances simultaneously only when attached in ReadOnly mode.

Key Concept

Selecting GCP Database and Persistent Disk types based on access patterns, scaling needs, latency SLA, and multi-attach capabilities.
Estimated Time:2m 0s
Rate this question

Topics

Planning Database Options and Persistent Disk Types

More questions from this topic