When a custom extension call times out; what best practice should the developer implement?
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 — add an error handling step detecting the timeout and providing the user with a meaningful fallback message is your go-to move. A timeout error handler provides a graceful user experience when the external API is slow. 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 timeout error handler provides a graceful user experience when the external API is slow. Removing the extension eliminates the integration. Increasing session timeout addresses idle disconnection; not individual API call latency. The search skill is for knowledge retrieval; not as a REST API failover. The correct answer, "Add an error handling step detecting the timeout and providing the user with a meaningful fallback message", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Remove the extension call from the action", "Increase the watsonx Assistant session timeout to match API latency", "Use the search skill as a backup") 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.