When creating an alert for a Universal Device Poller (UnDP), which trigger condition helps you target the custom poller you want?

• A. A trigger condition where the custom poller Unique Name is equal to the name of your UnDP
• B. A trigger condition based on the poller's ID
• C. A trigger condition based on the poller's type
• D. A trigger condition based on the poller's description

Answer: (A)

Targeting the exact UnDP in an alert is accomplished by matching the trigger to the poller’s Unique Name. The Unique Name serves as the stable, user-facing identifier that uniquely distinguishes one custom poller from another, so configuring the alert to require that the Unique Name equals the name of your UnDP ensures the alert fires only for that specific poller’s data.

Other fields like poller ID, type, or description are less reliable for pinpointing a single poller. The ID is an internal numeric value that isn’t as portable or easy to reference in alert logic; the type groups pollers by category rather than by individual poller; and the description is free text and can be duplicated or changed, which could lead to incorrect matches.