Data Provenance Vocabulary
Practice data provenance vocabulary: provenance chain, external vendor data, immutable audit logs, proving data origin for regulatory purposes, and chain of custody language.
0 / 14 completed
1 / 14
What does 'data provenance' mean?
Data provenance is the documented history of data's origin, movement, and transformations. It answers: where did this data come from, who touched it, and how was it changed?
2 / 14
An auditor asks you to prove that sales data 'came from external vendor X on date Y.' What record type supports this?
An immutable audit log records exactly when data was received, from which source, and by whom — providing the evidence needed for regulatory or legal proof of data origin.
3 / 14
What is a 'provenance chain'?
A provenance chain is the complete, unbroken sequence of records showing every step data has taken — from original source through all transformations — providing full traceability.
4 / 14
The phrase 'chain of custody' in a data context means:
Chain of custody (borrowed from legal/forensic contexts) means a documented, verifiable record of every person or system that had possession or control of data, ensuring accountability.
5 / 14
Which regulatory requirement most directly demands proof of data provenance?
GDPR requires organisations to demonstrate that personal data is accurate, lawfully obtained, and properly handled. Data provenance records are essential for proving compliance during audits.
6 / 14
Reviewer: 'I'm seeing that the customer ID used here was generated by the `UserCreationService`. Before merging, can you add a comment documenting *where* this ID came from and *when* it was created? It's crucial for debugging future issues with user accounts.'
Which of the following best describes what Reviewer is asking for in this context?The reviewer isn't simply asking for a random comment; they're specifically requesting information about the origin of the customer ID – where it was generated (the `UserCreationService`) and when (creation timestamp). This highlights the importance of 'data provenance', which is understanding *how* data originated and its history. The incorrect options either misunderstand the request or offer a simplistic view that ignores the critical need for traceability in software development.
7 / 14
Reviewer: 'I'm seeing that the customer ID used here was generated by the `UserCreationService`. Before merging, can you add a comment documenting *where* this ID came from and *when* it was created? It's crucial for debugging future issues with user accounts.'
Which of the following best describes what Reviewer is asking for in this context?The reviewer isn't simply asking for a random comment; they're specifically requesting information about the origin of the customer ID – where it was generated (the `UserCreationService`) and when (creation timestamp). This highlights the importance of 'data provenance', which is understanding *how* data originated and its history. The incorrect options either misunderstand the request or offer a simplistic view that ignores the critical need for traceability in software development.
8 / 14
Reviewer: 'I'm seeing that the customer ID used here was generated by the `UserCreationService`. Before merging, can you add a comment documenting *where* this ID came from and *when* it was created? It's crucial for debugging future issues with user accounts.'
Which of the following best describes what Reviewer is asking for in this context?The reviewer isn't simply asking for a random comment; they're specifically requesting information about the origin of the customer ID – where it was generated (the `UserCreationService`) and when (creation timestamp). This highlights the importance of 'data provenance', which is understanding *how* data originated and its history. The incorrect options either misunderstand the request or offer a simplistic view that ignores the critical need for traceability in software development.
9 / 14
Reviewer: 'I'm seeing that the customer ID used here was generated by the `UserCreationService`. Before merging, can you add a comment documenting *where* this ID came from and *when* it was created? It's crucial for debugging future issues with user accounts.'
Which of the following best describes what Reviewer is asking for in this context?The reviewer isn't simply asking for a random comment; they're specifically requesting information about the origin of the customer ID – where it was generated (the `UserCreationService`) and when (creation timestamp). This highlights the importance of 'data provenance', which is understanding *how* data originated and its history. The incorrect options either misunderstand the request or offer a simplistic view that ignores the critical need for traceability in software development.
10 / 14
A developer is reviewing a PR that uses the
get_user_data function. The code comments mention 'provenance' and 'tracking data lineage.' What does this likely refer to? This ensures we can trace where the user data originated.'Data provenance' refers to the ability to trace a piece of data back to its source and understand all the steps it has undergone. It's about tracking the entire journey of the data, not just enforcing regulations or optimizing performance. Options A & D are too broad; option B is the most accurate definition.
11 / 14
During a standup meeting, a developer says, "We need to ensure the data from our new analytics pipeline has strong provenance." What's the primary concern driving this statement?
Strong data provenance is crucial when dealing with sensitive or regulated data. It's not just about speed; it's about accountability and verifying that the data used in analytics is reliable and trustworthy. Option A & D are misinterpretations of the core concept.
12 / 14
A senior engineer asks you to add a field to your API response that records the original source of a product's price. What is the primary purpose of this addition related to 'data provenance'? This helps with debugging and understanding data transformations.
Adding provenance details allows you to trace back how a product's price was calculated. This is vital for debugging issues, understanding data transformations, and ensuring accuracy. Options B & D are related to API design but don't address the core concept of provenance.
13 / 14
You're investigating a discrepancy in sales figures. The data originated from a third-party CRM system. Which of the following best describes how 'data lineage' would be most helpful in your investigation?
-
-
-
-
'Data lineage' focuses on understanding the entire journey of the data – where it came from, how it was modified, and what systems it passed through. This is essential for identifying the root cause of discrepancies. Options A & D are tangential to the core concept. 14 / 14
A data governance team mandates that all customer data be tracked with a 'provenance record'. What is the MOST important reason for this requirement?
-
-
-
-
Data provenance is fundamentally about accountability and trust. Tracking the origin and transformations of data is crucial for complying with regulations (like GDPR or CCPA), demonstrating responsible data handling practices, and ensuring that decisions are based on reliable information. Options A & D are secondary benefits. Frequently Asked Questions
What does the "Data Provenance Vocabulary" exercise practise?
Practice data provenance vocabulary: provenance chain, external vendor data, immutable audit logs, proving data origin for regulatory purposes, and chain of custody language.
How many questions are in this exercise?
This exercise has 14 questions, each multiple-choice with a full explanation shown after you answer.
What English level is this exercise for?
This exercise is tagged Intermediate. If the vocabulary feels difficult, browse the Data Lineage Vocabulary category page for an easier module to start with.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free with no account, sign-up, or paywall.
Do I get feedback if I answer incorrectly?
Yes — whichever option you choose, right or wrong, you'll immediately see an explanation clarifying the correct term and why the other options don't fit.
Can I retry this exercise?
Yes — once you finish all the questions, a "Try again" button on the results screen resets the exercise so you can practise as many times as you like.
Do I need an account to track my progress?
No account is required. Your progress bar and score for this session are tracked in the browser as you go, but nothing is saved once you leave the page.
Is "Data Provenance Vocabulary" part of a larger series?
Yes — it's one exercise in the Data Lineage Vocabulary category on CoderSlingo. See the category page for the full list of related exercises on similar terminology.
Can I link directly to this exercise?
Yes — this exercise has its own permanent URL, so you can bookmark it or share the link directly with a colleague or study partner.
Where can I find more exercises like this one?
See the Data Lineage Vocabulary category page for related exercises, or browse the main Exercises hub for other IT English topics.