An automotive technology enterprise is building a telemetry and account management solution on Google Cloud. The application has two distinct storage requirements:
1. High-throughput, sub-10ms write latency ingestion for semi-structured sensor diagnostics arriving from millions of connected vehicles worldwide.
2. Standard relational database storage for customer subscription profiles and billing accounts that operates strictly within a single GCP region with high availability.
Which TWO database and storage services should you recommend to meet these requirements while optimizing cost and operational efficiency? (Select TWO)
- Provision Cloud Bigtable to handle the high-throughput, low-latency semi-structured time-series sensor diagnostic data.Answer
- Provision Cloud SQL with High Availability (regional failover) for single-region relational customer subscription and billing data.Answer
- CProvision a multi-region Cloud Spanner instance to store single-region relational customer subscription and billing accounts.
- DUse online Storage Transfer Service over the public internet to migrate 2 PB of offline historical telemetry logs from a disconnected on-premises facility.
Answer
The optimal architecture combines Cloud Bigtable for high-throughput semi-structured telemetry data and Cloud SQL configured for High Availability for single-region relational subscription and billing records.
Selecting Cloud Bigtable provides scalable, low-latency NoSQL storage for massive semi-structured IoT telemetry ingestion. Selecting Cloud SQL configured for High Availability delivers fully managed, single-region relational ACID capabilities with automatic failover, satisfying all business and technical constraints cost-effectively.
Step-by-Step Solution
Key Concept
Selecting optimal GCP storage resources based on relational vs NoSQL access patterns, latency bounds, scale, and regional requirements.