You have been asked to deploy BGP across a satellite link system to a small number of retail stores. What must you do to successfully deploy BGP in this situation?

Whether peering sessions are EBGP or IBGP depends on the AS numbering design of the retail stores, not on the fact that the link medium is a satellite.

The BGP hold timer should be increased for high-latency satellite links, not set to under one second, because the satellite propagation delay alone can exceed a sub-second hold timer.

BGP runs over TCP, and satellite links introduce round-trip delays of 500-600 ms along with potential MTU mismatches due to encapsulation. The TCP window size must be increased to fill the pipe efficiently on a high-latency link, the MTU must be sized to avoid fragmentation, and TCP keepalive timers must be adjusted so the BGP session does not time out during periods of low traffic - none of which happen by default.

Static route backup is an optional resilience measure and is not a requirement for successfully deploying BGP over a satellite link.