Question 40
A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. What should the administrator evaluate?
Explanation
Correct Answer
Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.
Incorrect Answers
Use a dedicated federated or managed workload identity with minimal Azure RBAC. It addresses another case: A GitHub deployment workflow needs access to Azure ML without storing an administrator password. For that case, the distinguishing justification or acceptance check is: Workload identity avoids persistent administrator secrets and can be constrained to the specific resources it deploys. The present case instead states: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. It calls for Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access. Showing success for the other case would not establish: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.
The alternative, Grant a task-scoped Azure ML role at workspace scope instead of subscription Owner, belongs to a different technical condition: A junior operator needs to submit ML training jobs but must not change workspace networking or grant user roles. There the source-specific mechanism or proof is: Least-privilege workspace RBAC permits job operations without broad control over security or billing resources. The condition asked about here is: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. A suitable correction is Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access; the targeted justification or result is: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.
Give the endpoint deployment's runtime identity the necessary feature-store data permissions. That operation would be relevant if: A production endpoint can fetch its model but cannot read a secured feature store at inference time. Its corresponding reason or verification is: Production inference uses its execution identity; author privileges do not automatically travel to the deployed container. However the problem in this question is: A contractor needs read-only access to experiment metrics but no ability to download sensitive datasets. The requirement instead calls for Use narrowly scoped roles and separate storage data-plane permissions for experiment versus dataset access; the question-specific check is: Workspace metadata permission does not automatically define every storage grant; separate resource policies protect restricted data.