A custom extension's OpenAPI spec defines a required query parameter 'city.' If the action calls the extension without supplying 'city'; what most likely happens?
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 — the api call fails with a 400 bad request error that the developer should handle with an error step is your go-to move. Most REST APIs return a 400 Bad Request error when a required parameter is absent. 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
Most REST APIs return a 400 Bad Request error when a required parameter is absent. The developer should handle this by checking the extension call status and providing a meaningful error response. watsonx Assistant does not auto-detect location; skip calls silently; or apply hardcoded defaults. The correct answer, "The API call fails with a 400 Bad Request error that the developer should handle with an error step", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("The extension auto-fills city from the user's IP location", "watsonx Assistant silently skips the extension call", "The extension returns weather for New York by default") 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.