A company is migrating its on-premises application to Google Cloud. The application requires low-latency access to a shared filesystem that can be mounted by multiple Compute Engine instances across different zones. Which storage solution should they use?
Trap 1: Create a Persistent Disk and attach it to all instances.
Persistent Disk is block storage and cannot be attached to multiple instances across zones for shared access.
Trap 2: Attach Local SSD to each instance and replicate data between them.
Local SSD is ephemeral and cannot be shared across instances, replication would add complexity and latency.
Trap 3: Use Cloud Storage FUSE to mount a bucket on each instance.
Cloud Storage is object storage and does not provide POSIX semantics required for shared filesystem.
- A
Provision a Filestore instance and mount it on the instances.
Filestore provides a managed NFS filesystem that can be mounted by multiple VMs across zones for low-latency shared access.
- B
Create a Persistent Disk and attach it to all instances.
Why wrong: Persistent Disk is block storage and cannot be attached to multiple instances across zones for shared access.
- C
Attach Local SSD to each instance and replicate data between them.
Why wrong: Local SSD is ephemeral and cannot be shared across instances, replication would add complexity and latency.
- D
Use Cloud Storage FUSE to mount a bucket on each instance.
Why wrong: Cloud Storage is object storage and does not provide POSIX semantics required for shared filesystem.