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 . Implement required changes to the Process API implementation so that whenever possible, the Process API’s RAML definition remains unchanged
B . Update the RAML definition of the current Process API and notify API client developers by sending them links to the updated RAML definition
C . Postpone changes until API consumers acknowledge they are ready to migrate to a new Process API or API version
D . Implement the Process API changes in a new API implementation, and have the old API implementation return an HTTP status code 301 – Moved Permanently to inform API clients they should be calling the new API implementation

Answer: A

Explanation:

* Option B shouldn’t be used unless extremely needed, if RAML is changed, client needs to accommodate changes. Question is about minimizing impact on Client. So this is not a valid choice.

* Option C isn’t valid as Business can’t stop for consumers acknowledgment.

* Option D again needs Client to accommodate changes and isn’t viable option.

* Best choice is A where RAML definition isn’t changed and underlined functionality is changed without any dependency on client and without impacting client.