Question 160
A production team wants all trained models and associated data lineage linked to the same run. What MLflow logging practice helps?
Explanation
Correct Answer
Consistent run linkage provides provenance between training inputs, metrics, and resulting model versions.
Incorrect Answers
Log or register the MLflow model with an input-output model signature. A separate source case supports that approach when: A model's inference signature is missing, causing downstream clients to send unsupported column names. The supporting rationale or observable result is: A model signature documents the expected schema and reduces integration mistakes between training and consuming applications. This question describes a different issue: A production team wants all trained models and associated data lineage linked to the same run. Address it through Log the model artifact and relevant dataset or run metadata under the same tracked run, with the required justification or evidence: Consistent run linkage provides provenance between training inputs, metrics, and resulting model versions.
Configure MLflow to use the workspace's Azure Machine Learning tracking URI. This is useful for the distinct issue: A team performs training from a laptop but wants MLflow runs visible in its Azure ML workspace. The relevant technical rationale or evidence for that issue is: The remote tracking endpoint associates externally launched runs with the intended workspace rather than an unrelated local MLflow store. Here the reported issue is: A production team wants all trained models and associated data lineage linked to the same run. The relevant response is: Log the model artifact and relevant dataset or run metadata under the same tracked run. The first result cannot verify this different correction: Consistent run linkage provides provenance between training inputs, metrics, and resulting model versions.
Log the confusion-matrix file as an MLflow run artifact. It addresses another case: A data scientist needs to preserve a confusion-matrix image generated during evaluation alongside an MLflow run. For that case, the distinguishing justification or acceptance check is: Artifacts capture supplementary files such as plots and reports that are not scalar parameters or metrics. The present case instead states: A production team wants all trained models and associated data lineage linked to the same run. It calls for Log the model artifact and relevant dataset or run metadata under the same tracked run. Showing success for the other case would not establish: Consistent run linkage provides provenance between training inputs, metrics, and resulting model versions.