A developer needs to call an order-management REST API from within a watsonx Assistant action. The API requires a static API key passed as a custom HTTP header 'X-API-Key'. After importing the OpenAPI spec as a custom extension, where should the developer configure this header value?
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 — add the header value in the extension's authentication settings when the extension is added to an environment is your go-to move. When a custom extension is added to a watsonx Assistant environment, the platform presents an authentication configuration screen. 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
When a custom extension is added to a watsonx Assistant environment, the platform presents an authentication configuration screen. For API-key schemes the developer supplies the key value there; watsonx Assistant then injects it as the appropriate header on every extension call. Hardcoding secrets in the OpenAPI spec embeds them in source control, and session-variable mapping is not the correct mechanism for authentication headers. The correct answer, "Add the header value in the extension's authentication settings when the extension is added to an environment", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("Hardcode the header value directly in the OpenAPI spec's 'securitySchemes' section before importing", "Create a session variable named 'X-API-Key' and map it to the extension call's input parameters", "Configure a pre-message webhook that injects the header into every outbound HTTP request") 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.