HTTP JSON APIs · interview question
Why should an API version change when a field is renamed or removed?
Multiple choiceHardchapter-11-curatedpremiumhttp-json-apisapi-versioning
Answer and explanation
Correct answer
B. Because that is a breaking contract change for existing clients
Why
Adding fields is often backward compatible, but renaming or removing fields can break client deserialization immediately. Versioning gives clients time to migrate without silent runtime failures.
Test yourself on HTTP JSON APIs
A free test with instant, explained results. No account needed.
More HTTP JSON APIs questions
- Why might an API client crash if JSON response shapes are not treated as strict contracts?
- Why might you choose to use an API gateway in conjunction with API versioning?
- In the context of Java's HttpClient, which method allows you to perform an asynchronous HTTP request?
- How can you ensure that a Java application using HttpClient does not suffer from resource exhaustion during network…
- Which of the following is a challenge when using URL path versioning for APIs?
- What should the DTO-to-domain translation step usually do?