AZ-305 Practice Question 88: ACR Geo Replication Clusters
Microsoft Azure Solutions Architect Expert (AZ-305) · Test 9 · question 8 of 10
A company runs Azure Kubernetes Service clusters in West Europe, East US, and Southeast Asia, each pulling the same container images on every deployment and during autoscaling events. Today all three clusters pull from a single Azure Container Registry in West Europe, and the operations team has noticed slow image pulls and extra data transfer charges from the two remote regions. The design must keep a single registry name and a single image tag that every pipeline and cluster references, while making pulls fast and cheap from all three regions, and it must keep working without changes to deployment manifests if the West Europe region becomes unavailable.
What should you recommend?
Show answer and explanation
Answer:
Geo-replication, available on the Premium tier, maintains one registry resource with one login server name and one set of tags, while automatically synchronizing image layers to replicas in the regions you choose. Each cluster's local replica serves pulls with regional latency and no cross-region data transfer charge, manifests never change because the registry name stays the same, and if one region goes down the registry keeps serving from the others.
Option A gives every region its own registry, so pipelines would need to push to and clusters would need to reference three different registry names, breaking the "single registry name" requirement and losing automatic synchronization between them.
Option B caches static content at the edge, but Azure Container Registry's image pull protocol is not a Content Delivery Network scenario Azure supports this way, and it would not provide automatic, registry-aware replication or resilience if the origin registry's region fails.
Option D can route traffic to endpoints, but the registry itself would still be a single-region resource behind it; Traffic Manager has nothing local to route to in East US or Southeast Asia unless a replicated registry already exists there.
Reference: Geo-replication in Azure Container Registry