What are common patterns for API versioning in MuleSoft?

• A. Versioning APIs by path (e.g., /v1/resource) or by headers; maintain backward compatibility and route to the appropriate versioned API.
• B. APIs should never be versioned; always update all clients.
• C. Versioning is done by changing the Java class package.
• D. Versioning is achieved by altering the database schema.

Answer: (A)

Versioning APIs by including the version in the URL or via a version header is the standard way to evolve an API while keeping existing clients working. In MuleSoft, you can publish multiple versions of an API and route each incoming request to the correct version based on the path (for example, /v1/resource or /v2/resource) or a version indicator in a header. This approach makes the intended API contract explicit to consumers, supports simultaneous live versions, and allows you to deprecate older versions on a planned timeline without forcing all clients to change at once.

Using a Java package reference or changing the database schema doesn’t provide a client-facing API versioning mechanism. Those approaches affect implementation details or data storage rather than the API contract exposed to consumers, so they don’t support clean, backward-compatible versioning of the API surface.