400-007 · Question #252
Company XYZ must design a strategy to protect their routers from DoS attacks such as traffic destined to the router's own route processor, using separate control plane categories. Which two…
The correct answer is B. Control Plane Protection using queue thresholding on the host subinterface C. Control Plane Protection using port filtering on the host subinterface. Cisco Control Plane Protection (CPPr) uses the host subinterface to police traffic destined directly to the router's route processor, supporting both queue thresholding and port filtering as protection mechanisms.
Question
Company XYZ must design a strategy to protect their routers from DoS attacks such as traffic destined to the router's own route processor, using separate control plane categories. Which two capabilities can be used to achieve this requirement? (Choose two.)
Options
- AControl Plane Protection using queue thresholding on the transit subinterface
- BControl Plane Protection using queue thresholding on the host subinterface
- CControl Plane Protection using port filtering on the host subinterface
- DControl Plane Protection using port filtering on the transit subinterface
- EControl Plane Protection using port filtering on the main interface
How the community answered
(23 responses)- A13% (3)
- B78% (18)
- D4% (1)
- E4% (1)
Why each option
Cisco Control Plane Protection (CPPr) uses the host subinterface to police traffic destined directly to the router's route processor, supporting both queue thresholding and port filtering as protection mechanisms.
The transit subinterface handles traffic passing through the router to another destination, not traffic destined to the router itself, so queue thresholding there does not protect the route processor.
The host subinterface in CPPr specifically handles traffic addressed to the router's own IP addresses (including the route processor), so applying queue thresholding here directly caps the packet rate reaching the RP, mitigating DoS flooding attacks.
Port filtering on the host subinterface drops packets targeting specific TCP/UDP ports before they consume RP CPU resources, providing granular per-protocol protection against DoS attacks aimed directly at the route processor.
Port filtering on the transit subinterface filters forwarded through-traffic, not traffic aimed at the router's own route processor, making it ineffective for the stated requirement.
The CPPr main interface is a parent aggregate interface; applying filtering only at the main interface does not provide the per-category granularity that dedicated host and transit subinterfaces deliver.
Concept tested: Cisco CPPr host subinterface mechanisms for route processor protection
Source: https://www.cisco.com/c/en/us/support/docs/ip/access-lists/43920-cpp.html
Topics
Community Discussion
No community discussion yet for this question.