Google Professional Cloud DevOps Engineer
Get started today
Ultimate access to all questions.
You have production services running in Google Kubernetes Engine (GKE) in the eu-west-1 region, while your build system operates in the us-west-1 region. To optimize bandwidth for transferring container images from the build system to the GKE cluster, which scalable registry solution should you use?
You have production services running in Google Kubernetes Engine (GKE) in the eu-west-1 region, while your build system operates in the us-west-1 region. To optimize bandwidth for transferring container images from the build system to the GKE cluster, which scalable registry solution should you use?
Explanation:
The goal is to maximize bandwidth for transferring container images to the GKE cluster in eu-west-1. Google Container Registry (GCR) offers region-specific hostnames to optimize latency and bandwidth. Option C (eu.gcr.io) stores images in the European multi-region, aligning with the cluster's location (eu-west-1). This minimizes cross-region data transfer costs and latency when the cluster pulls images, while GCR's scalability ensures high bandwidth. Option A (gcr.io) defaults to a global endpoint, which may not prioritize European regions. Option B (us.gcr.io) stores images in the US, increasing latency for the European cluster. Option D uses a private registry in eu-west-1, but a Compute Engine instance is less scalable and requires manual management compared to GCR.