An online retail organization is migrating its platform backend to Google Cloud. The architecture requires two storage components: first, a transactional relational database for order management that mandates ACID compliance and automatic cross-zone failover within a single region; second, ultra-low sub-millisecond latency scratch storage for ephemeral data processing jobs running on Compute Engine instances. Which TWO storage and database configurations should the team select to satisfy these requirements?
- Cloud SQL configured with High Availability (regional failover) for the order management databaseCevap
- Local SSD attached to Compute Engine instances for high-performance temporary scratch storageCevap
- CCloud Bigtable configured with multi-cluster replication for the order management database
- DCloud Storage Coldline storage bucket mounted to VM instances for high-performance temporary scratch storage
Cevap
The team should select Cloud SQL configured with High Availability for the transactional relational order management database, and Local SSD attached to Compute Engine instances for low-latency temporary scratch storage.
Cloud SQL with High Availability (HA) provides managed relational engines with ACID compliance and automatic failover between primary and standby zones in a region. Local SSDs are physically attached to the server hosting the Compute Engine VM, offering high throughput and sub-millisecond latency required for temporary scratch processing.
Adım Adım Çözüm
Anahtar Kavram
Matching GCP relational databases (Cloud SQL HA) and block storage types (Local SSD) to specific operational and performance requirements