What is the purpose of versioning an OpenAPI spec imported into a custom extension?
Select an answer to reveal the explanation.
Short Explanation and Infographic
Todd Lammle: 'Imagine you're building a chatbot and this exact situation comes up — to track api changes and update the extension when the external api specification changes is your go-to move. Versioning the OpenAPI spec allows the developer to track which API version the extension was built against and manage updates when the external API changes its interface. This is a classic Domain 6: Build Back-End Integrations concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
Versioning the OpenAPI spec allows the developer to track which API version the extension was built against and manage updates when the external API changes its interface. Session call limits; HTTP protocol version; and rate limiting are separate concerns. The correct answer, "To track API changes and update the extension when the external API specification changes", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("To limit how many times the extension can be called per session", "To set the HTTP protocol version for the connection", "To configure API rate limiting") may appear relevant but each misses a key requirement or introduces a step that is either unnecessary or belongs to a different workflow. Mastering the distinction between these approaches is essential for effective watsonx Assistant implementations and is a core focus of the Domain 6: Build Back-End Integrations section of the certification exam.