Topic 1 Question 33
Your application is controlled by a managed instance group. You want to share a large read-only data set between all the instances in the managed instance group. You want to ensure that each instance can start quickly and can access the data set via its filesystem with very low latency. You also want to minimize the total cost of the solution. What should you do?
Move the data to a Cloud Storage bucket, and mount the bucket on the filesystem using Cloud Storage FUSE.
Move the data to a Cloud Storage bucket, and copy the data to the boot disk of the instance via a startup script.
Move the data to a Compute Engine persistent disk, and attach the disk in read-only mode to multiple Compute Engine virtual machine instances.
Move the data to a Compute Engine persistent disk, take a snapshot, create multiple disks from the snapshot, and attach each disk to its own instance.
ユーザの投票
コメント(9)
C: https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms#use-multi-instances Share a disk in read-only mode between multiple VMs Sharing static data between multiple VMs from one persistent disk is "less expensive" than replicating your data to unique disks for individual instances.
https://cloud.google.com/compute/docs/disks/gcs-buckets#mount_bucket Mounting a bucket as a file system You can use the Cloud Storage FUSE tool to mount a Cloud Storage bucket to your Compute Engine instance. The mounted bucket behaves similarly to a persistent disk even though Cloud Storage buckets are object storage.
https://github.com/GoogleCloudPlatform/gcsfuse/ Cloud Storage FUSE performance issues: Latency, Rate limit
👍 7celia202004102021/07/18Option: C is correct. https://cloud.google.com/compute/docs/disks/add-persistent-disk#use-multi-instances
Option-A: Technically will work. But not low latency. https://cloud.google.com/compute/docs/disks/gcs-buckets#mount_bucket
👍 4StelSen2021/02/18- 正解だと思う選択肢: C
C is correct
👍 2tomato1232022/08/19
シャッフルモード