A developer wants to capture the user saying 'urgent'; 'ASAP'; or 'right away' as indicating high priority. How should this be configured?
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 a dictionary entity with those phrases mapped to a high-priority canonical value is your go-to move. A dictionary entity with 'urgent'; 'ASAP'; and 'right away' as values or synonyms of a 'high-priority' value detects all three phrasings and returns a consistent canonical value for branching. 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
A dictionary entity with 'urgent'; 'ASAP'; and 'right away' as values or synonyms of a 'high-priority' value detects all three phrasings and returns a consistent canonical value for branching. Three separate intents for synonymous concepts overcomplicates the design. Pattern entities are for structured formats. Custom extensions are not needed for simple keyword detection. The correct answer, "Create a dictionary entity with those phrases mapped to a high-priority canonical value", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Create three separate intents for each phrase", "Use a pattern entity with regex matching those exact strings", "Configure a custom extension to detect urgency keywords") 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.