A public-health clinic assistant image must stay close to regional App Service deployments across the state. How should the team place the images in Azure Container Registry?
Select an answer to reveal the explanation.
Short Explanation
Pulling a clinic assistant image from the far side of the country is like trucking vaccines across the state for every clinic refill. Geo-replicate ACR (or place registries near each App Service region) so regional hosts grab a nearby copy instead of hauling bits across the WAN.
Full Explanation
ACR geo-replication (or placing registries near each App Service region) keeps container pulls local to the compute that runs them. A public-health clinic assistant image that must stay close to regional App Service deployments benefits from replicas in each region: pull latency drops, dependency on a single distant registry shrinks, and regional outages are less likely to block every clinic host from starting new instances. Geo-replication presents a single registry endpoint while distributing image content, which fits multi-region municipal App Service layouts without changing application image references for each site.
Keeping a single non-replicated registry in one region and accepting cross-region pull latency everywhere fails proximity and resilience goals when the assistant must serve statewide App Service regions efficiently. Hosting images only on a developer workstation and syncing overnight with robocopy fails enterprise registry operations entirely—laptops are not highly available private registries and cannot support authenticated regional pulls at scale. Mirroring images into public Docker Hub for anonymous regional pulls fails municipal privacy and control: public anonymous distribution is not an appropriate private-image strategy for clinic AI workloads.
Exam caveat: Geo-replication is an ACR Premium capability in Microsoft’s model; regional placement of separate registries is an alternative design. The exam concept is “pull images from nearby registry capacity,” not a specific SKU name. ACR still requires proper authentication (for example AcrPull via managed identity) even when geo-replicated.
Operational check: Map each App Service region hosting the clinic assistant to an ACR replica or nearby registry. Measure cold-start pull times from those regions, confirm the same image digest is available in each replica, and verify regional hosts authenticate to ACR rather than falling back to a distant single-region registry or a public Hub mirror.