Question 780At fictional Orchard Link 195, a regional service-provider network, during a preproduction design validation, operations observes: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. Which operational harm would persist without the intended correction? Healthy MPLS transport is disrupted by a false fault diagnosis. Transport LSPs are absent despite healthy basic IP routing. An incorrect topology conclusion prompts needless routing changes. Unnecessary route changes mask a switching defect and prolong the outage. ExplanationCorrect Answer C:An incorrect topology conclusion prompts needless routing changes. MPLS TTL handling can affect the hop visibility of path diagnostics. Interpret MPLS TTL and traceroute behavior using the configured transport model. Incorrect Answers A:Healthy MPLS transport is disrupted by a false fault diagnosis. The choice would be appropriate if an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Here, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. B:Transport LSPs are absent despite healthy basic IP routing. That option concerns two core routers cannot form an LDP session even though they discover one another on the connected link. The problem here is different: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. D:Unnecessary route changes mask a switching defect and prolong the outage. This could matter when an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. In this case, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut.
Question 781In a separate fictional JNCIS-SP lab review for Oakshore Peering 196, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. What should the Junos specialist change first to resolve this specific fault? Perform controlled LSP validation and only then switch the authorized service resolution. Inspect label stack, bottom-of-stack indicator, and the expected transport operation. Fix the OSPF export policy's precise match and validate external route origination. Interpret MPLS TTL and traceroute behavior using the configured transport model. ExplanationCorrect Answer D:Interpret MPLS TTL and traceroute behavior using the configured transport model. Forwarding tables and controlled trace results agree with documented TTL behavior. MPLS TTL handling can affect the hop visibility of path diagnostics. Incorrect Answers A:Perform controlled LSP validation and only then switch the authorized service resolution. This addresses a situation in which a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; however, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. B:Inspect label stack, bottom-of-stack indicator, and the expected transport operation. The choice would be appropriate if operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Here, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. C:Fix the OSPF export policy's precise match and validate external route origination. That option concerns a static service prefix is missing from OSPF because the export policy was attached but does not match it. The problem here is different: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut.
Question 782In a separate fictional JNCIS-SP lab review for Oakshore Peering 196, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. What technical principle underlies the right remedy? MPLS TTL handling can affect the hop visibility of path diagnostics. MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it. LDP distributes label mappings needed for label-switched forwarding paths. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. ExplanationCorrect Answer A:MPLS TTL handling can affect the hop visibility of path diagnostics. Forwarding tables and controlled trace results agree with documented TTL behavior. Interpret MPLS TTL and traceroute behavior using the configured transport model. Incorrect Answers B:MPLS ingress typically pushes a label, transit nodes swap, and egress behavior may remove it. This addresses a situation in which a network test expects the ingress PE to swap a label that it should actually impose; however, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. C:LDP distributes label mappings needed for label-switched forwarding paths. The choice would be appropriate if an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. Here, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. D:Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. That option concerns a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it. The problem here is different: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut.
Question 783In a separate fictional JNCIS-SP lab review for Oakshore Peering 196, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. Which acceptance finding demonstrates the affected service has recovered? The failing RSVP hop is identified and the LSP reports Up after correction. The target loopback FEC has a valid binding and corresponding programmed label action. The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately. Forwarding tables and controlled trace results agree with documented TTL behavior. ExplanationCorrect Answer D:Forwarding tables and controlled trace results agree with documented TTL behavior. Interpret MPLS TTL and traceroute behavior using the configured transport model. MPLS TTL handling can affect the hop visibility of path diagnostics. Incorrect Answers A:The failing RSVP hop is identified and the LSP reports Up after correction. It is useful for situations where an RSVP LSP stays down but engineers only examine the ingress router's IP default route; the reported fault, though, is that traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. B:The target loopback FEC has a valid binding and corresponding programmed label action. That relates to circumstances in which monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. Here the problem is that traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. C:The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately. This addresses a situation in which a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing; however, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut.
Question 784In a separate fictional JNCIS-SP lab review for Oakshore Peering 196, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: Traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. What is the direct residual network risk if the fault remains unresolved? Traffic bypasses an approved low-latency or protected path. An incorrect topology conclusion prompts needless routing changes. Traffic is briefly blackholed during normal network convergence. IPv6 routing does not converge across the link. ExplanationCorrect Answer B:An incorrect topology conclusion prompts needless routing changes. Interpret MPLS TTL and traceroute behavior using the configured transport model. MPLS TTL handling can affect the hop visibility of path diagnostics. Incorrect Answers A:Traffic bypasses an approved low-latency or protected path. This relates to a case where a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change; the current situation is that traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. C:Traffic is briefly blackholed during normal network convergence. That relates to circumstances in which a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Here the problem is that traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. D:IPv6 routing does not converge across the link. This addresses a situation in which an IPv6 prefix is missing across a point-to-point link because OSPFv2 was configured but OSPFv3 was omitted; however, traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut.
Question 785At fictional Brookridge Metro 197, a regional service-provider network, during a core-routing acceptance test, operations observes: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Which targeted remediation best fits the reported behavior? Use an appropriate segment list or routing design matching the required steering behavior. Identify the ingress, transit, and egress LSR roles before modifying label rules. Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery. Verify renewed label forwarding entries after the IGP path change and correct stale state. ExplanationCorrect Answer D:Verify renewed label forwarding entries after the IGP path change and correct stale state. MPLS label forwarding must follow the current resolved transport topology. The active label operation now uses the recovered egress next hop. Incorrect Answers A:Use an appropriate segment list or routing design matching the required steering behavior. This could help if a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path, but not when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. B:Identify the ingress, transit, and egress LSR roles before modifying label rules. This relates to a case where a network test expects the ingress PE to swap a label that it should actually impose; the current situation is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. C:Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery. It is useful for situations where a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree; the reported fault, though, is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device.
Question 786At fictional Brookridge Metro 197, a regional service-provider network, during a core-routing acceptance test, operations observes: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Why is this particular correction the best fit for the stated defect? A route's presence is insufficient if its selected MPLS transport next hop is unusable. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. Junos routing policy is evaluated by terms whose order and matching conditions affect the outcome. MPLS label forwarding must follow the current resolved transport topology. ExplanationCorrect Answer D:MPLS label forwarding must follow the current resolved transport topology. Verify renewed label forwarding entries after the IGP path change and correct stale state. The active label operation now uses the recovered egress next hop. Incorrect Answers A:A route's presence is insufficient if its selected MPLS transport next hop is unusable. It is relevant if a service path references an LSP that is down, but its IP route remains visible in the route table, but the reported issue is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. B:MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. This could help if operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header, but not when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. C:Junos routing policy is evaluated by terms whose order and matching conditions affect the outcome. This relates to a case where a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through; the current situation is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device.
Question 787At fictional Brookridge Metro 197, a regional service-provider network, during a core-routing acceptance test, operations observes: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. What direct observation would prove the corrective action worked? Packet observations match the intended push, swap, and disposition stages. A targeted incoming label maps to the intended outgoing label and interface. The active label operation now uses the recovered egress next hop. The path comparison identifies the deciding attributes and final active candidate. ExplanationCorrect Answer C:The active label operation now uses the recovered egress next hop. MPLS label forwarding must follow the current resolved transport topology. Verify renewed label forwarding entries after the IGP path change and correct stale state. Incorrect Answers A:Packet observations match the intended push, swap, and disposition stages. This is applicable when a network test expects the ingress PE to swap a label that it should actually impose; the present condition is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. B:A targeted incoming label maps to the intended outgoing label and interface. It is relevant if an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing, but the reported issue is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. D:The path comparison identifies the deciding attributes and final active candidate. This relates to a case where a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; the current situation is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device.
Question 788At fictional Brookridge Metro 197, a regional service-provider network, during a core-routing acceptance test, operations observes: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Which failure consequence follows most closely from ignoring this issue? An SID collision or wrong label steers packets onto an unintended destination. Packets cannot travel the intended MPLS transport path. MPLS traffic remains broken despite restored IGP neighbors. Customer Layer 2 service fails despite healthy physical link status. ExplanationCorrect Answer C:MPLS traffic remains broken despite restored IGP neighbors. MPLS label forwarding must follow the current resolved transport topology. Verify renewed label forwarding entries after the IGP path change and correct stale state. Incorrect Answers A:An SID collision or wrong label steers packets onto an unintended destination. That could help when a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation; here, after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. B:Packets cannot travel the intended MPLS transport path. This is applicable when an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop; the present condition is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. D:Customer Layer 2 service fails despite healthy physical link status. This could help if a provider access port drops customer tagged frames because it was configured for untagged access mode, but not when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device.
Question 789In a separate fictional JNCIS-SP lab review for Stonefield Telecom 198, a carrier-edge and core routing team, following a monitored network change window, engineers find: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. What intervention most directly restores the intended routing or switching behavior? Inspect label stack, bottom-of-stack indicator, and the expected transport operation. Verify renewed label forwarding entries after the IGP path change and correct stale state. Review RSVP path constraints and explicit-route settings, then reestablish the LSP. Align the supported metric style and review full link metrics across the participating routing level. ExplanationCorrect Answer B:Verify renewed label forwarding entries after the IGP path change and correct stale state. The active label operation now uses the recovered egress next hop. MPLS label forwarding must follow the current resolved transport topology. Incorrect Answers A:Inspect label stack, bottom-of-stack indicator, and the expected transport operation. This could matter when operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. In this case, after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. C:Review RSVP path constraints and explicit-route settings, then reestablish the LSP. This is applicable when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route; the present condition is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. D:Align the supported metric style and review full link metrics across the participating routing level. It is relevant if an intended core link metric is truncated by a mismatched metric-style design and fails to shift paths as expected, but the reported issue is that after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device.
Question 790In a separate fictional JNCIS-SP lab review for Stonefield Telecom 198, a carrier-edge and core routing team, following a monitored network change window, engineers find: After an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. Which networking principle explains why the proposed correction is appropriate? MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. Protocol adjacency health does not prove every required MPLS forwarding entry exists. Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. MPLS label forwarding must follow the current resolved transport topology. ExplanationCorrect Answer D:MPLS label forwarding must follow the current resolved transport topology. The active label operation now uses the recovered egress next hop. Verify renewed label forwarding entries after the IGP path change and correct stale state. Incorrect Answers A:MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. It addresses a different problem: A new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. Here, after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. B:Protocol adjacency health does not prove every required MPLS forwarding entry exists. This could matter when monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback. In this case, after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. C:Aggregate route eligibility depends on the presence of suitable contributing routes and policy conditions. That could help when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; here, after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device.