Question

Difficulty: MediumSelecting and Designing Storage and Database Resources

A global fleet management platform collects real-time vehicle telemetry data across North America and Europe. The architecture requires two distinct data storage services to support its core capabilities:

1. Low-latency, high-throughput ingestion of real-time telemetry time-series data streams (exceeding 100,000 writes per second per region).
2. Globally distributed, strongly consistent ACID transactions for managing vehicle registration, driver profiles, and billing subscription data across multiple regions.

Which TWO Google Cloud database and storage services should the cloud architect select to meet these technical requirements? (Select TWO.)

  1. Cloud Bigtable to handle high-throughput, low-latency ingestion of vehicle telemetry time-series data.Answer
  2. Cloud Spanner to manage globally distributed vehicle registration and billing subscription data with ACID transactional consistency.Answer
  3. C
    Cloud SQL for PostgreSQL to provide multi-region global strong ACID consistency for subscription and vehicle registration data.
  4. D
    Transfer Appliance to stream continuous real-time vehicle telemetry time-series points directly into Cloud Storage.

Answer

Selecting Cloud Bigtable for high-throughput NoSQL time-series telemetry data and Cloud Spanner for globally distributed relational ACID subscription data.
The solution requires two specialized databases. Cloud Bigtable is optimized for heavy write time-series telemetry workloads where throughput and low latency are critical. Cloud Spanner provides a globally distributed relational database with multi-region strong ACID consistency for vehicle and billing profiles.

Step-by-Step Solution

1
Analyze the workload requirement for streaming vehicle telemetry data.
Identified high write volume (>100,000 writes/sec), time-series access pattern, and low-latency requirement.
Cloud Bigtable is designed specifically for low-latency, high-throughput time-series and IoT telemetry storage.
2
Analyze the workload requirement for vehicle registration and billing subscription data.
Identified multi-region deployment requirement with strong ACID transactional consistency.
Cloud Spanner is Google Cloud's fully managed relational database that scales globally with strong consistency across regions.
3
Evaluate and eliminate non-matching GCP storage options.
Disqualified Cloud SQL (regional limitation for writes/global consistency) and Transfer Appliance (offline bulk hardware migration tool).
Matching technical requirements to service capabilities ensures scalable, reliable operational architecture.

Key Concept

Selecting GCP database and storage resources based on access patterns, throughput, latency, and regional consistency requirements.
Rate this question