Google Cloud Certified Associate Cloud Engineer Practice

In Google Cloud, where do container images need to exist for Kubernetes to work with them?

1. Service Accounts

2. Stackdriver

3. Pub/Sub

4. A container registry

The correct answer is: A container registry

Kubernetes needs access to container images to deploy applications, and the appropriate location for these images is a container registry. Google Cloud has its own fully managed container registry service known as Google Container Registry (GCR) or the newer Artifact Registry. When you push your container images to a registry, Kubernetes can pull those images as needed during the deployment of your applications. This setup allows for efficient image management, version control, and security, as the registry can enforce access controls and manage authentication for pulling images. Relying on a proper registry ensures that Kubernetes has reliable access to the images it requires. The other options presented do not serve as suitable locations for storing container images. Service Accounts are used for managing permissions and access rights in Google Cloud but are not a repository for container images. Stackdriver, now known as Google Cloud Operations Suite, provides monitoring and logging services, which are vital for performance tracking but do not store container images. Pub/Sub is a messaging service designed for real-time messaging between applications and would not host container images either.