MLOps1 / 5
A machine learning engineer needs to implement an MLOps practice where every model training run is linked to the exact Git commit of the training code, the specific version of the training data, and the resulting model artifact. What ensures this end-to-end traceability?
CorrectIncorrect
Alex
MLOps provenance chain: 1) Code → Run: Databricks Repos: automatic Git integration. MLflow: logs notebook path and Git commit SHA. Reproducibility: checkout commit, rerun notebook. 2) Data → Run: Delta Lake version: exact snapshot of training data. Data hash: fingerprint of the dataset. Feature Store version: which feature table version used. Time travel: spark.read.format('delta').option('versionAsOf', 42).table('training_data'). 3) Run → Model: MLflow run contains: parameters, metrics, artifacts. Model registered from run: linked via run_id. Model Registry: version → run → code + data. 4) Model → Deployment: deployment logs: which model version is serving. Endpoint: references model URI. Inference table: logs every prediction. 5) Full chain: prediction → model version → MLflow run → (Git commit + data version) → original source code and data. 6) Automation: autologging: captures most code/model links automatically. Data logging: requires manual mlflow.log_param for data version. Unity Catalog: adds governance layer (permissions, audit logs). 7) Benefits: reproducibility: recreate any model. Auditability: satisfy compliance requirements. Debugging: find what changed when model degraded.
Sourcedocs.databricks.com
Follow-up answers are available in the app. Create a free account — no credit card required.
Question 1 of 5
Create a free account