Question 730
Storage account `stbilling` has an approved Blob private endpoint in VNet `vnet-billing`. The `privatelink.blob.core.windows.net` private zone is already linked to the client VNet. After the endpoint was replaced, its new private IP is 10.17.4.9, but a previously hand-maintained A record for `stbilling` still points to the deleted endpoint at 10.17.4.6. DNS clients reliably receive that obsolete record; cache expiry is not the cause. The team wants future endpoint replacements to update DNS records without manual IP edits. Which change directly addresses the record-lifecycle problem?
Explanation
Correct Answer
A private DNS zone group ties a private endpoint to the correct private DNS zone and manages its endpoint A records when endpoint configuration changes. After reconciling the obsolete hand-authored entry, clients can resolve the normal Blob service hostname through the linked private zone to the current private IP, including after supported endpoint lifecycle changes.
Incorrect Answers
Private DNS zone VNet-link auto-registration is designed for supported VM hostnames, not to maintain service-specific Blob Private Link records. It would not replace the manually authored `stbilling` A record that is pointing to the deleted endpoint.
A service endpoint changes the private VNet route identity used when reaching a public service endpoint; it does not manage `privatelink.blob.core.windows.net` A records for a private endpoint. The obsolete private IP would remain in DNS.
Enabling universal public network access weakens the required private access boundary and does not correct a DNS response pointing to 10.17.4.6. A stale A record remains incorrect regardless of the storage firewall configuration.