A developer wants certain actions accessible only to authenticated premium users. What is the recommended implementation?
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 — use conditions in actions that check a session variable set by a pre-chat authentication or verification step is your go-to move. The recommended pattern is to set a session variable (such as 'user_tier = premium') during a pre-chat authentication step and add conditions on restricted actions that check this variable. This is a classic Domain 5: Administration concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
The recommended pattern is to set a session variable (such as 'user_tier = premium') during a pre-chat authentication step and add conditions on restricted actions that check this variable. Direct IAM-per-action control is not a feature. Environment variables are deployment configuration; not per-user access control. The correct answer, "Use conditions in actions that check a session variable set by a pre-chat authentication or verification step", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Configure IAM roles per action in IBM Cloud", "Set environment variables to restrict action visibility", "Disable the action in Live for all users and enable it via the API") 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 5: Administration section of the certification exam.