You are asked to design an RSVP-TE LSP protection solution for a large service provider network. Which traffic protection mechanism is highly scalable and ensures that multiple LSPs always terminate a

Detour LSPs provide per-LSP local repair by creating individual bypass tunnels around a failed node or link, which does not scale well in large networks because every protected LSP requires its own dedicated detour path.

1:1 protection dedicates one unique backup LSP for every single primary LSP, consuming significantly more bandwidth and signaling resources, making it poorly suited for large-scale deployments.

1:N protection maps one backup LSP to N primary LSPs, all of which share the same merge point at the tail end. This is highly scalable because only one set of backup resources is reserved regardless of how many primary LSPs are protected. When a failure occurs on any of the N primary LSPs, traffic is rerouted onto the single shared backup path without requiring per-LSP backup provisioning.

Shared-explicit reservation style is an RSVP session attribute that allows multiple senders to share a single reservation object, but it is not a defined LSP protection model and does not prescribe a common merge point architecture.