PROFESSIONAL-CLOUD-DEVELOPER Question #192: Real Exam Question with Answer & Explanation

Question

Your organization has recently begun an initiative to replatform their legacy applications onto Google Kubernetes Engine. You need to decompose a monolithic application into microservices. Multiple instances have read and write access to a configuration file, which is stored on a shared file system. You want to minimize the effort required to manage this transition, and you want to avoid rewriting the application code. What should you do?

Options

• ACreate a new Cloud Storage bucket, and mount it via FUSE in the container.
• BCreate a new persistent disk, and mount the volume as a shared PersistentVolume.
• CCreate a new Filestore instance, and mount the volume as an NFS PersistentVolume.
• DCreate a new ConfigMap and volumeMount to store the contents of the configuration file.

Explanation

https://kubernetes.io/docs/concepts/storage/volumes/#nfs An nfs volume allows an existing NFS (Network File System) share to be mounted into a Pod. Unlike emptyDir, which is erased when a Pod is removed, the contents of an nfs volume are preserved and the volume is merely unmounted. This means that an NFS volume can be pre- populated with data, and that data can be shared between pods. NFS can be mounted by multiple writers simultaneously.

No community discussion yet for this question.