A custom extension returns HTTP 200 but the response body contains an error message field. How does watsonx Assistant handle this?
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 developer must add a step that reads the response body and checks for error fields; then branches accordingly is your go-to move. A 200 status with an application-level error in the body requires explicit developer handling: reading the error field; evaluating it; and routing to an appropriate response step. 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
A 200 status with an application-level error in the body requires explicit developer handling: reading the error field; evaluating it; and routing to an appropriate response step. watsonx Assistant does not automatically parse application error fields; terminate sessions; or retry on application errors. The correct answer, "The developer must add a step that reads the response body and checks for error fields; then branches accordingly", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Automatically parse the error field and show it to the user", "The session is automatically terminated on any error message", "The extension retries up to three times automatically") 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.