A rural fiber cooperative's network engineer is asked which Junos component is responsible for actually switching subscriber traffic from an incoming interface to the correct outgoing interface at line rate, on a core aggregation router. Which component performs this function?
Select an answer to reveal the explanation.
Short Explanation
Think of the Packet Forwarding Engine as the co-op's loading dock crew - fast, hands-on, and working from a list someone else prepared. It reads the forwarding table that the Routing Engine already built and moves packets from the right inbound port to the right outbound port using dedicated hardware, so ordinary traffic never waits on software decisions. That hardware path is what lets a core router keep pace with thousands of subscriber flows.
Full Explanation
The Packet Forwarding Engine is the Junos subsystem built specifically for high-speed packet switching: it holds a hardware copy of the forwarding table, produced from the Routing Engine's routing table, and uses that copy to make per-packet forwarding decisions in dedicated hardware rather than general-purpose software. This lets a core aggregation router in a rural fiber build sustain line-rate throughput for ordinary transit traffic. The distractors misassign this job: the Routing Engine builds and maintains the routing table but does not itself switch every packet - doing so would make throughput dependent on CPU speed rather than dedicated hardware; the management daemon handles configuration and CLI sessions, not per-packet switching; and the chassis control process monitors physical components like power supplies and fans, unrelated to the data path. A useful distinction for the exam is control decisions versus data-path execution - the Routing Engine decides what the forwarding table should say, and the Packet Forwarding Engine executes it. An operational check worth knowing conceptually: forwarding continues to work correctly only as long as the forwarding hardware's table matches what the Routing Engine most recently computed.