An architecture team is planning storage configurations for a web application deployed on Google Cloud Compute Engine. The solution requires: 1) A ultra-fast, temporary caching tier requiring sub-millisecond I/O latency where data loss during instance termination is acceptable. 2) A fully managed relational database service for handling transaction data. Which TWO storage solutions should the team select? (Select TWO)
- Local SSD attached to Compute Engine instances for the temporary caching tierCevap
- BCloud Bigtable for the transactional database layer
- Cloud SQL instance for the transactional database layerCevap
- DSpot VM instances with standard persistent disks to host the transactional database
Cevap
Local SSD attached to Compute Engine instances for the temporary caching tier, and Cloud SQL instance for the transactional database layer.
Local SSDs are directly attached to the physical host running the Compute Engine instance, providing sub-millisecond latency for caching data where persistence across instance reboot/termination is not required. Cloud SQL is the recommended Google Cloud service for fully managed relational databases needing standard SQL capabilities and high availability.
Adım Adım Çözüm
Anahtar Kavram
Selecting GCP Database and Persistent Disk types based on latency, transactional compliance, and persistence requirements.