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 Permanently to inform API clients they should be calling the new API implementation

Answer: C

Explanation:

Correct Answer. Implement required changes to the Process API implementation so that, whenever possible, the Process API’s RAML definition remains unchanged.

*****************************************

Key requirement in the question is:

>> Approach that minimizes the impact of this change on API clients Based on above:

>> Updating the RAML definition would possibly impact the API clients if the changes require any thing mandatory from client side. So, one should try to avoid doing that until really necessary.

>> Implementing the changes as a completely different API and then redirectly the clients with 3xx status code is really upsetting design and heavily impacts the API clients.

>> Organisations and IT cannot simply postpone the changes required until all API consumers acknowledge they are ready to migrate to a new Process API or API version. This is unrealistic and not possible.

The best way to handle the changes always is to implement required changes to the API implementations so that, whenever possible, the API’s RAML definition remains unchanged.