Topic 1 Question 86

Professional Cloud Architect

Topic 1 Question 86
You have been engaged by your client to lead the migration of their application infrastructure to GCP. One of their current problems is that the on-premises high performance SAN is requiring frequent and expensive upgrades to keep up with the variety of workloads that are identified as follows: 20 TB of log archives retained 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 allows customers to restart sessions even if off-line for several days. Which of the following best reflects your recommendations for a cost-effective storage allocation?
- Local SSD for customer session state data. Lifecycle-managed Cloud Storage for log archives, thumbnails, and VM boot/data volumes.
- Memcache backed by Cloud Datastore for the customer session state data. Lifecycle-managed Cloud Storage for log archives, thumbnails, and VM boot/data volumes.
- 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.
- 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.
ユーザの投票
コメント(17)
- B is correct. WHY NOT OTHERS. A: is wrong Local SSD in non-persistent therefore cannot be used for session state (as questions also need to save data for users who are offline for several days). C: Again Local SSD cannot be used for boot volume (because its Non-persistent again) and always used for temporary data storage. D: Same reason as C. WHY B? Left with B that's why, but the question is how to store Boot/Data volume on Cloud Storage?
  
  Storing other type of data is easy but most comments were about boot volume.
  
  Boot volume can be stored to Cloud Storage by creating an Custom Image. https://cloud.google.com/compute/docs/images/create-delete-deprecate-private-images#selecting_image_storage_location ---- Upvote if agree for the clarification of others ----
  👍 79
  OSNG2020/12/05
- IMHO Answer is B:
  
  Memcache backed by Cloud Datastore https://cloud.google.com/appengine/docs/standard/python/memcache
  
  Compute Engine image can be stored in Cloud Storage https://cloud.google.com/solutions/image-management-best-practices After the complete sequence of bytes from the disk are written to the file, the file is archived using the tar format and then compressed using the GZIP format. You can then upload the resulting *.tar.gz file to Cloud Storage and register it as an image in Compute Engine.
  
  👍 15
  siumk2020/03/09
- The correct answer is D For the customer session state data, which needs to be highly available and fast, it is recommend to use Memcache backed by Persistent Disk SSD storage. This will provide fast read and write access to the data, as well as high availability.
  
  For the VM boot/data volumes, which also require fast read and write access, it is recommend to use local SSD-backed instances. This will provide the highest performance for these workloads.
  
  For the log archives and thumbnails, which do not require the same level of performance as the other workloads, it is recommend to use lifecycle-managed Cloud Storage. This will provide a cost-effective solution for storing this data, as it will automatically move data to lower-cost storage options as it becomes less frequently accessed.
  
  👍 8
  omermahgoub2022/12/22
シャッフルモード

ユーザの投票

コメント(17)