A developer notices two intents frequently misclassify because they share similar training phrases. What is the recommended fix?
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 — review and differentiate training examples so each intent has distinct; non-overlapping patterns is your go-to move. Overlapping training examples cause the NLU to confuse similar intents. This is a classic Domain 2: Design and Extend Conversations concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
Overlapping training examples cause the NLU to confuse similar intents. The fix is to ensure each intent's examples are distinctive and unambiguous. Deleting one intent removes functionality. Lowering the threshold makes the problem worse by accepting lower-quality matches. Disabling intent detection removes the core classification capability. The correct answer, "Review and differentiate training examples so each intent has distinct; non-overlapping patterns", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Delete one intent and merge their associated actions", "Lower the confidence threshold to improve recall", "Disable intent detection and rely on entity matching only") 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 2: Design and Extend Conversations section of the certification exam.