A containerized legacy app reads configuration from an NFS share; it must not serve traffic until the config is available. How should you deploy to GKE?
Choose an answer
Tap an option to check your answer.
Correct answer: Create a PersistentVolumeClaim in the GKE cluster, mount the volume for the config files, and start the service from an ENTRYPOINT script..
Why this is the answer
The correct answer is to create a PersistentVolumeClaim (PVC) and mount it. This is the standard, cloud-native way to provide persistent storage, like an NFS share, to a containerized application in GKE. The container can then access the configuration files directly from the mounted volume. Using an ENTRYPOINT script ensures the service only starts after the configuration is accessible. Running gsutil inside the container is inefficient and couples the application to Google Cloud Storage, which isn't the source of truth (NFS). Baking configuration into the Docker image with COPY makes the image less flexible and requires rebuilding for config changes. Adding a startup script on GKE nodes is an anti-pattern for GKE; it's not scalable, difficult to manage, and bypasses Kubernetes' native storage mechanisms.
Pass your exam — without the endless answer hunt
Get every verified question and explanation for this exam in one place, and save hours of prep. 1,000+ certifications · 20+ languages · free to start.
Pass your exam faster → No card needed