An action has 8 steps. Steps 3 and 4 should only run for returning customers. Which feature supports 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 — conditional steps checking a session variable that indicates returning customer status is your go-to move. Conditional steps evaluate a boolean or value condition at runtime. This is a classic Domain 1: Build Conversations concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
Conditional steps evaluate a boolean or value condition at runtime. Setting a session variable indicating returning customer status during authentication or lookup; then conditioning steps 3 and 4 on that variable; is the correct approach. Confidence thresholds affect intent detection. Entities detect text values in messages. A per-step extension call adds unnecessary overhead. The correct answer, "Conditional steps checking a session variable that indicates returning customer status", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Intent confidence thresholds", "A dictionary entity with customer IDs", "A custom extension that queries customer status per step") 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 1: Build Conversations section of the certification exam.