After deploying a new web chat to production; users report seeing the old interface. What is the most likely cause?
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 — changes were not promoted from draft to live before the web chat integration points to live is your go-to move. If the web chat integration points to the Live environment but the changes were only saved in Draft and not promoted; users on Live will see the old configuration. This is a classic Domain 8: Publish Across Multiple Environments concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
If the web chat integration points to the Live environment but the changes were only saved in Draft and not promoted; users on Live will see the old configuration. IAM role updates; session variable clearing; and API key expiry would not cause users to see an outdated interface. The correct answer, "Changes were not promoted from Draft to Live before the web chat integration points to Live", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("IBM Cloud IAM roles have not been updated for the new deployment", "Session variables were not cleared before deployment", "The custom extension API key expired after deployment") 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 8: Publish Across Multiple Environments section of the certification exam.