Scenario: An Amazon Lex virtual assistant sometimes fails to recognize variations of its category themes (e.g., mapping "thrill-seeking" to…

The most effective and immediate solution is to use synonyms within the custom slot type. By defining "thrill-seeking" as a synonym for the existing enumeration value "adventure," you instruct Amazon Lex to map this user input directly to the canonical value. When a user mentions "thrill-seeking," Lex will resolve the slot's value to "adventure" before passing it to the backend. This approach correctly interprets the user's intent without requiring any modifications to the backend Lambda function or database, thus adhering to all constraints of the scenario.

A. Training a new intent is incorrect because the user's goal (the intent) remains the same; only the terminology for a specific piece of information (the slot value) has changed.

B. Runtime hints are provided programmatically during a session, which would require modifying the backend Lambda function to implement, violating a key constraint of the problem.

D. Adding the unrecognized word as a new enumeration value would make it a distinct category. The backend would then receive "thrill-seeking" as a new value and would need to be updated to handle it, which is explicitly forbidden.

1. AWS Documentation - Amazon Lex V2 Developer Guide: In the section on "Custom slot types," the guide explains the use of synonyms. It states, "You can provide synonyms for slot values... When the user enters a synonym, the slot is resolved to the slot value." This directly supports using synonyms to map variations like "thrill-seeking" to a canonical value like "adventure".

Source: AWS Documentation, Amazon Lex V2 Developer Guide, "Custom slot types," section on "Synonyms."

2. AWS Documentation - Amazon Lex V2 Developer Guide: The guide clarifies the purpose of enumeration values. Adding a new value to the enumeration list treats it as a separate, independent value. The documentation on "Slot value resolution" shows that if "thrill-seeking" were a new value, it would be resolved as "thrill-seeking," not "adventure," thus requiring backend changes.

Source: AWS Documentation, Amazon Lex V2 Developer Guide, "Custom slot types," section on "Slot value resolution."

3. AWS Documentation - Amazon Lex V2 API Reference: The documentation for the RecognizeText and RecognizeUtterance operations describes runtimeHints. It specifies that these hints are part of the API request, confirming they are set programmatically from a client or backend service, not through static console configuration.

Source: AWS Documentation, Amazon Lex V2 API Reference, RecognizeText operation, runtimeHints parameter description.