गाइड से जुड़ी प्रश्नोत्तरी · मध्यम स्तर
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.
प्रश्न 1 का 8
Which items can an ODCS data contract describe?
प्रत्येक प्रश्न का पूर्वावलोकन करें8 प्रश्न
जैसे ही आप प्रश्नोत्तरी लेते हैं उत्तर और स्पष्टीकरण दिखाई देते हैं।
- 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
- 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
- Does “contract” in a data-contract specification necessarily mean a legal contract?
- हाँ, हमेशा
- 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
- 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
- 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
- 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
- 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
- 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