A company runs container workloads in West Europe and East US. Both clusters must pull images from a nearby copy, and the deployment manifests must keep using one registry login server name. The images are pushed once by a single pipeline. What should the developer set up?
Choose one.
Geo-replication turns one Premium registry into a multi-region registry with a single login server.
The two deciding requirements are a nearby copy for each region and one login server name. Geo-replication satisfies both: the pipeline pushes once, Azure replicates the content, and DNS routes each pull to the closest replica. Separate registries also give nearby copies but break the single-name requirement, and Standard registries cannot hold replicas at all.
- Identify the need: regional copies of the same images.
- Note the constraint: one login server and one push.
- Recall that geo-replication provides both and requires the Premium tier.
Exam tip: One login server, many regions: Premium tier with geo-replication.
AI-200 Container Hosting: Azure Container Registry, ACR Tasks and App Service Containers — the lesson that teaches this.