A regional hospital group runs a central records hub with fiber and LTE TLOCs in VPN 20 advertising patient-imaging prefixes. Clinics must send imaging uploads to the fiber TLOC for throughput, fail over automatically to LTE if fiber is unreachable, and require no extra routing policy on clinic routers. Which TLOC preference configuration on the hub best controls path selection toward the destination?

TLOC preference is advertised with the hub OMP routes for VPN 20 and controls how remote clinic edges choose the destination TLOC for those imaging prefixes, so setting a higher value on fiber makes it the preferred ingress while LTE remains as automatic backup when fiber OMP/TLOC is withdrawn, satisfying throughput, resilience, and no clinic policy in one hub-side change. Advertising the imaging prefixes only via fiber pins traffic correctly during normal operation but violates the failover requirement because clinics lose all reachable paths if fiber fails, which is a valid filtering technique for traffic pinning but not for resilient services. Preferring the LTE TLOC is operationally sound for favoring a stable or lower-cost backup path, yet it directly contradicts the stated need to use fiber for throughput and would steer steady-state uploads onto constrained LTE. Configuring equal preference on both hub TLOCs is a common design for ECMP load sharing and utilization, but it fails the determinism requirement because clinics will distribute flows across both transports instead of preferring fiber first. For exam purposes, remember that destination-side TLOC preference governs remote ingress selection, whereas local color preference or outbound policy governs local egress and site preference governs site-level path choice, so match the mechanism to the direction of control. In practice, verify with show omp routes vpn 20 plus TLOC details on a clinic edge to confirm fiber shows higher preference and reachability, then simulate fiber loss to confirm convergence to LTE without touching clinic configuration.