Practice vocabulary for negotiating data contracts between teams: SLA breach clauses, schema evolution policy, backward compatibility, and contract amendment language.
0 / 5 completed
1 / 5
A producer team says: 'We commit to ___ the agreed schema for at least 90 days before deprecating any field.' Which word fits?
'Maintaining' the agreed schema is standard contract language — the producer promises to keep the schema stable for a defined period before making breaking changes.
2 / 5
What does 'backward compatible change' mean in a data contract context?
Adding a new optional field is backward compatible because existing consumers can ignore it without breaking. Removing or renaming fields, or changing types, are breaking changes.
3 / 5
Fill in the blank: 'An SLA ___ triggers an automatic incident ticket and a credit to the consuming team.'
An SLA breach (failure to meet the agreed service level) is the trigger for remediation actions. SLA breach language is a core element of data contract negotiation.
4 / 5
A contract clause reads: 'The ___ team agrees to notify consumers 30 days before any breaking schema change.' Which role fits?
The producing team owns the data and therefore agrees to notify downstream consumers before making breaking changes. This is standard producer responsibility in data contract language.
5 / 5
What is a 'schema evolution policy' in a data contract?
A schema evolution policy defines what kinds of changes are allowed (e.g., only additive changes), how much notice must be given, and what approval process is required before modifying a contract schema.