Mobile and backend teams agree on an OpenAPI contract for a city services app, and CI must fail if staging drifts. What should they automate?
Select an answer to reveal the explanation.
Short Explanation
A contract you never check is a handshake in the dark. Point CI at staging with OpenAPI contract tests so drift fails the build before citizens' phones do. Hoping mobile devs notice missing fields is not a gate.
Full Explanation
Contract testing validates that a deployed API still matches the agreed schema before promotion. For DVA-C02 Task 2, running those checks in development/test environments catches breaking changes early between municipal mobile and backend teams. Documentation-only OpenAPI, reactive mobile hotfixes, or never evolving the backend are not substitutes for automated contract validation.