A developer needs to distinguish between 'cancel my subscription' and 'cancel my order.' What is the best approach?
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 — create two intents (#cancel_subscription; #cancel_order) with distinct training examples is your go-to move. Two separate intents with distinct training examples allow the NLU to reliably differentiate between the two cancellation scenarios based on the full user utterance. 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
Two separate intents with distinct training examples allow the NLU to reliably differentiate between the two cancellation scenarios based on the full user utterance. A single intent cannot distinguish the object of cancellation on its own. Context variables set before the fact do not help classify the incoming message. Pattern entities detect specific words but do not represent the user goal. The correct answer, "Create two intents (#cancel_subscription; #cancel_order) with distinct training examples", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Use a single @cancel entity and rely on intent alone", "Use a context variable set before the cancel intent fires", "Create two pattern entities matching 'subscription' and 'order'") 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.