An IT helpdesk assistant handles requests such as 'reset my password,' 'change my password,' and 'I forgot my password.' The designer needs to capture the specific action the user requires. Which entity type BEST handles these surface-form variations?

A synonym entity allows multiple surface forms to resolve to the same entity value, enabling consistent downstream logic regardless of how the user phrases their need. Pattern entities handle structured formats like ID numbers. System entities cover numeric and date values. Contextual entities are more appropriate for ambiguous terms whose meaning depends on surrounding words. The correct answer, "A synonym entity where reset, change, and forgot are defined as synonyms mapping to a single entity value representing the password action", directly satisfies the scenario because it aligns with watsonx Assistant's design principles and the specific capability being tested. The incorrect options ("A pattern entity using a regular expression to match the literal word password in any sentence", "A built-in system entity such as @sys-number to identify numeric codes associated with password resets", "A contextual entity trained on annotated example sentences to detect account-related terms by position") 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 2: Conversational AI Design section of the certification exam.