What is the most likely reason for SNMP alerts not being received despite correct configuration?

What is the most likely reason for SNMP alerts not being received despite correct configuration?

• A. The Citrix Web App Firewall is blocking the alerts from going out.
• B. The community name was NOT configured in the Citrix ADC SNMP trap destination settings.
• C. The Citrix ADC only has standard licensing.
• D. The Citrix ADC is configured for SNMP version 1.

Answer: (C)

Licensing controls whether SNMP alerting is enabled on the Citrix ADC. Even with correct destination, community, and SNMP version, traps won’t be generated or sent if the device’s license level doesn’t include SNMP alerting features. With a standard license, the SNMP trap/alert capability is not available, so no alerts reach the manager. Upgrading to a license tier that includes SNMP alerting (or enabling the required feature) is needed for traps to be emitted. In practice, other issues like a blocked path or incorrect community or version would typically show some signs of failure related to configuration or network path, whereas the licensing limitation explains why everything appears configured correctly but no alerts are produced at all.

Licensing controls whether SNMP alerting is enabled on the Citrix ADC. Even with correct destination, community, and SNMP version, traps won’t be generated or sent if the device’s license level doesn’t include SNMP alerting features. With a standard license, the SNMP trap/alert capability is not available, so no alerts reach the manager. Upgrading to a license tier that includes SNMP alerting (or enabling the required feature) is needed for traps to be emitted.

In practice, other issues like a blocked path or incorrect community or version would typically show some signs of failure related to configuration or network path, whereas the licensing limitation explains why everything appears configured correctly but no alerts are produced at all.