An oriole-copse /orders API must keep v1 live while v2 ships a breaking request body. Which APIM construct should the developer use for that breaking change?
Select an answer to reveal the explanation.
Short Explanation
Breaking body change? Use an APIM version so oriole-copse v1 keeps running while v2 ships. Revisions are for safer in-place updates.
Full Explanation
API Management versions let multiple contract generations coexist (for example /orders?api-version=1 versus version 2). Revisions support non-breaking or staged in-place changes to an existing API. Git branches alone do not create a gateway version path for callers, and per-consumer storage accounts are unrelated to API versioning.