A developer wants to call an external API from an action but the API has no published OpenAPI spec. What should be done?
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 — write an openapi specification for the relevant endpoints and import it as a custom extension is your go-to move. The developer should author an OpenAPI specification that accurately describes the endpoints they need to call and import it as a custom extension. 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
The developer should author an OpenAPI specification that accurately describes the endpoints they need to call and import it as a custom extension. Dialog node webhooks are a legacy pattern. Hardcoding responses eliminates the benefit of a live integration. The search skill is for document knowledge base retrieval; not arbitrary REST API calls. The correct answer, "Write an OpenAPI specification for the relevant endpoints and import it as a custom extension", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Use a dialog node webhook instead of a custom extension", "Hardcode the API responses in action steps", "Use the search skill to retrieve data from the API") 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.