Learn the vocabulary of tracking dataset snapshots so a past training run can always be reproduced.
0 / 5 completed
1 / 5
A teammate explains that a machine learning team tracks every dataset used to train a model with a unique version identifier, similar to how source code is version-controlled, so a model's training run can always be traced back to the exact dataset snapshot that produced it, even after the underlying data has since been updated. What dataset-reproducibility practice is being described?
Data versioning tracks every dataset used to train or evaluate a model with a unique, immutable version identifier, the way source code is tracked with commit hashes, so a specific training run can always be traced back to the exact dataset snapshot that produced it, even after the underlying data has since been updated, corrected, or grown with new records. A DNS zone transfer is an unrelated concept about replicating name server records. This version-datasets-like-source-code approach is exactly why data versioning is what lets a team reproduce or debug a model trained months ago even after the live dataset has changed substantially since then.
2 / 5
During a design review, the team adopts data versioning for a model-debugging investigation into why a model trained three months ago behaves differently from one trained last week, specifically so the investigation can compare the exact dataset snapshot each model was trained on. Which capability does this provide?
Data versioning here provides exact reproducibility of the training data behind any past model, since each training run's dataset version identifier points to an immutable snapshot rather than a live, continuously changing table. Pointing every training run at the same live, continuously updated table with no snapshot preserved, so the exact data a past run trained on can never be reconstructed is the alternative this avoids. This behavior is exactly why data versioning is favored in this kind of scenario.
3 / 5
In a code review, a dev notices a training pipeline points every run at the same live, continuously updated table with no versioned snapshot preserved, so nobody can reconstruct exactly what data a model trained three months ago actually saw, instead of recording a data versioning identifier for each run. What does this represent?
This is a missed data versioning-opportunity, since data versioning would preserve an immutable snapshot identifier for each run instead of leaving every run pointed at an ever-changing live table. A cache eviction policy is an unrelated concept about discarded cache entries. This pattern is exactly the kind of gap a reviewer flags once the tradeoffs are understood.
4 / 5
An incident report shows a debugging investigation into a model's regressed accuracy stalled for days because the training pipeline had always pointed at the same live table, and nobody could determine what that table's contents actually looked like at the time the regressed model was trained. What practice would prevent this?
Adopting data versioning so every training run records an immutable snapshot identifier, letting a past run's exact training data always be reconstructed. Continuing the prior approach regardless of the risk it has already caused is exactly what led to the incident described here. This fix is the standard remedy once the root cause is confirmed.
5 / 5
During a PR review, a teammate asks why the team reaches for data versioning instead of always training against the same live, continuously updated table. What is the reasoning?
data versioning trades the storage cost and tooling overhead of preserving immutable dataset snapshots for guaranteed reproducibility of any past training run, while training against a live table avoids that storage overhead but makes past runs impossible to reconstruct once the table has changed. This is exactly why data versioning is favored when reproducibility and auditability of past training runs matters, such as in regulated domains, while always training against the same live, continuously updated table remains acceptable when storage is tightly constrained and reconstructing past runs is not a real requirement.
What does the "Data Versioning Vocabulary" vocabulary exercise cover?
This exercise tests real IT vocabulary related to data versioning vocabulary through 5 multiple-choice questions, each built from realistic workplace sentences rather than abstract definitions.
Is this vocabulary exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is completely free — no account, sign-up, or payment required.
How many questions does this exercise have?
This exercise has 5 questions. Each one shows a real-world sentence or scenario with multiple-choice options and an explanation once you answer.
What happens after I answer a question?
You'll see immediate feedback showing whether your answer was correct, along with a short explanation of why — then a button to move to the next question, and a full results screen at the end.
Can I retry the exercise if I get questions wrong?
Yes. Once you reach the results screen, click "Try again" to reset your answers and go through the exercise from the start as many times as you like.
Do I need to create an account to take this exercise?
No account is needed. Your answers are scored in your browser during the session — nothing is saved to a server, so you can jump straight in.
Is my progress saved if I leave the page?
No — progress within an exercise resets if you navigate away or reload. Each exercise is short enough to complete in a few minutes in one sitting.
Are these vocabulary exercises connected to other topics?
Yes — browse the full vocabulary exercises hub to find related modules covering adjacent IT topics and roles.
How is this different from reading a glossary or blog article?
Exercises like this one are active recall drills — you have to choose the correct term or phrasing yourself, which builds retention faster than passively reading a definition.
Where can I find more vocabulary exercises?
Browse the full Vocabulary exercises hub for hundreds of modules covering Agile, DevOps, security, databases, architecture, and more — organised by IT role and skill.