Practice vocabulary for testing data contracts: contract violation alerts, Great Expectations, data quality assertions, and dataset contract check language.
0 / 5 completed
1 / 5
What does it mean when a system reports 'the dataset failed the contract check'?
'The dataset failed the contract check' means the data violated at least one rule defined in the data contract — such as a null constraint, type mismatch, or value range violation.
2 / 5
In Great Expectations, a '___ suite' is a named collection of expectations attached to a dataset.
Great Expectations uses the term 'expectation suite' — a named, versioned collection of expectations (rules) that can be run against a dataset to validate it against a data contract.
3 / 5
What is a 'contract violation alert'?
A contract violation alert is an automated notification — sent to the data owner or consuming team — when a dataset fails validation against its data contract, enabling fast incident response.
4 / 5
A 'data quality ___ ' is a specific, testable rule such as 'column order_id must not be null'.
A data quality assertion is a specific, boolean-testable rule. Assertions are the building blocks of data contract tests — they either pass or fail against actual data.
5 / 5
Which phrase best describes 'contract-driven testing' in a data pipeline?
Contract-driven testing means validating that data actually meets the contract's rules at pipeline checkpoints — not just that the code runs, but that the data output matches agreed expectations.