Answer-first summary for fast verification
Answer: Move the data to a Compute Engine persistent disk, and attach the disk in read-only mode to multiple Compute Engine virtual machine instances.
The question requires sharing a large read-only dataset across a managed instance group (MIG) with low latency, fast instance startup, and minimal cost. - **Option A** (Cloud Storage FUSE) introduces network latency since Cloud Storage is object storage, making it unsuitable for very low latency requirements. - **Option B** (copy data via startup script) slows down instance startup due to data transfer time, especially for large datasets, and incurs Cloud Storage egress costs. - **Option C** (shared read-only persistent disk) allows multiple instances to attach the same persistent disk in read-only mode. This ensures low latency (block storage), fast startup (no data copying), and minimal cost (single disk storage). - **Option D** (snapshot-derived disks) creates multiple disks from a snapshot, increasing storage costs and potentially introducing latency during on-demand data loading from the snapshot. Option C is optimal: it meets all requirements by leveraging a shared persistent disk for cost efficiency, low latency, and quick instance initialization.
Author: LeetQuiz Editorial Team
Ultimate access to all questions.
Your application runs on a managed instance group, and you need to share a large read-only dataset across all instances. The requirements are:
What is the optimal approach?
A
Move the data to a Cloud Storage bucket, and mount the bucket on the filesystem using Cloud Storage FUSE.
B
Move the data to a Cloud Storage bucket, and copy the data to the boot disk of the instance via a startup script.
C
Move the data to a Compute Engine persistent disk, and attach the disk in read-only mode to multiple Compute Engine virtual machine instances.
D
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.
No comments yet.