What must be configured when setting up OAuth 2.0 authentication for a custom extension connecting to a corporate system?
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 — the client id; client secret; authorization url; and token url is your go-to move. OAuth 2. 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
OAuth 2.0 requires the client ID; client secret; and the authorization and token endpoint URLs so the assistant can obtain and refresh access tokens. Database credentials and server IPs are not OAuth components. SSH keys are for server access. SAML assertions use a different federated identity protocol. The correct answer, "The client ID; client secret; authorization URL; and token URL", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("The system database credentials and server IP", "An SSH key and port number for the server", "A SAML assertion file from the identity provider") 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.