Topic 1 Question 175
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?
Create a new Cloud Storage bucket, and mount it via FUSE in the container.
Create a new persistent disk, and mount the volume as a shared PersistentVolume.
Create a new Filestore instance, and mount the volume as an NFS PersistentVolume.
Create a new ConfigMap and volumeMount to store the contents of the configuration file.
ユーザの投票
コメント(5)
- 正解だと思う選択肢: C
A is incorrect, because Cloud Storage FUSE does not support concurrency and file locking. B is incorrect, because a persistent disk PersistentVolume is not read-write-many. It can only be read-write once or read-many. C is correct, because it’s the only managed, supported read-write-many storage option available for file-system access in Google Kubernetes Engine. D is incorrect, because the ConfigMap cannot be written to from the Pods.
https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes https://cloud.google.com/filestore/docs/accessing-fileshares https://cloud.google.com/storage/docs/gcs-fuse
👍 4x_cath2022/12/23 - 正解だと思う選択肢: D
D is the answer.
https://cloud.google.com/kubernetes-engine/docs/concepts/configmap ConfigMaps bind non-sensitive configuration artifacts such as configuration files, command-line arguments, and environment variables to your Pod containers and system components at runtime.
A ConfigMap separates your configurations from your Pod and components, which helps keep your workloads portable. This makes their configurations easier to change and manage, and prevents hardcoding configuration data to Pod specifications.
👍 2zellck2022/12/15 - 正解だと思う選択肢: C
Generally ConfigMaps (D) are the right choice to store pod config-files, but: They are read-only, which does not match what is asked for here. If, as stated in the question, the application-parts need to be able to also write to that Configfile that should be on a shared file system, the only valid choice is a NFS PV.
👍 2Underverse2022/12/20
シャッフルモード