Data Contract Governance Vocabulary
Practice data contract governance vocabulary: contract registry, contract owner, deprecating fields, data steward role, and governance team sign-off language.
0 / 25 completed
1 / 25
What is a 'contract registry' in a data governance context?
A contract registry is a centralized store — often a data catalog feature — that tracks all active data contracts, who owns them, their current version, and which teams are consumers.
2 / 25
The 'contract ___ ' is the person accountable for keeping a data contract accurate and up to date.
The contract owner is the accountable party — typically someone from the producing team — responsible for the contract's accuracy, versioning, and lifecycle management.
3 / 25
What does 'deprecating a contract field' mean?
Deprecating a contract field means announcing that it will be removed in a future version. Consumers see a deprecation notice and have a defined grace period to stop depending on that field.
4 / 25
What is the role of a 'data steward' in the data contract process?
A data steward is a business-side domain expert responsible for the meaning, quality, and governance of data in their domain. In data contracts, they often review and approve contract definitions.
5 / 25
A team says 'we need ___ from the data governance team before merging this contract change.' What word fits?
'Sign-off' is standard governance language meaning formal approval. Requiring sign-off from a data governance team or data steward before contract changes go live is a common governance control.
6 / 25
Reviewer: 'I'm seeing a potential issue with the `customer_address` contract field. The Slack channel discussion mentions that we're moving to a new address validation service, but this contract still uses the legacy format and lacks validation logic. It seems like we need to formally deprecate this field before any further integration work happens. This scenario highlights the importance of following a defined governance process. Simply changing systems doesn't resolve underlying issues; formally deprecating the field signals its obsolescence and triggers necessary updates across all dependent services. Ignoring the Slack discussion and proceeding without a formal process risks inconsistencies and future rework due to a lack of clear direction from the data governance team, specifically regarding lifecycle management.
7 / 25
PR Description:
"As part of the recent API v2.0 migration, we've updated the `product_name` contract to include a new field, `product_category`. This change aligns with the updated product taxonomy and ensures consistent categorization across all services. We've also removed the deprecated `product_code` field as per our data governance policies."The correct answer emphasizes the need for formal approval. While auditing is often important, the scenario explicitly mentions data governance policies regarding deprecation and addition of fields. Simply documenting changes isn't sufficient; a formal approval process ensures alignment with established rules and mitigates potential risks associated with evolving contracts. Option A is incorrect because it suggests reverting a deployed version without proper justification.
8 / 25
Reviewer: 'Okay, I'm reviewing this PR and noticed a potential conflict. The `user_id` contract field is still referencing the old database schema (v1), while the new microservice uses v2. We need to formally flag this for deprecation and update the contract accordingly, otherwise we risk data inconsistencies down the line. PR Description: 'We've updated the customer_name contract to include a new field, customer_email, to comply with GDPR regulations.'This situation highlights the importance of proactive data governance. Simply ignoring inconsistencies or assuming downstream systems will adapt is risky. The correct action is to formally deprecate the outdated field (
user_id) and initiate a contract update – this demonstrates accountability and minimizes the chance of future data discrepancies. Option A is incorrect because ignoring conflicts can lead to serious problems; option B is flawed due to assuming automatic adaptation, while option C focuses on a different issue entirely.9 / 25
Reviewer: 'Hey team, I'm reviewing this PR for the `order_status` contract. It looks good overall, but I'm seeing a concerning trend – we're consistently adding new fields without formally deprecating the old ones. This is creating significant complexity and increasing the risk of data discrepancies as different services continue to rely on outdated formats. Specifically, the `shipping_method` field hasn't been touched in years, despite multiple teams using it. What's the most appropriate action we should take before merging this change? This question tests understanding of proactive data governance. The correct answer—formally deprecating the field—addresses the core issue: a lack of structured removal of outdated contract elements. Options A and B represent reactive approaches that exacerbate the problem; option C is dismissive and irresponsible, while option B is too broad and doesn't directly address the immediate risk related to the specific field. Deprecation ensures proper documentation and migration planning.
10 / 25
Reviewer: 'Okay, the `payment_method` contract is updated to include support for SEPA direct debit. However, we're still using a legacy field, `credit_card_number`, which is flagged as deprecated in our governance documentation. This isn't triggering any alerts or blocking changes, but I'm concerned about the long-term maintainability and potential future issues if this contract remains inconsistent with current standards. What should be the immediate next step?The correct answer is 2 because ignoring deprecation flags ultimately leads to technical debt and increased risk. A formal deprecation process—updating systems and documenting changes—is crucial for maintaining data contract governance. Options A and D represent short-sighted solutions that exacerbate the problem, while option C is premature without a proper investigation and plan.
11 / 25
Reviewer: 'I'm seeing a potential issue with the `customer_address` contract field. The Slack channel discussion mentions that we're moving to a new address validation service, but this contract still uses the legacy format and lacks validation logic. It seems like we need to formally deprecate this field before any further integration work happens. This scenario highlights the importance of following a defined governance process. Simply changing systems doesn't resolve underlying issues; formally deprecating the field signals its obsolescence and triggers necessary updates across all dependent services. Ignoring the Slack discussion and proceeding without a formal process risks inconsistencies and future rework due to a lack of clear direction from the data governance team, specifically regarding lifecycle management.
12 / 25
PR Description:
"As part of the recent API v2.0 migration, we've updated the `product_name` contract to include a new field, `product_category`. This change aligns with the updated product taxonomy and ensures consistent categorization across all services. We've also removed the deprecated `product_code` field as per our data governance policies."The correct answer emphasizes the need for formal approval. While auditing is often important, the scenario explicitly mentions data governance policies regarding deprecation and addition of fields. Simply documenting changes isn't sufficient; a formal approval process ensures alignment with established rules and mitigates potential risks associated with evolving contracts. Option A is incorrect because it suggests reverting a deployed version without proper justification.
13 / 25
Reviewer: 'Okay, I'm reviewing this PR and noticed a potential conflict. The `user_id` contract field is still referencing the old database schema (v1), while the new microservice uses v2. We need to formally flag this for deprecation and update the contract accordingly, otherwise we risk data inconsistencies down the line. PR Description: 'We've updated the customer_name contract to include a new field, customer_email, to comply with GDPR regulations.'This situation highlights the importance of proactive data governance. Simply ignoring inconsistencies or assuming downstream systems will adapt is risky. The correct action is to formally deprecate the outdated field (
user_id) and initiate a contract update – this demonstrates accountability and minimizes the chance of future data discrepancies. Option A is incorrect because ignoring conflicts can lead to serious problems; option B is flawed due to assuming automatic adaptation, while option C focuses on a different issue entirely.14 / 25
Reviewer: 'Hey team, I'm reviewing this PR for the `order_status` contract. It looks good overall, but I'm seeing a concerning trend – we're consistently adding new fields without formally deprecating the old ones. This is creating significant complexity and increasing the risk of data discrepancies as different services continue to rely on outdated formats. Specifically, the `shipping_method` field hasn't been touched in years, despite multiple teams using it. What's the most appropriate action we should take before merging this change? This question tests understanding of proactive data governance. The correct answer—formally deprecating the field—addresses the core issue: a lack of structured removal of outdated contract elements. Options A and B represent reactive approaches that exacerbate the problem; option C is dismissive and irresponsible, while option B is too broad and doesn't directly address the immediate risk related to the specific field. Deprecation ensures proper documentation and migration planning.
15 / 25
Reviewer: 'Okay, the `payment_method` contract is updated to include support for SEPA direct debit. However, we're still using a legacy field, `credit_card_number`, which is flagged as deprecated in our governance documentation. This isn't triggering any alerts or blocking changes, but I'm concerned about the long-term maintainability and potential future issues if this contract remains inconsistent with current standards. What should be the immediate next step?The correct answer is 2 because ignoring deprecation flags ultimately leads to technical debt and increased risk. A formal deprecation process—updating systems and documenting changes—is crucial for maintaining data contract governance. Options A and D represent short-sighted solutions that exacerbate the problem, while option C is premature without a proper investigation and plan.
16 / 25
Reviewer: 'I'm seeing a potential issue with the `customer_address` contract field. The Slack channel discussion mentions that we're moving to a new address validation service, but this contract still uses the legacy format and lacks validation logic. It seems like we need to formally deprecate this field before any further integration work happens. This scenario highlights the importance of following a defined governance process. Simply changing systems doesn't resolve underlying issues; formally deprecating the field signals its obsolescence and triggers necessary updates across all dependent services. Ignoring the Slack discussion and proceeding without a formal process risks inconsistencies and future rework due to a lack of clear direction from the data governance team, specifically regarding lifecycle management.
17 / 25
PR Description:
"As part of the recent API v2.0 migration, we've updated the `product_name` contract to include a new field, `product_category`. This change aligns with the updated product taxonomy and ensures consistent categorization across all services. We've also removed the deprecated `product_code` field as per our data governance policies."The correct answer emphasizes the need for formal approval. While auditing is often important, the scenario explicitly mentions data governance policies regarding deprecation and addition of fields. Simply documenting changes isn't sufficient; a formal approval process ensures alignment with established rules and mitigates potential risks associated with evolving contracts. Option A is incorrect because it suggests reverting a deployed version without proper justification.
18 / 25
Reviewer: 'Okay, I'm reviewing this PR and noticed a potential conflict. The `user_id` contract field is still referencing the old database schema (v1), while the new microservice uses v2. We need to formally flag this for deprecation and update the contract accordingly, otherwise we risk data inconsistencies down the line. PR Description: 'We've updated the customer_name contract to include a new field, customer_email, to comply with GDPR regulations.'This situation highlights the importance of proactive data governance. Simply ignoring inconsistencies or assuming downstream systems will adapt is risky. The correct action is to formally deprecate the outdated field (
user_id) and initiate a contract update – this demonstrates accountability and minimizes the chance of future data discrepancies. Option A is incorrect because ignoring conflicts can lead to serious problems; option B is flawed due to assuming automatic adaptation, while option C focuses on a different issue entirely.19 / 25
Reviewer: 'Hey team, I'm reviewing this PR for the `order_status` contract. It looks good overall, but I'm seeing a concerning trend – we're consistently adding new fields without formally deprecating the old ones. This is creating significant complexity and increasing the risk of data discrepancies as different services continue to rely on outdated formats. Specifically, the `shipping_method` field hasn't been touched in years, despite multiple teams using it. What's the most appropriate action we should take before merging this change? This question tests understanding of proactive data governance. The correct answer—formally deprecating the field—addresses the core issue: a lack of structured removal of outdated contract elements. Options A and B represent reactive approaches that exacerbate the problem; option C is dismissive and irresponsible, while option B is too broad and doesn't directly address the immediate risk related to the specific field. Deprecation ensures proper documentation and migration planning.
20 / 25
Reviewer: 'Okay, the `payment_method` contract is updated to include support for SEPA direct debit. However, we're still using a legacy field, `credit_card_number`, which is flagged as deprecated in our governance documentation. This isn't triggering any alerts or blocking changes, but I'm concerned about the long-term maintainability and potential future issues if this contract remains inconsistent with current standards. What should be the immediate next step?The correct answer is 2 because ignoring deprecation flags ultimately leads to technical debt and increased risk. A formal deprecation process—updating systems and documenting changes—is crucial for maintaining data contract governance. Options A and D represent short-sighted solutions that exacerbate the problem, while option C is premature without a proper investigation and plan.
21 / 25
Reviewer: 'I'm seeing a potential issue with the `customer_address` contract field. The Slack channel discussion mentions that we're moving to a new address validation service, but this contract still uses the legacy format and lacks validation logic. It seems like we need to formally deprecate this field before any further integration work happens. This scenario highlights the importance of following a defined governance process. Simply changing systems doesn't resolve underlying issues; formally deprecating the field signals its obsolescence and triggers necessary updates across all dependent services. Ignoring the Slack discussion and proceeding without a formal process risks inconsistencies and future rework due to a lack of clear direction from the data governance team, specifically regarding lifecycle management.
22 / 25
PR Description:
"As part of the recent API v2.0 migration, we've updated the `product_name` contract to include a new field, `product_category`. This change aligns with the updated product taxonomy and ensures consistent categorization across all services. We've also removed the deprecated `product_code` field as per our data governance policies."The correct answer emphasizes the need for formal approval. While auditing is often important, the scenario explicitly mentions data governance policies regarding deprecation and addition of fields. Simply documenting changes isn't sufficient; a formal approval process ensures alignment with established rules and mitigates potential risks associated with evolving contracts. Option A is incorrect because it suggests reverting a deployed version without proper justification.
23 / 25
Reviewer: 'Okay, I'm reviewing this PR and noticed a potential conflict. The `user_id` contract field is still referencing the old database schema (v1), while the new microservice uses v2. We need to formally flag this for deprecation and update the contract accordingly, otherwise we risk data inconsistencies down the line. PR Description: 'We've updated the customer_name contract to include a new field, customer_email, to comply with GDPR regulations.'This situation highlights the importance of proactive data governance. Simply ignoring inconsistencies or assuming downstream systems will adapt is risky. The correct action is to formally deprecate the outdated field (
user_id) and initiate a contract update – this demonstrates accountability and minimizes the chance of future data discrepancies. Option A is incorrect because ignoring conflicts can lead to serious problems; option B is flawed due to assuming automatic adaptation, while option C focuses on a different issue entirely.24 / 25
Reviewer: 'Hey team, I'm reviewing this PR for the `order_status` contract. It looks good overall, but I'm seeing a concerning trend – we're consistently adding new fields without formally deprecating the old ones. This is creating significant complexity and increasing the risk of data discrepancies as different services continue to rely on outdated formats. Specifically, the `shipping_method` field hasn't been touched in years, despite multiple teams using it. What's the most appropriate action we should take before merging this change? This question tests understanding of proactive data governance. The correct answer—formally deprecating the field—addresses the core issue: a lack of structured removal of outdated contract elements. Options A and B represent reactive approaches that exacerbate the problem; option C is dismissive and irresponsible, while option B is too broad and doesn't directly address the immediate risk related to the specific field. Deprecation ensures proper documentation and migration planning.
25 / 25
Reviewer: 'Okay, the `payment_method` contract is updated to include support for SEPA direct debit. However, we're still using a legacy field, `credit_card_number`, which is flagged as deprecated in our governance documentation. This isn't triggering any alerts or blocking changes, but I'm concerned about the long-term maintainability and potential future issues if this contract remains inconsistent with current standards. What should be the immediate next step?The correct answer is 2 because ignoring deprecation flags ultimately leads to technical debt and increased risk. A formal deprecation process—updating systems and documenting changes—is crucial for maintaining data contract governance. Options A and D represent short-sighted solutions that exacerbate the problem, while option C is premature without a proper investigation and plan.
Frequently Asked Questions
What does the "Data Contract Governance Vocabulary" exercise practise?
Practice data contract governance vocabulary: contract registry, contract owner, deprecating fields, data steward role, and governance team sign-off language.
How many questions are in this exercise?
This exercise has 25 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 Contracts 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 Contract Governance Vocabulary" part of a larger series?
Yes — it's one exercise in the Data Contracts 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 Contracts category page for related exercises, or browse the main Exercises hub for other IT English topics.