How should the developer of an API client respond to this change?

An API has been updated in Anypoint Exchange by its API producer from version 3.1.1 to 3.2.0 following accepted semantic versioning practices and the changes have been communicated via the API’s public portal. The API endpoint does NOT change in the new version.

How should the developer of an API client respond to this change?
A . The update should be identified as a project risk and full regression testing of the functionality that uses this API should be run.
B . The API producer should be contacted to understand the change to existing functionality.
C . The API producer should be requested to run the old version in parallel with the new one.
D . The API client code ONLY needs to be changed if it needs to take advantage of new features.

Answer: D

Explanation:

* Semantic Versioning is a 3-component number in the format of X.Y.Z, where: X stands for a major version.

Y stands for a minor version: Z stands for a patch.

So, SemVer is of the form Major.Minor.Patch Coming to our question, minor version of the API has been changed which is backward compatible. Hence there is no change required on API client end. If they want to make use of new featured that have been added as a part of minor version change they may need to change code at their end. Hence correct answer is The API client code ONLY needs to be changed if it needs to take advantage of new features.