You run a single Azure Container Registry (ACR) in East US on the Basic SKU. AKS clusters in East US and West Europe pull images from it, but image pulls in West Europe are slow and incur egress. You want a single login server name and automatic regional replication to minimize latency. What should you do?

Upgrading to the Premium SKU and enabling geo-replication is the correct solution because it directly addresses all requirements. The Premium SKU supports geo-replication, which automatically replicates images across specified regions. This provides a single login server name (myregistry.azurecr.io) and ensures that image pulls are served from the nearest replica, minimizing latency and egress costs for the West Europe AKS cluster. Creating a second ACR in West Europe and using ACR Tasks to mirror images would require updating AKS manifests to point to a different login server for West Europe, violating the "single login server name" requirement. Exporting images to Azure Storage and using az acr import is a manual and complex process, not providing automatic replication or a single login server. Placing Azure Traffic Manager in front of two independent registries is overly complex and doesn't provide the integrated, automatic replication and single namespace management offered by ACR geo-replication.