A network administrator wants to receive a major alarm every time a controller or an Aruba switch goes down for either a local or an upstream device failure. Which A. B. C.

Question

Exhibit

Options

• ATrigger: Type='Device Down', Severity='Major'. Conditions: Device Type='Controller' AND Device Type='Router/Switch'.
• BTrigger: Type='Device Down', Severity='Major'. Conditions: Device Type='Controller' AND Device Type='Router/Switch'.
• CTrigger: Type='Device Down', Severity='Major'. Conditions: Device Type='Controller' AND Device Type='Universal Network'.

• A
  88% (21)
• B
  8% (2)
• C
  4% (1)

Explanation

Option A correctly pairs the Device Down trigger at Major severity with conditions targeting both Controller and Router/Switch device types - the two categories in Aruba's management platform (AirWave/Central) that represent controllers and Aruba switches respectively. Although options A and B appear identical as transcribed (likely a formatting artifact in the source question where B may differ by operator or condition detail), the key distinction lies in option C: it substitutes Router/Switch with Universal Network, which is a separate device category not representative of Aruba switches and would miss the switch-down events the admin needs. In Aruba's platform, Router/Switch is the precise device type label for managed switches, so using any other label would silently fail to match those devices in the alarm rule.

Memory tip: Think "Controller + Router/Switch = Cover Real devices" - both need the exact platform label. If you see "Universal Network," that's a red flag: it sounds generic but doesn't map to Aruba switches in the alarm engine.

No community discussion yet for this question.