A logistics firm has dual transports at each branch, MPLS for voice and broadband Internet for bulk data, but video conferencing flaps when both TLOCs are equal cost. Which TLOC list design should you apply in policy to steer traffic to specific transports?
Select an answer to reveal the explanation.
Short Explanation
You're steering by road, not by town, so name the roads first. TLOC lists let your policy pick MPLS or Internet colors directly, like choosing highway versus side street.
Full Explanation
TLOC lists group specific TLOCs by color, site, or encapsulation so centralized control or data policy can match traffic and set preferred TLOCs or backup paths per application SLA. That mechanism makes named TLOC lists for MPLS and Internet referenced in policy actions correct because it explicitly pins voice to MPLS and bulk to Internet and stabilizes video with ordered preference. Site lists for each branch fail by concept because site lists identify source or destination sites, not transports, so they cannot select a color. Prefix lists for voice subnets fail by concept because they match destination prefixes for route control, not transport selection without a TLOC action. VPN membership lists fail by concept because they control which VPNs exist on devices in localized policy, not WAN transport preference. Exam caveat is that TLOC lists live under centralized policy constructs in SD-WAN Manager and are referenced as actions, not match-only lists. Practical check is to verify colors, restrict versus prefer, and confirm active TLOC in SD-WAN Manager tunnel statistics.