The implementation of a Process API must change.
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?
The best approach to minimize the impact of changes on API clients is to implement the required changes to the Process API implementation in such a way that the RAML definition remains unchanged whenever possible. This ensures that clients relying on the existing API definition do not experience disruptions or need to make modifications to their integrations.
C. Implement required changes to the Process API implementation so that, whenever possible, the Process API's RAML definition remains unchanged.
C. Implement required changes to the Process API implementation so that, whenever possible, the Process API's RAML definition remains unchanged.
Answer: C
It should be C. API Implementation is changing, no changes are needed to RAML. Question does not clarify if change is backward compatible. My assumption is the change is backward compatible, in which case we can go ahead and do the change and RAML remains unchanged.