Question 420
A private endpoint is successfully provisioned, but client DNS resolves the Foundry hostname to a public IP. What should be repaired?
Explanation
Correct Answer
Private endpoint approval alone cannot route clients privately when hostname resolution still returns public destinations.
Incorrect Answers
The alternative, Complete endpoint approval and verify the target resource's network configuration, belongs to a different technical condition: A developer changes the service's DNS record to a private address but the private endpoint connection is not approved. There the source-specific mechanism or proof is: DNS alone cannot make an unapproved private endpoint usable; the endpoint's resource connection must be authorized. The condition asked about here is: A private endpoint is successfully provisioned, but client DNS resolves the Foundry hostname to a public IP. A suitable correction is Configure the appropriate private DNS zone and forwarding for the endpoint; the targeted justification or result is: Private endpoint approval alone cannot route clients privately when hostname resolution still returns public destinations.
Establish approved VNet routing or peering and name resolution for the second network. That operation would be relevant if: A model deployment works from one subnet but fails from a second VNet that has no peering to the private endpoint network. Its corresponding reason or verification is: Private endpoint access depends on supported network connectivity between the caller and the endpoint address. However the problem in this question is: A private endpoint is successfully provisioned, but client DNS resolves the Foundry hostname to a public IP. The requirement instead calls for Configure the appropriate private DNS zone and forwarding for the endpoint; the question-specific check is: Private endpoint approval alone cannot route clients privately when hostname resolution still returns public destinations.
Review private endpoint addresses and DNS zone associations for the new regional deployment. A separate source case supports that approach when: A team has private endpoints but deploys a new project in another region and assumes the same DNS records apply automatically. The supporting rationale or observable result is: Private address resolution is tied to actual deployed endpoint resources and cannot be assumed from another environment. This question describes a different issue: A private endpoint is successfully provisioned, but client DNS resolves the Foundry hostname to a public IP. Address it through Configure the appropriate private DNS zone and forwarding for the endpoint, with the required justification or evidence: Private endpoint approval alone cannot route clients privately when hostname resolution still returns public destinations.