Question 130
A private endpoint connection is approved, but clients resolve the workspace hostname to a public address. What must be fixed?
Explanation
Correct Answer
Private connectivity requires name resolution to return the private address; endpoint approval alone cannot repair a public DNS answer.
Incorrect Answers
Apply appropriate storage-account private endpoints and firewall restrictions for data-plane access. It addresses another case: A team secures the workspace using private networking but leaves its dependent storage account public. For that case, the distinguishing justification or acceptance check is: Workspace network isolation does not automatically make every linked storage account private; dependent services require their own controls. The present case instead states: A private endpoint connection is approved, but clients resolve the workspace hostname to a public address. It calls for Configure the proper private DNS zone and resolution path for the workspace private endpoint. Showing success for the other case would not establish: Private connectivity requires name resolution to return the private address; endpoint approval alone cannot repair a public DNS answer.
The alternative, Configure Key Vault private endpoint resolution and access from the executing environment, belongs to a different technical condition: A private AML workspace connects to its associated Key Vault through a public DNS name and secret reads fail under a firewall policy. There the source-specific mechanism or proof is: Private workspace endpoints do not substitute for Key Vault's own private DNS and network authorization requirements. The condition asked about here is: A private endpoint connection is approved, but clients resolve the workspace hostname to a public address. A suitable correction is Configure the proper private DNS zone and resolution path for the workspace private endpoint; the targeted justification or result is: Private connectivity requires name resolution to return the private address; endpoint approval alone cannot repair a public DNS answer.
Allow the specific required outbound destination through supported managed-network egress rules. That operation would be relevant if: An Azure ML managed virtual network is configured with restricted outbound mode; training jobs cannot download required Python packages from an approved feed. Its corresponding reason or verification is: Restricted outbound access blocks unapproved destinations until explicitly allowed; opening all internet traffic is unnecessary. However the problem in this question is: A private endpoint connection is approved, but clients resolve the workspace hostname to a public address. The requirement instead calls for Configure the proper private DNS zone and resolution path for the workspace private endpoint; the question-specific check is: Private connectivity requires name resolution to return the private address; endpoint approval alone cannot repair a public DNS answer.