HPE7-A02 · Question #113
A company has AOS-CX switches. The company wants to make it simpler and faster for admins to detect denial of service (DoS) attacks, such as ping or ARP floods, launched against the switches. What…
The correct answer is A. Deploy an NAE agent on the switches to monitor control plane policing (CoPP). Option A is correct because NAE (Network Analytics Engine) agents run directly on AOS-CX switches and can monitor Control Plane Policing (CoPP) statistics in real time - CoPP tracks and rate-limits traffic destined for the switch CPU, so spikes in ICMP or ARP traffic (classic…
Question
A company has AOS-CX switches. The company wants to make it simpler and faster for admins to detect denial of service (DoS) attacks, such as ping or ARP floods, launched against the switches. What can you do to support this use case?
Options
- ADeploy an NAE agent on the switches to monitor control plane policing (CoPP).
- BConfigure the switches to implement RADIUS accounting to HPE Aruba Networking ClearPass
- CImplement ARP inspection on all VLANs that support end-user devices.
- DEnabling debugging of security functions on the switches.
How the community answered
(54 responses)- A78% (42)
- B2% (1)
- C15% (8)
- D6% (3)
Explanation
Option A is correct because NAE (Network Analytics Engine) agents run directly on AOS-CX switches and can monitor Control Plane Policing (CoPP) statistics in real time - CoPP tracks and rate-limits traffic destined for the switch CPU, so spikes in ICMP or ARP traffic (classic DoS indicators) are immediately visible, enabling fast, automated detection and alerting without manual log analysis.
Option B is wrong because RADIUS accounting tracks user authentication events for identity/access auditing, not switch CPU traffic patterns - it won't detect a ping or ARP flood hitting the switch itself.
Option C is wrong because Dynamic ARP Inspection (DAI) prevents ARP spoofing by validating ARP packets against a DHCP snooping binding table - it's a mitigation/prevention control, not a detection tool for flooding attacks.
Option D is wrong because enabling debugging generates verbose logs that are useful for troubleshooting specific issues but are not designed for continuous, efficient DoS detection - they add overhead and are not a scalable monitoring solution.
Memory tip: Think of NAE as the switch's "always-on analyst" - it watches internal telemetry like CoPP counters continuously, so when a flood hits, the agent catches it immediately. The key phrase in the question is "simpler and faster to detect", which points directly to automated agent-based monitoring rather than reactive or preventive tools.
Topics
Community Discussion
No community discussion yet for this question.