An API returns a nested JSON field 'customer.email.' How should this be referenced in the custom extension output mapping?
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 — using dot notation or jsonpath syntax such as $.customer.email is your go-to move. Nested JSON fields are accessed using dot notation or JSONPath expressions in the extension output mapping. 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
Nested JSON fields are accessed using dot notation or JSONPath expressions in the extension output mapping. Underscore notation is not valid for nested field access. Making a separate flattening call adds unnecessary complexity. Fuzzy matching applies to entity detection; not API response parsing. The correct answer, "Using dot notation or JSONPath syntax such as $.customer.email", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("${customer_email} using underscore notation", "In a separate API call that flattens the response", "By enabling fuzzy matching in the extension settings") 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.