A statewide health-assistant image must be available close to several regional App Service deployments. What ACR topology should the municipal cloud team prefer?

ACR geo-replication (or an equivalent multi-region registry design) places the statewide health-assistant image near regional App Service deployments, so hosts can pull from nearby replicas rather than crossing the WAN to one distant registry. Lower pull latency and greater resilience for regional deployments matter when the same municipal image must be available close to several regions. A single non-replicated ACR in a distant region fails by concept because every regional host must pull over a potentially high-latency WAN path, while the registry is a single geographic dependency. Copying images to USB drives and mailing them overnight is not an Azure registry topology, breaks automation, and cannot support timely regional deployments. Publishing the production image anonymously on a public gallery without a regional strategy abandons private municipal control and provenance, and does not plan for regional placement. Exam caveat: Geo-replication synchronizes tags across regions, but access control, private endpoints or firewall rules as needed, and consistent image-promotion practices remain necessary. Nearby replicas do not prevent pull failures if regional replica health or permissions break. Practical check: Enable ACR geo-replication for the regions hosting the health-assistant App Service apps, deploy from each region, compare pull times with the single-region baseline, and verify that only authorized municipal identities can pull. Confirm disaster drills still succeed if one registry region is unavailable.