Exam Professional Cloud Architect topic 1 question 86 discussion

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 ----

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.

None of these provide an effective method of storing boot/data volumes The correct approach would be to create persistent disk Drives for boot/data volumes directly and go with B or D for the remainder of requirements.

B is correct. the question lays emphasis on a cost-effective storage allocation, and persistent disks are costly than B (that rules out D)

This is a troublesome question... IMHO, it's D. I was between C & D, but seeing how they stored the customer session data as files, storing it in SQL would require refactoring, and maybe higher latencies. I'm against B because of the latency added by booting & loading data off Cloud Storage, since it adds network latency to the equation. BUT this is assuming the method of using cloud storage is via gcsfuse, that is, using the bucket as a HD. Now if the way of using it is via image of the disk that is loaded when the instance starts, that would be ok. And that's what I expected of option D, that it would load an image of the boot/data volume in it's non-persistent disks. No 'persistent' data would be stored in it, so anything lost when it's shutdown can be ignored.

D is correct answer because - Memcache backed by Persistent Disk SSD storage for customer session state data. - Persistent disk will ensure that Session data is preserved evern if not used for long time. - Assorted local SSD-backed instances for VM boot/data volumes. Provides faster boot up for VMs. (There is no requirement for persistent storage) - Cloud Storage for log archives and thumbnails. - For low cost and scalable solution.

d wrong because of local ssd cannot use for boot image. its temporary and will be cleared if vm was suspended >> so chose b

Local SSD means Ephemeral ( Temp Disk ) so do not confused with PERSISTENT disk ( Permanent Disk ). The data that you store on a local SSD persists only until the instance is stopped or deleted.

Local SSD cannot be used for neither boot nor data!!! This rules out B&C. Oh, and A too.

Cloud Datastore is the right solution to store the session data

B Seems correct.

D. makes more sense

d makes more sense

ChatGPT says option D.

My answer is D

I will go with Option D as it is best practice to keep similar data together and seprate OS, Volatile and permanent

i'll go D because i don't think Cloud storage can be used for booting a VM.