A global fleet management company is designing a Google Cloud architecture to handle two core workloads for its telematics platform:
1. Real-time ingestion and low-latency point-in-time querying of high-throughput time-series telemetry data originating from millions of vehicle GPS sensors.
2. Archival of unstructured driver inspection PDF logs and vehicle camera images that are accessed frequently for the first 30 days and must automatically transition to low-cost archival storage for long-term compliance retention.
Which TWO storage services and features should the lead cloud architect select to satisfy these requirements while minimizing operational overhead?
- Cloud Bigtable to ingest high-throughput time-series vehicle telemetry data with millisecond read/write latency.Answer
- Cloud Storage buckets combined with Object Lifecycle Management to store unstructured logs and automatically transition aged files to Nearline or Coldline storage.Answer
- CCloud Spanner to store unstructured PDF inspection logs and binary camera images to guarantee global multi-region transactional consistency for binary objects.
- DCustomer-Supplied Encryption Keys (CSEK) managed manually on local key management hardware for Cloud Storage object encryption to satisfy standard GCP managed key compliance requirements.
Answer
The optimal architecture selects Cloud Bigtable for high-throughput time-series vehicle sensor data and Cloud Storage with Object Lifecycle Management for unstructured log and image archival.
Cloud Bigtable is optimized for massive write throughput and time-series data such as telemetry from vehicle sensors. Cloud Storage paired with Object Lifecycle Management provides a cost-effective solution for unstructured documents and images by automatically downgrading storage classes as files age.
Step-by-Step Solution
Key Concept
Matching workload access patterns (high-throughput time-series telemetry vs unstructured blob lifecycle archival) to managed GCP storage resources.
Estimated Time:2m 0s