Managing API breaking changes requires clear, professional communication. This quiz covers the collocations for deprecating, versioning, communicating, and sunsetting API endpoints.
0 / 5 completed
1 / 5
We will ___ the /v1/users endpoint in favour of the new /v2/users route.
Deprecate endpoints is the standard API collocation — deprecation signals to consumers that an endpoint will be removed in a future version.
2 / 5
The team must ___ timelines clearly in the developer changelog and email blast.
Communicate timelines is the correct collocation — API teams communicate timelines for deprecation and removal to give consumers time to migrate.
3 / 5
We decided to ___ the API using URL path prefixes (/v1/, /v2/).
Version the API is the standard collocation — teams version the API to allow multiple versions to coexist during transition periods.
4 / 5
Our developer relations team will help ___ consumers from v1 to v2 over six months.
Migrate consumers is the correct collocation — the goal is to migrate consumers before the old version is removed.
5 / 5
Legacy v1 endpoints will be fully ___ 12 months after the v2 general availability date.
Sunset versions is the standard lifecycle collocation — APIs are sunsetted on an announced date after a deprecation period.