Which action is required on the publishing checklist when releasing a custom extension to Live?
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 — verifying the custom extension is configured with production api credentials in the live environment is your go-to move. Production API credentials must be configured separately in the Live environment extension settings since Draft and Live have independent configurations. 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
Production API credentials must be configured separately in the Live environment extension settings since Draft and Live have independent configurations. Deleting Draft; disabling analytics; and exporting logs are not part of a standard publishing checklist. The correct answer, "Verifying the custom extension is configured with production API credentials in the Live environment", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Deleting the Draft environment to prevent version confusion", "Disabling all analytics to prevent overwriting Draft data", "Exporting all conversation logs as CSV before going Live") 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.