You are developing several Azure API Management (APIM) hosted APIs.
You must make several minor and non-breaking changes to one of the APIs. The API changes include the following requirements:
• Must not disrupt callers of the API.
• Enable roll back if you find issues.
• Documented to enable developers to understand what is new.
• Tested before publishing.
You need to update the API.
What should you do?
To address the need for making minor and non-breaking changes without disrupting callers, the best approach is to add a new revision to the API. Adding a new revision allows you to safely model and test changes, document them for developers, and enable a rollback if issues are found. This ensures that the updates are managed in a controlled manner and are tested before being published.
D is correct: In Azure API Management, use revisions to make non-breaking API changes so you can model and test changes safely. When ready, you can make a revision current and replace your current API. https://learn.microsoft.com/en-us/azure/api-management/api-management-get-started-revise-api?tabs=azure-portal
Question 'need to update the API'? --> Correct answer 'Add a new revision to the API'
D is the correct answer: https://learn.microsoft.com/en-us/azure/api-management/api-management-revisions
The best approach for making non-breaking changes to an APIM-hosted API is to create a new revision of the API.
Voting D
Should be revision and not versioning. Anew version will disrupt current use
The answer is D. Revisions can be used for minor and non-breaking changes to an API.
version might introduce breaking changes!
D is more relevant.