Question-13: Both storage area networks (SAN) and network-attached storage (NAS) are examples of centralized storage management systems that allow numerous hosts to share the same storage space (servers). SAN, on the other hand, can make use of both Ethernet and Fibre Channel, whereas NAS can only utilise Ethernet. Your company's customer has entrusted you to spearhead the transition of their application infrastructure to Google Cloud Platform. One of their current issues is that the on-premises high performance SAN requires regular and expensive updates in order for it to be able to keep up with the various types of workloads that are as follows: 20 terabytes worth of log archives that must be kept for legal reasons; 500 gigabytes worth of VM boot/data volumes and template files; 500 gigabytes worth of image thumbnails; and 200 gigabytes worth of customer session state data that enables customers to restart sessions even if they have been offline for several days. FCP, which stands for Fibre Channel Protocol, iSCSI, which stands for Internet Small Computer System Interface, FCoE, which stands for Fibre Channel over Ethernet, and FC-NVMe are the protocols that are used by storage area networks (Non-Volatile Memory Express over Fibre Channel). Which of the following best represents your suggestions for a storage allocation that makes the most efficient use of resources?
A. Local SSD for customer session state data. Cloud storage that is managed throughout its lifecycle, used for storing log archives, thumbnails, and boot and data volumes for virtual machines.
B. Memcache for the customer session state data, backed by Cloud Datastore. Cloud storage that is managed throughout its lifecycle, used for storing log archives, thumbnails, and boot and data volumes for virtual machines.
C. Memcache supported by Cloud SQL for storing the session state data of customers A variety of locally supported SSD instances for use as VM boot and data volumes. Storage in the cloud for log archives as well as thumbnails.
D. Memcache storage for customer session state data, backed by persistent disc solid-state drive storage. A variety of locally supported SSD instances for use as VM boot and data volumes. Storage in the cloud for log archives as well as thumbnails.
Correct Answer
Get All 340 Questions and Answer for Google Professional Cloud Architect
: 2 Explanation: Option-1 : is wrong Local SSD is non-persistent therefore cannot be used for session state (as questions also need to save data for users who are offline for several days). Option-3 : Again Local SSD cannot be used for boot volume (because its Non-persistent again) and always used for temporary data storage. Option-4 : Same reason as Option-3 . Left with Option-2 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. Memcache backed by Cloud Datastore, Compute Engine image can be stored in Cloud Storage 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. Option-2 comes very close to be the correct answer to this weird question, where none of the choices given seems to be correct. Reasons - 1. Local SSDs are ephemeral & can't be used as a VM Boot Disk ( Option-3 & Option-4 are ruled out) 2. Google Cloud Storage can't be used as a VM Boot Disk, but the custom image of the boot disk can be stored in the GCS. But still pragmatically, the GCS can't function as a VM Boot disk. Hence with no potential choices left, from sheer storage point of view(as asked in the question), Option-2 seems to be the solitary but contentious choice.