Question 20
A job can read a datastore from a user's notebook but fails on a managed compute cluster. Why should the platform team inspect identity context?
Explanation
Correct Answer
Interactive user authorization may not transfer to managed job identities; compute execution must possess its own permitted access.
Incorrect Answers
Configure the datastore to reference the intended ADLS Gen2 filesystem and directory path. It addresses another case: An Azure ML job expects nested directories in an ADLS Gen2 container, but its configured datastore points to a different blob root. For that case, the distinguishing justification or acceptance check is: The datastore must identify the actual backing storage location; changing experiment names cannot fix a misaddressed filesystem. The present case instead states: A job can read a datastore from a user's notebook but fails on a managed compute cluster. It calls for Grant storage data access to the job's runtime identity and verify datastore authentication mode. Showing success for the other case would not establish: Interactive user authorization may not transfer to managed job identities; compute execution must possess its own permitted access.
The alternative, Review datastore resource references and cross-subscription identity permissions explicitly, belongs to a different technical condition: A workspace is moved to a new subscription and its datastore still points to the previous subscription's storage account. There the source-specific mechanism or proof is: Subscription changes do not transparently update storage references or their RBAC; the new workspace needs valid data-plane authorization. The condition asked about here is: A job can read a datastore from a user's notebook but fails on a managed compute cluster. A suitable correction is Grant storage data access to the job's runtime identity and verify datastore authentication mode; the targeted justification or result is: Interactive user authorization may not transfer to managed job identities; compute execution must possess its own permitted access.
Renew the expired delegated credential or migrate the connection to managed identity access. That operation would be relevant if: A datastore configured with a temporary SAS token worked yesterday but now returns 403 responses on every job. Its corresponding reason or verification is: Time-limited SAS credentials expire independently of the model code; credential renewal or identity-based access restores authorization. However the problem in this question is: A job can read a datastore from a user's notebook but fails on a managed compute cluster. The requirement instead calls for Grant storage data access to the job's runtime identity and verify datastore authentication mode; the question-specific check is: Interactive user authorization may not transfer to managed job identities; compute execution must possess its own permitted access.