Which statement about hot-potato routing architecture design is true?

Hot-potato routing hands off traffic to the peer AS at the closest possible exit point, reducing the distance and resources traffic consumes within the local network, which is ideal when connecting to content providers who can then carry the traffic efficiently on their own infrastructure.

Hot-potato routing does the opposite - it minimizes the time traffic stays under the local network administrator's control by exiting the AS as early as possible; cold-potato routing is the strategy that retains traffic longer.

OSPF external metric values influence route selection within an AS but do not define hot-potato routing, which is a BGP and inter-AS traffic engineering philosophy, not an OSPF-specific behavior.

Hot-potato routing is a deliberate and well-understood inter-domain routing strategy; while it requires coordination, it is not inherently more prone to misconfiguration than other routing architectures.