A custom extension call returns HTTP 401 Unauthorized. 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 — authentication credentials are missing; incorrect; or expired is your go-to move. A 401 status specifically indicates an authentication failure: the credentials are absent; wrong; or the token has expired. 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
A 401 status specifically indicates an authentication failure: the credentials are absent; wrong; or the token has expired. A server being offline typically returns a connection error or 503. An OpenAPI syntax error would be caught at import time; not at runtime. Connectivity issues produce network-level errors; not HTTP 401 status codes. The correct answer, "Authentication credentials are missing; incorrect; or expired", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("The API server is offline", "The OpenAPI spec has a syntax error", "The assistant instance has no internet connectivity") 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.