Question 330
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An MPLS transport router receives label mappings for prefixes it should never carry, causing label-space pressure. Which observable result most directly verifies that this network issue was resolved?
Explanation
Correct Answer
For this scenario, the observed situation is: An MPLS transport router receives label mappings for prefixes it should never carry, causing label-space pressure. The most directly supported response is: Filter permitted LDP label allocation and advertise only necessary FECs on the supported platform. Technical basis: LDP bindings associate FECs with labels and can be constrained by control-plane policy. Evidence of success: The label database contains intended FEC mappings and unauthorized allocations stop appearing. Ongoing protection: Review label allocation filters and resource utilization as the routing table grows.
Incorrect Answers
That observation tests a different mechanism: TE tunnel control-plane teardown and service-level forwarding dependencies must be coordinated. It cannot establish this case, whose mechanism is: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The needed verification is: The label database contains intended FEC mappings and unauthorized allocations stop appearing.
That observation tests a different mechanism: SR-MPLS uses IGP-advertised SIDs with label-index interpretation relative to the SRGB. It cannot establish this case, whose mechanism is: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The needed verification is: The label database contains intended FEC mappings and unauthorized allocations stop appearing.
That observation tests a different mechanism: RSVP-TE signaling can reserve bandwidth and fail when requested resources are unavailable. It cannot establish this case, whose mechanism is: LDP bindings associate FECs with labels and can be constrained by control-plane policy. The needed verification is: The label database contains intended FEC mappings and unauthorized allocations stop appearing.