I feel like the larger list of traffic-engineering constraints could be a benefit, but it seems more related to CSPF in general rather than just label stack reduction.
I remember practicing a question about CSPF and PCE, but I can't recall if delegating path calculation was specifically an advantage of label stack reduction.
Based on my understanding, the advantage of label stack reduction is that it allows the path calculation to be delegated to an external PCE. This can be useful in large networks where the routers may not have the resources to perform the full CSPF calculation themselves. I think that's the best answer here.
Hmm, I'm a bit confused on this one. I know CSPF is about constraint-based routing, but I'm not sure how label stack reduction fits into that. I'll have to re-read the material on MPLS and traffic engineering to refresh my memory.
Okay, let me think this through. The key advantage of enabling label stack reduction is that it can reduce the number of hops in the end-to-end path, right? I'm pretty confident that's the right answer here.
This question seems straightforward, but I want to make sure I understand the key differences between CSPF and CSPF with label stack reduction. I'll need to review my notes on the advantages of each approach.
I think option A is the correct answer. Enabling label stack reduction can help reduce the number of hops in the path, which is an advantage over plain CSPF.
Hyun
3 months agoDaren
3 months agoTammy
3 months agoRosendo
4 months agoMagnolia
4 months agoGail
4 months agoKarl
4 months agoNobuko
4 months agoElinore
5 months agoSarina
5 months agoRuth
5 months agoStefania
5 months agoJaney
5 months agoAdaline
9 months agoEloisa
10 months agoPa
8 months agoAliza
8 months agoAdell
8 months agoArminda
10 months agoLinsey
8 months agoLouis
8 months agoCherri
8 months agoCheryl
11 months agoRosina
10 months agoLong
10 months agoToi
11 months agoTalia
11 months agoElvera
11 months ago