A ferry kiosk bookmarks the Azure Container Instances public IP, then the group restarts during platform maintenance and the IP changes. What should clients use instead for a stabler public address?
Select an answer to reveal the explanation.
Short Explanation
An ACI public IP is a hotel room number that can change after maintenance. Use the DNS name label—or another stable front door—so kiosks keep the same name even when the room number moves.
Full Explanation
ACI public IP addresses are not a reliable long-term client contract across recreations. When the ferry kiosk bookmarks the container group’s public IP and platform maintenance restarts the group, that IP can change and bookmarks break. Prefer the ACI DNS name label (*.azurecontainer.io) or another stable external front door so clients keep a name that continues to resolve after recycling.
Hard-coding the previous IP in DNS TXT records does not make browsers use a retired address and misuses TXT data for what should be an A/AAAA or CNAME style client target. Disabling restarts permanently is unrealistic for platform maintenance and rests on the false claim that ACI public IPs never change when groups recycle. Publishing only through ACR’s login server FQDN is wrong because the registry endpoint authenticates image pull—it does not load-balance live application traffic for running containers.
Exam caveat: DNS name labels must be unique within the region, and clients should respect DNS TTLs rather than permanently caching a resolved IP they observed once.
Operational check: assign a DNS name label on the group, point the kiosk at that FQDN, recreate the group after a simulated maintenance restart, and confirm the name still reaches the service while any bookmark to the old raw IP fails.