1 / 5
Scenario: "The pipeline broke because the producer changed the schema without notifying consumers." What is a data contract designed to prevent?
A A data contract is a formal agreement between producer and consumer specifying the schema, data types, freshness SLA, quality expectations, and versioning policy — preventing unilateral breaking changes B A data contract prevents all schema changes C A data contract is an internal SLA document between two engineering teams D A data contract is a legal document signed by both parties
Data contract defines: schema, semantics, quality expectations, SLA, and breaking change policy. Born from data engineering reliability needs — tables breaking downstream pipelines silently.Systems: Soda, Great Expectations.Key vocab: data producer , data consumer , schema definition , freshness SLA , breaking change notification .
Next →
2 / 5
Scenario: "The contract specifies the schema is owned by the producing team." What does schema ownership mean in a data contract context?
A The producing team can change the schema at any time without restriction B The consuming team must request schema changes from the producing team C Ownership is shared equally between both teams D The producing team is responsible for maintaining schema validity, announcing changes, and ensuring stability per the deprecation policy
Schema ownership: the producer controls the structure but has obligations — advance notice, versioning, migration support. Producer-driven vs. consumer-driven contracts are different models.Key vocab: schema ownership , producer obligations , advance notice , schema registry .
Next →
3 / 5
Scenario: "The analyst reports a sudden drop in row count." How does a data contract help in this situation?
A Provides the analyst access to the producer team's CI/CD logs B Defines expected row count ranges, anomaly thresholds, and escalation process — giving both teams a shared reference for diagnosing whether the drop is a violation or expected behaviour C Data contracts only cover schema structure, not row count expectations D The data contract automatically restores the missing rows
Data contracts include: volume (row count ranges), freshness, completeness (null rate), validity. A shared definition of "normal" vs. "anomaly" removes ambiguity during incidents.Key vocab: quality expectation , volume anomaly , contract violation , escalation path in contract .
Next →
4 / 5
Scenario: "The data product team versioned the contract as v2.0.0." What does a MAJOR version bump mean for a data contract?
A A minor improvement to documentation in the contract B A new optional field added to the schema C A breaking change — renaming a column, removing a field, changing a data type, or altering the primary key — requiring consumers to modify their consuming code D A scheduled maintenance period for the producing pipeline
SemVer for data contracts: MAJOR (breaking: column rename/removal, type change), MINOR (backward-compatible addition), PATCH (doc fix).Protocol: advance notice (30 days), migration guide, dual-version support period.Key vocab: breaking data contract change , SemVer for data , migration notice , deprecation period .
Next →
5 / 5
Scenario: "The team is implementing contract-first data development ." What does contract-first mean?
A Legal contracts must be signed before any data sharing begins B The data contract (schema, quality expectations, SLA) is designed and agreed upon before the pipeline is built — ensuring producer and consumer alignment before implementation C Contracts must be reviewed quarterly before new pipelines are approved D The first pipeline built should be the data validation pipeline
Contract-first: analogous to API-first. Benefits: catches design disagreements early, documents assumptions, enables parallel development.Key vocab: contract-first development , design before implementation , schema registry pre-registration .
See results