Topic: Google Cloud Architect topic 1 question 123

You need to deploy a stateful workload on Google Cloud. The workload can scale horizontally, but each instance needs to read and write to the same POSIX filesystem. At high load, the stateful workload needs to support up to 100 MB/s of writes. What should you do?

A.
Use a persistent disk for each instance.
B.
Use a regional persistent disk for each instance.
C.
Create a Cloud Filestore instance and mount it in each instance.
D.
Create a Cloud Storage bucket and mount it in each instance using gcsfuse.

Re: Google Cloud Architect topic 1 question 123

Answer should be C,
https://cloud.google.com/storage/docs/gcs-fuse#notes

Re: Google Cloud Architect topic 1 question 123

Agreed - C

Re: Google Cloud Architect topic 1 question 123

https://cloud.google.com/filestore

Re: Google Cloud Architect topic 1 question 123

"“Cloud Storage FUSE is an open source [FUSE](http://fuse.sourceforge.net/) adapter that allows you to mount Cloud Storage buckets as file systems on Linux or macOS systems. It also provides a way for applications to upload and download Cloud Storage objects using standard file system semantics. Cloud Storage FUSE can be run anywhere with connectivity to Cloud Storage, including Google Compute Engine VMs or on-premises systems[**1**](https://cloud.google.com/storage/docs/gcs-fuse#f1-note)."

D says "gcsfuse", should be D

Re: Google Cloud Architect topic 1 question 123

FUSE is not posix

Re: Google Cloud Architect topic 1 question 123

directly from the documentation of gcs fuse > While Cloud Storage FUSE has a file system interface, it is not like an NFS or CIFS file system on the backend. Additionally, Cloud Storage FUSE is not POSIX compliant. For a POSIX file system product in Google Cloud, see Filestore.

Re: Google Cloud Architect topic 1 question 123

Google Cloud Storage Fuse is not POSIX compliant so C

Re: Google Cloud Architect topic 1 question 123

Not, you need a file system not a blob storage...

  • decw
  • New member
  • Offline

Re: Google Cloud Architect topic 1 question 123

''While Cloud Storage FUSE has a file system interface, it is not like an NFS or CIFS file system on the backend. Additionally, Cloud Storage FUSE is not POSIX compliant. For a POSIX file system product in Google Cloud, see Filestore.''

  • XDevX
  • New member
  • Offline

Re: Google Cloud Architect topic 1 question 123

IMHO d) is wrong, the correct answer is c).
The requirement is explicitly POSIX filesystem - using gcsfuse Cloud Storage still remains an object storage - IMHO gcsfuse brings a lot of downsizes compared with Filestore and in the question there are no indications that a non-POSIX filesystem shall be used.

  • enado
  • New member
  • Offline

Re: Google Cloud Architect topic 1 question 123

Additional google explicitly states that Cloud Storage fuse is not POSIX compliant
https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations

  • enado
  • New member
  • Offline

Re: Google Cloud Architect topic 1 question 123

So the correct answer is C

Re: Google Cloud Architect topic 1 question 123

From https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations
Cloud Storage FUSE is not POSIX compliant. For a POSIX file system product in Google Cloud, see Filestore.

Re: Google Cloud Architect topic 1 question 123

https://cloud.google.com/storage/docs/gcs-fuse#notes

Re: Google Cloud Architect topic 1 question 123

C is correct, Per documentation ( Cloud Storage FUSE is not POSIX compliant. For a POSIX file system product in Google Cloud, see Filestore)

Re: Google Cloud Architect topic 1 question 123

https://cloud.google.com/storage/docs/gcs-fuse, not POSIX complieant.

Re: Google Cloud Architect topic 1 question 123

C


Explanation:
A & B: persistent disk won't be shared. Question says "each instance needs to read and write to the same POSIX filesystem." Although, now u can share persistent disk(https://cloud.google.com/compute/docs/disks/sharing-disks-between-vms#:~:text=Note%3A%20You%20can%20share%20Persistent%20Disk%20volumes%20only%20with%20VMs%20that%20are%20in%20the%20same%20zone%20as%20the%20disk.) but question doesnt mention that all VMs are in same zone as disk.

C: Filestore ideal for NFS and POSIX

D: shared access can be achieved using GCSFuse, still, it's not POSIX complaint (https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations)

Re: Google Cloud Architect topic 1 question 123

Yes, the correct answer is C:
LIMITATIONS: "While Cloud Storage FUSE has a file system interface, it is not like an NFS or CIFS file system on the backend. Additionally, Cloud Storage FUSE is not POSIX compliant. For a POSIX file system product in Google Cloud, see Filestore."
https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations

Re: Google Cloud Architect topic 1 question 123

You need a file system not a blob storage...

Re: Google Cloud Architect topic 1 question 123

As per the documentation, https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations. The option is C.

Re: Google Cloud Architect topic 1 question 123

firestore is POSIX

Re: Google Cloud Architect topic 1 question 123

Could anyone please tell why A or B is wrong? Thanks

Re: Google Cloud Architect topic 1 question 123

https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations
Answer C because POSIX and FUSE are not compatible. Google recommends using Filestore to address POSIX file operations

Re: Google Cloud Architect topic 1 question 123

Answer is C
https://cloud.google.com/storage/docs/gcs-fuse
Clearly mentioned to see filestore for POSIX