Question 20
An AML compute subnet connects privately to a hierarchical-namespace Azure Storage account. Blob reads succeed over `account.blob.core.windows.net`, but an ADLS Gen2 operation that creates a directory fails because `account.dfs.core.windows.net` resolves publicly. Public network access is disabled. What network configuration fixes this *DFS-specific* failure?
Explanation
Correct Answer
Data Lake `dfs` APIs use a separate storage subresource from Blob APIs. A Blob private endpoint cannot serve every DFS operation; the DFS endpoint and private DNS must be available from compute.
Incorrect Answers
The Blob path already works and public access is deliberately blocked. Removing private connectivity worsens access and does not provide a DFS private endpoint.
The observed failure is name resolution and routing to DFS, not an ACL or Azure RBAC denial. More data rights cannot make the DFS hostname resolve privately.
Application dependencies do not create a DNS zone or a Private Link endpoint for the DFS service subresource.