Question 140
A private AML workspace connects to its associated Key Vault through a public DNS name and secret reads fail under a firewall policy. What is missing?
Explanation
Correct Answer
Private workspace endpoints do not substitute for Key Vault's own private DNS and network authorization requirements.
Incorrect Answers
The alternative, Configure the required private or controlled outbound path to the approved repository, belongs to a different technical condition: A shared training cluster must reach a corporate package repository through a secured route, not general internet egress. There the source-specific mechanism or proof is: A targeted egress route satisfies dependency retrieval while maintaining restrictions on unrelated internet destinations. The condition asked about here is: A private AML workspace connects to its associated Key Vault through a public DNS name and secret reads fail under a firewall policy. A suitable correction is Configure Key Vault private endpoint resolution and access from the executing environment; the targeted justification or result is: Private workspace endpoints do not substitute for Key Vault's own private DNS and network authorization requirements.
Disable or restrict workspace public network access according to the private-only policy. That operation would be relevant if: A workspace administrator enables a private endpoint but users still reach the public hostname from outside the private network. Its corresponding reason or verification is: Adding private access does not necessarily remove a public path; explicit public network settings enforce the intended perimeter. However the problem in this question is: A private AML workspace connects to its associated Key Vault through a public DNS name and secret reads fail under a firewall policy. The requirement instead calls for Configure Key Vault private endpoint resolution and access from the executing environment; the question-specific check is: Private workspace endpoints do not substitute for Key Vault's own private DNS and network authorization requirements.
Compare the subnet NSG and route policy with documented required Azure ML service endpoints. A separate source case supports that approach when: An AML compute cluster loses access after its subnet network security group is hardened. The workspace is healthy. The supporting rationale or observable result is: Network rules can deny necessary runtime communication even when workspace control-plane APIs remain available. This question describes a different issue: A private AML workspace connects to its associated Key Vault through a public DNS name and secret reads fail under a firewall policy. Address it through Configure Key Vault private endpoint resolution and access from the executing environment, with the required justification or evidence: Private workspace endpoints do not substitute for Key Vault's own private DNS and network authorization requirements.