During a performance audit of an enterprise router, traffic containing specialized IP options is punted to the main Route Processor CPU for intensive processing, raising local CPU usage to nearly 100%. Despite this high CPU utilization on the Route Processor, standard transit data packets matching pre-calculated forwarding entries continue flowing through the router without any measurable latency or throughput impact. Which operational mechanism explains why standard transit traffic performance remains unaffected?
- Data plane transit traffic is switched in hardware by specialized ASICs using the Forwarding Information Base (FIB), bypassing the general control plane CPU.Cevap
- BThe control plane dynamic routing process buffers transit packets on interface queues until CPU utilization drops below critical thresholds.
- CThe centralized SDN controller dynamically absorbs all data plane switching responsibilities via Southbound APIs when local CPU load spikes.
- DThe router management plane automatically offloads IP option processing tasks directly into the Layer 2 MAC address table for hardware acceleration.
Cevap
Data plane transit traffic is switched in hardware by specialized ASICs using the Forwarding Information Base (FIB), bypassing the general control plane CPU.
The correct option highlights the fundamental distinction between the control plane and data plane. The control plane CPU computes routing paths and populates the Routing Information Base (RIB). This information is compiled into the Forwarding Information Base (FIB) and programmed into dedicated hardware ASICs on the data plane. Consequently, standard transit traffic matching FIB entries is handled entirely in hardware, remaining completely immune to general CPU utilization spikes caused by exception packets (such as those with IP options).
Adım Adım Çözüm
Anahtar Kavram
Separation of Control Plane CPU decisions and Data Plane ASIC forwarding