Quick Answer

The correct order begins with both peers advertising the graceful restart capability in the OPEN message, followed by exchanging the restart time and stale-path timer via capabilities, then the helper router marking routes as stale upon session failure, the restarting router re-establishing the session, and finally the helper removing stale routes if not refreshed. This sequence is correct because BGP graceful restart relies on a negotiated capability exchange to preserve forwarding during a control plane failure; the helper must first learn the restart timers to know how long to retain stale routes, and only after the session is re-established can it safely purge routes that were not refreshed. On the ENCOR 350-401 exam, this drag-and-drop task tests your understanding of the order of operations in high-availability BGP designs, and a common trap is confusing when stale routes are marked versus when they are removed—remember that marking happens immediately upon session failure, while removal waits for the new session. A helpful memory tip is to think of the acronym “C-M-R-R-R”: Capability exchange, Mark stale, Re-establish session, Remove stale.