A developer wants to reuse address-collection steps across five different actions. What is the recommended 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 a subaction that collects the address and call it from each of the five actions is your go-to move. Subactions enable reuse of common conversation patterns. This is a classic Domain 1: Build Conversations concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
Subactions enable reuse of common conversation patterns. Creating one address-collection subaction and calling it from each parent action eliminates duplication and makes maintenance easier. Manual copy-paste creates maintenance burden. A global session variable does not collect addresses. A database extension adds unnecessary complexity for address entry. The correct answer, "Create a subaction that collects the address and call it from each of the five actions", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Copy and paste the steps into each action manually", "Use a global session variable to auto-populate address fields", "Configure a custom extension that returns address data from a database") 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.