A transit-fare consumer depends on specific fields from a fare-rules producer. How can consumer-driven contracts catch producer drift before production?
Select an answer to reveal the explanation.
Short Explanation
Let the rider’s actual needs write the checklist the ticket booth must pass. Consumer-driven contracts replay what the consumer depends on inside the producer’s build—stronger than a dusty OpenAPI nobody runs.
Full Explanation
In a consumer-driven contract approach, the consumer records the requests and responses it depends on, and the producer verifies those expectations in its pipeline. That executable check catches producer drift earlier than a producer-only OpenAPI artifact that is never run. It remains a test of the contract, not a service-mesh or authorizer redesign.