179 questions
No questions match those filters.
Why does production ML need data versioning, and how do...
This is one of the questions in the full AI/ML interview bank. Pro unlocks all 1789 questions; Premium includes the same bank plus the highest daily Practice limit.
See plansCode versioning by itself gives a false sense of reproducibility in ML — checking out the same commit and rerunning training can still produce a materially different model if the underlying data has changed since, and in a live pipeline the data is almost always changing. The fix is treating data with the same discipline as code: every meaningful dataset gets a version identifier, and every trained model logs exactly which data version it was trained on.
DVC does this by tracking a lightweight pointer file in Git while the actual data sits in object storage, so a git checkout combined with a dvc pull recreates the exact dataset a historical commit used. Delta Lake takes a different route, versioning a data lake table itself so any past state can be queried with a versionAsOf parameter — no separate pointer file needed.
The real payoff shows up during debugging: a model that quietly regressed is much easier to diagnose when the experiment tracker can say “trained on data version 1.31” and that exact snapshot can be pulled back down and diffed against the version the current model trained on, rather than the team having to guess which data changed.