QuestionQ131

Designing and planning a cloud solution architecture

You have been hired by your client to lead the migration of their application infrastructure to GCP. A current issue is that their on-premises high-performance SAN needs frequent, costly upgrades to keep pace with these identified workloads:

  • 20 TB of log archives kept for legal reasons
  • 500 GB of VM boot/data volumes and templates
  • 500 GB of image thumbnails
  • 200 GB of customer session-state data that lets customers restart sessions even after being offline for several days

Which option best represents your recommendations for a cost-effective storage allocation?

  • A Local SSD for customer session state data. Lifecycle-managed Cloud Storage for log archives, thumbnails, and VM boot/data volumes.
  • B Memcache backed by Cloud Datastore for the customer session state data. Lifecycle-managed Cloud Storage for log archives, thumbnails, and VM boot/data volumes.
  • C Memcache backed by Cloud SQL for customer session state data. Assorted local SSD-backed instances for VM boot/data volumes. Cloud Storage for log archives and thumbnails.
  • D Memcache backed by Persistent Disk SSD storage for customer session state data. Assorted local SSD-backed instances for VM boot/data volumes. Cloud Storage for log archives and thumbnails.
Explanation

Customer session state that must survive customers being offline for several days needs durable storage. Memcache can provide low-latency cached access, while Cloud Datastore persists the session data. Local SSD is temporary storage and may lose data when its VM stops, restarts, crashes, or is terminated; it also cannot be used as a boot device. Cloud Storage lifecycle rules can automatically transition or manage objects to reduce the cost of retained archives and other object data.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!