Q: 4
Which utility can you use to locate MPLS faults?
Options
Discussion
Option C here. Tricky since A is usually a trap for path mapping, but C is for pinpointing MPLS LSP faults specifically.
C imo. MPLS traceroute (A) is tempting but only shows hops, doesn't actually catch LSP faults like C does.
Why is nobody mentioning B? EEM scripts could also help troubleshoot faults, but not as directly as C.
Probably C here since MPLS LSP ping is made for finding faults in the LSP, not just mapping the path. Traceroute (A) doesn't check LSP integrity, it just shows hops. Pretty sure Cisco wants C for fault isolation but correct me if I'm missing something.
B. not A. MPLS LSP ping (C) is designed to actually test and verify the health of an MPLS LSP, not just trace the route. Traceroute only maps the path, so you wouldn’t spot specific LSP faults that way. Pretty sure C is what Cisco expects for this one.
Cisco loves to jumble up traceroute and LSP ping in these exams, but seriously, C tbh.
C , that's the only one here that actually checks if the LSP is working properly, not just showing hops.
C , had something like this in a mock, MPLS LSP ping is what finds faults in the LSP path.
Yeah, it's C. MPLS LSP ping is the go-to for actually checking where the label switched path breaks.
C tbh. MPLS LSP ping is what specifically checks for faults in the label switched path, not just tracing it.
Be respectful. No spam.
