A regional ISP's core router in its main POP experiences a Routing Engine process restart during a routine software patch, but subscribers report no interruption to traffic already flowing through existing sessions. Which aspect of Junos architecture best explains this behavior?
Select an answer to reveal the explanation.
Short Explanation
Picture the control plane as the router's brain and the forwarding plane as its hands - the hands keep doing the job they were already trained for even if the brain steps out for a second. Junos programs the forwarding table into the forwarding hardware ahead of time, so transit packets keep moving off that already-programmed table while the Routing Engine restarts. The moment the Routing Engine comes back, it resumes updating routes and can refresh that table.
Full Explanation
The Packet Forwarding Engine and the Routing Engine are deliberately separate subsystems in Junos: the Routing Engine runs the control-plane software that computes routes and builds a forwarding table, then downloads that table into the Packet Forwarding Engine's hardware so transit packets can be switched at line rate without consulting the Routing Engine for every packet. When the Routing Engine restarts, the previously downloaded forwarding table stays resident in the Packet Forwarding Engine, so already-established transit flows keep moving; only route recalculation and forwarding-table updates pause until the Routing Engine returns. The wrong options misplace where the resilience comes from: the Packet Forwarding Engine does not run its own copy of the routing software, a backup Internet path is a network-design choice and not something Junos architecture guarantees automatically, and control and forwarding are never merged into one process - keeping them separate is exactly what makes this resilience possible. A useful operational check after any Routing Engine event is confirming route freshness once it returns, since the forwarding table can grow stale for any routes that changed while the Routing Engine was unavailable.