Refer to Exhibit. An HPE Aruba Networking 9x00 gateway is part of an HPE Aruba Networking Central group that has the settings shown in the exhibit. What would cause the gateway to drop traffic as…

Question

Exhibit

Options

• AIts site-to-site VPN connections failing
• BTraffic matching a rule in the active ruleset
• CIts IDPS engine failing
• DTraffic showing anomalous behavior

• A
  5% (3)
• B
  81% (48)
• C
  2% (1)
• D
  12% (7)

Explanation

Option B is correct because IDPS in prevention mode actively drops traffic that matches a signature in the active ruleset - that is literally the enforcement mechanism of the "Prevention" side of IDPS. The exhibit shows the gateway configured with an active ruleset, so any traffic matching those signatures is blocked inline.

Why the distractors are wrong:

• A (VPN failure): Site-to-site VPN is a separate feature; its failure affects tunnel connectivity, not IDPS enforcement decisions.
• C (IDPS engine failure): A failed IDPS engine typically causes a fail-open condition (traffic is passed, not dropped), so the engine failing is the opposite of dropping traffic via IDPS.
• D (Anomalous behavior): Anomaly detection may generate alerts, but HPE Aruba's IDPS drops traffic based on rule matches in the configured ruleset, not on general behavioral anomalies.

Memory tip: Think of the IDPS ruleset as a blocklist - traffic only gets dropped when it hits a rule, just like a firewall only blocks what matches a deny rule. If anything else breaks (VPN, engine), IDPS stays out of the way.

No community discussion yet for this question.