Guide-linked quiz · Medium Level

Data Contracts for ML Pipelines Quiz

Understand what a data contract specifies, how executable tests enforce it, and why declarations alone do not guarantee data correctness.

Question 1 of 8

Which items can an ODCS data contract describe?

Preview every question8 questions

Answers and explanations appear as you take the quiz.

  1. Which items can an ODCS data contract describe?
    • A guarantee that every model is fair
    • The accuracy of every prediction
    • Schema, semantics, quality expectations, and service levels such as freshness
    • A replacement for monitoring
  2. How can a pipeline detect a changed upstream field against a contract?
    • A producer or consumer system validates actual data against the declared rule
    • The contract file exists somewhere
    • The ML model is retrained automatically
    • The producer team sends no notice
  3. Does “contract” in a data-contract specification necessarily mean a legal contract?
    • Yes, always
    • Only if it has a YAML file
    • Yes, and every consumer automatically signs it
    • No; the term commonly describes a technical agreement and is not necessarily legal
  4. Which standard does the Data Contract Specification project recommend for new adoption after its deprecation notice?
    • OpenLineage Run Cycle
    • Open Data Contract Standard (ODCS)
    • Parquet schema registry
    • Delta Change Data Feed
  5. What can a passing data-contract check establish?
    • The data are unbiased and semantically perfect
    • Every future batch will pass
    • The tested batch met the specific checks that were implemented
    • The model is safe for deployment
  6. Who should resolve a meaning such as “eligible customer” in a contract?
    • The schema validator alone
    • Producer and consumer domain owners who share the data meaning
    • A hash function
    • The storage system
  7. Which service objective can be represented in a data contract?
    • A maximum age for the newest record using a timestamp field
    • Guaranteed model accuracy on future users
    • Guaranteed fairness without evaluation
    • A promise that values are always true
  8. What should a team define for contract violations?
    • Nothing after validation fails
    • Automatic replacement with guessed values
    • A rule that hides all failures
    • An owner and explicit alerting, quarantine, or remediation behavior

Keep testing yourself

More quizzes picked for your level.

View all quizzes