Scenario: To receive data alerts for failures, a Citrix Administrator is configuring SNMP on the Citrix ADC. The administrator is confident that the manager, alarms, and SNMP traps are configured…

Question

Options

• AThe Citrix ADC is configured for SNMP version 1.
• BThe Citrix Web App Firewall is blocking the alerts from going out.
• CThe Citrix ADC only has standard licensing.
• DThe community name was NOT configured in the Citrix ADC SNMP trap destination settings.

• A
  13% (3)
• B
  9% (2)
• C
  4% (1)
• D
  74% (17)

Explanation

Option D is correct because the SNMP community name acts as a shared authentication token between the Citrix ADC (trap sender) and the SNMP manager (receiver). Without the community string configured in the trap destination settings, the ADC cannot properly authenticate its trap messages, so they are either not sent or silently rejected by the manager - resulting in no alerts during the outage.

Why the distractors are wrong:

• A - SNMP v1 is a valid, functional protocol version; using it would not prevent traps from being delivered.
• B - Citrix Web App Firewall inspects HTTP/S web traffic, not SNMP (UDP port 162); it would not intercept or block outgoing SNMP traps.
• C - SNMP is a core feature available on standard Citrix ADC licensing; no premium license tier is required to send traps.

Memory tip: Think of the SNMP community name as the "handshake password" - the trap destination needs it to recognize and trust the ADC's alerts. The question even hints at this by saying everything else (manager, alarms, traps) was configured correctly, pointing to a single missing piece in the destination settings.

No community discussion yet for this question.