What is a valid approach that minimizes the impact of this change on API clients?

The implementation of a Process API must change.

What is a valid approach that minimizes the impact of this change on API clients?
A . Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition.
B . Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version.
C . Implement required changes to the Process API implementation so that, whenever possible, the Process API’s RAML definition remains unchanged.
D . Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 – Moved Permanentlyto inform API clients they should be calling the new API implementation.

Answer: A

Subscribe
Notify of
guest
1 Comment
Inline Feedbacks
View all comments
Narayana
Narayana
4 years ago

The question says “minimizes the impact of this change on API clients” — hence if the impact remains to be minimal — the changes must be as much as possible change to the RAML — while the API can still change. By this only we can keep the changes minimal