Question 90
A compliance team needs to know which workspace produced a model later shared through the central registry. What provenance should be retained?
Explanation
Correct Answer
Origin and run lineage distinguish the producing experiment from workspaces that merely consume the same registry version.
Incorrect Answers
Publish the canonical environment asset version to a separately governed central registry. It addresses another case: A workspace loses a locally published environment after cleanup, but several teams still need its reviewed version. For that case, the distinguishing justification or acceptance check is: Central registries decouple shared asset availability from any one development workspace's lifecycle and cleanup policy. The present case instead states: A compliance team needs to know which workspace produced a model later shared through the central registry. It calls for Capture the origin workspace and generating training job in registered model metadata. Showing success for the other case would not establish: Origin and run lineage distinguish the producing experiment from workspaces that merely consume the same registry version.
The alternative, Verify the requesting identity's registry-level access permissions, belongs to a different technical condition: A new project cannot read a model from the organization's registry although the asset exists. There the source-specific mechanism or proof is: Registry assets have access-control requirements distinct from merely being a member of the destination workspace. The condition asked about here is: A compliance team needs to know which workspace produced a model later shared through the central registry. A suitable correction is Capture the origin workspace and generating training job in registered model metadata; the targeted justification or result is: Origin and run lineage distinguish the producing experiment from workspaces that merely consume the same registry version.
Retain the earlier explicit component asset version in the historical pipeline definition. That operation would be relevant if: A registry-backed component is updated, but an existing batch pipeline must reproduce last month's scores. Its corresponding reason or verification is: Immutable historical version references preserve the exact executable component while newer versions remain separately available. However the problem in this question is: A compliance team needs to know which workspace produced a model later shared through the central registry. The requirement instead calls for Capture the origin workspace and generating training job in registered model metadata; the question-specific check is: Origin and run lineage distinguish the producing experiment from workspaces that merely consume the same registry version.