A developer needs to store an account number collected in one step and use it three steps later in the same conversation. What should be used?
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 — a session variable assigned during the step is your go-to move. Session variables are the correct mechanism for persisting data within a conversation so it can be referenced in later steps of the same session. This is a classic Domain 1: Build Conversations concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
Session variables are the correct mechanism for persisting data within a conversation so it can be referenced in later steps of the same session. Global system variables are read-only platform values. A database call adds unnecessary overhead for within-session reuse. Intent confidence scores are metrics; not data storage. The correct answer, "A session variable assigned during the step", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("A global system variable", "A customer profile pulled from a connected database", "An intent confidence score") 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.