API Testing / Quiz
Versioning Without Breaking the World
URI vs header versioning, additive evolution, deprecation windows, and proving v1 still behaves after v2 ships.
- Difficulty
- Easy
- Format
- Quiz
- Points
- 100
- Estimate
- 8 min
// MISSION BRIEF
Your Mission
A public API is a promise you cannot quietly change. This quiz covers versioning strategies, what counts as a safe additive change, how to deprecate with dignity, and the regression that a v1-to-v2 migration must never introduce.
// FIRST CONTACT
Battle teaser
A public API must ship a breaking change. The right approach:
- AChange v1 in place and email consumers to update
- BBreak it now, consumers should have been resilient
- CIntroduce a new version (e.g. /v2 or a version header) and keep /v1 alive through a deprecation window
- DSilently feature-flag the new behavior per user
Answers, scoring, hints, and the full battle stay sealed.
// SKILL TAGS
apiversioningdeprecationbackward-compatibility