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.
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.
C. Implement required changes to the Process API implementation so that, whenever possible, the Process API's RAML definition remains unchanged.
upvoted 2 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
calazans
2 years, 5 months agoOutdoor25
2 years, 11 months agoAB317
3 years, 3 months agoPavan_Nagineni
3 years, 4 months ago