What does a versioned contract refer to in schema evolution?

What does a versioned contract refer to in schema evolution?

• A. Contracts identify color of UI
• B. Contracts define expectations between producer and consumer of data, versioned to track changes.
• C. Contracts are for licensing.
• D. Contracts expedite data deletion.

Answer: (B)

In schema evolution, a versioned contract is the formal agreement between data producers and data consumers that defines the expected shape, types, and constraints of the data. By versioning the contract, every change to the schema is tracked, so downstream users and systems know which version they are working with and can adapt or migrate as needed. This keeps data quality and compatibility intact as the data model evolves. The other choices miss this core idea: contracts aren’t about UI color, licensing, or speeding up data deletion.

In schema evolution, a versioned contract is the formal agreement between data producers and data consumers that defines the expected shape, types, and constraints of the data. By versioning the contract, every change to the schema is tracked, so downstream users and systems know which version they are working with and can adapt or migrate as needed. This keeps data quality and compatibility intact as the data model evolves. The other choices miss this core idea: contracts aren’t about UI color, licensing, or speeding up data deletion.