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?
For stateful workloads that need to read and write to the same POSIX filesystem, Cloud Filestore is the most appropriate choice. Cloud Filestore provides a fully managed NFS file server that meets POSIX compliance requirements and supports the necessary high I/O throughput, including the requirement to support up to 100 MB/s of writes. Using a persistent disk (whether regional or not) is not suitable as each instance requires access to the same filesystem simultaneously, and mounting a Cloud Storage bucket with gcsfuse does not provide POSIX compliance, which is a crucial requirement.
Answer should be C, https://cloud.google.com/storage/docs/gcs-fuse#notes
Agreed - C
https://cloud.google.com/filestore
"“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
FUSE is not posix
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.
Google Cloud Storage Fuse is not POSIX compliant so C
Not, you need a file system not a blob storage...
''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.''
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.
Additional google explicitly states that Cloud Storage fuse is not POSIX compliant https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations
So the correct answer is C
GCFUSE does not work with POSIX File System , refer - https://cloud.google.com/storage/docs/gcs-fuse So Answer should be C
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
Answer is C https://cloud.google.com/storage/docs/gcs-fuse Clearly mentioned to see filestore for POSIX
You need a file system not a blob storage...
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
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.
Could anyone please tell why A or B is wrong? Thanks
firestore is POSIX
As per the documentation, https://cloud.google.com/storage/docs/gcs-fuse#differences-and-limitations. The option is C.
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)
https://cloud.google.com/storage/docs/gcs-fuse, not POSIX complieant.
C is correct, Per documentation ( 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#notes
C 1. "each Instance needs to read and wrlte to the same POSIX filesystem" 2. Cloud Storage is not POSIX compliant filesystem but Object Storage and gcsfuse only "simulates" file system 3. See: 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.
Answer is C As filestore can be attached to multiple pods/vm in R/W mode A & B are wrong for the same reason, PD can be attached to single pod for write operation.