Refer to the exhibit. For Company XYZ Bangkok is using ECMP to reach the 172.20.2.0/24 network. The company wants a design that would allow them to forward traffic from 172.16.2.0/24 toward…

PBR uses route maps applied to an interface to match packets by source address via an ACL and then sets a specific next hop, overriding the normal routing table lookup only for matched traffic. Because PBR operates per-packet before the FIB is consulted for matched flows, traffic from 172.16.2.0/24 is forwarded via Singapore while unmatched traffic falls through to the existing ECMP routing table entries.

Route summarization aggregates destination prefixes in the routing table and has no mechanism to differentiate forwarding based on source IP address.

Unequal-cost load balancing via variance distributes traffic proportionally across multiple paths based on metric ratios but cannot match and steer traffic by source address to a preferred next hop.

LFA pre-computes backup next hops for fast reroute during link or node failures and does not provide source-address-based traffic engineering for normal forwarding.