Where are API key credentials configured when adding an authenticated custom extension to a watsonx Assistant environment?
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 — in the custom extension authentication settings when the extension is added to the environment is your go-to move. API key credentials are entered in the extension's authentication settings within the environment configuration; where they are applied securely to all requests. This is a classic Domain 6: Build Back-End Integrations concept you'll want locked in before exam day.'
Full explanation below image
Full Explanation
API key credentials are entered in the extension's authentication settings within the environment configuration; where they are applied securely to all requests. Hardcoding credentials in response text is a security risk. Including credentials in the OpenAPI file is an anti-pattern. The web chat script does not manage API credentials. The correct answer, "In the custom extension authentication settings when the extension is added to the environment", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Hardcoded in the action step response text", "Inside the OpenAPI specification file as a default header", "In the web chat widget configuration script") 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 6: Build Back-End Integrations section of the certification exam.