Your company requires two diverse multihop External Border Gateway Protocol peerings to a partner network. Which two methods would you use to improve lost peer detection? (Choose two.)

BFD for multihop eBGP requires explicit multihop BFD configuration and is less reliable across diverse forwarding paths; SAT and Fast Peering Session Deactivation are the preferred Cisco-recommended tools for this scenario.

Selective Address Tracking (SAT) monitors the routing table for the reachability of a BGP neighbor's address and immediately deactivates the BGP session when the peer IP becomes unreachable, providing event-driven failure detection suited for multihop sessions.

Subsecond keepalives significantly increase control-plane traffic and CPU processing on both peers, adding network burden rather than efficiently detecting failure.

Subsecond hold timers cause BGP sessions to tear down at the slightest delay or packet loss, leading to excessive instability and route churn rather than reliable failure detection.

Fast Peering Session Deactivation uses Cisco's event-driven infrastructure to detect BGP peer loss faster than standard keepalive/hold-timer expiry by tracking next-hop reachability changes, which is especially valuable for multihop eBGP peerings where BFD echo mode is unavailable.

The minimum route advertisement interval (MRAI) controls how frequently BGP sends routing updates to peers and has no effect on detecting whether a peer session itself is lost.