A public-library consortium wants the same container repository available in two Azure regions so App Service pulls stay local. Which ACR capability unlocks that multi-region pull pattern?
Select an answer to reveal the explanation.
Short Explanation
Want the same shelves in two cities? That is ACR Premium geo-replication—not a Basic registry trick and not “stand up AKS twice.” One Premium registry, replicas where your App Service apps pull.
Full Explanation
Multi-region pull locality for the public-library consortium comes from Azure Container Registry Premium geo-replication. With geo-replication enabled, the same repository and tags are available through regional endpoints so App Service instances in each region can pull nearby instead of crossing long distances to a single registry home region.
Geo-replication is not available as a Basic SKU feature you simply toggle while staying on Basic; Premium is the SKU that unlocks this capability. Deploying AKS in both regions does not turn a registry into a multi-region image store—AKS consumes registries, it does not replace ACR replication. Blob soft delete on underlying storage is a data-protection setting for accidental deletes; it does not replicate tags to a second Azure region for local pulls.
Exam caveat: geo-replication keeps tags synchronized, but each region still enforces authentication. Webhooks and retention policies should be planned with replicas in mind so cleanup and notifications behave as expected across locations.
Operational check: upgrade or create a Premium registry, add the second region replica, push a test tag once, then from each regional App Service (or a VM in each region) pull loginServer/repo:tag and confirm pulls succeed locally without changing repository names between regions.