Question 760In a separate fictional JNCIS-SP lab review for Bluehaven Backbone 190, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. What likely service impact does this condition create? Healthy MPLS transport is disrupted by a false fault diagnosis. Labeled packets are discarded at the affected core node. Customers experience a blackhole hidden by otherwise present route advertisements. Half the expected capacity is unavailable and link failover is fragile. ExplanationCorrect Answer A:Healthy MPLS transport is disrupted by a false fault diagnosis. Validate the advertised label behavior and egress processing expectations. Penultimate-hop popping can remove the outer transport label before the final LSR. Incorrect Answers B:Labeled packets are discarded at the affected core node. It is useful for situations where an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing; the reported fault, though, is that an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. C:Customers experience a blackhole hidden by otherwise present route advertisements. That relates to circumstances in which a service path references an LSP that is down, but its IP route remains visible in the route table. Here the problem is that an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. D:Half the expected capacity is unavailable and link failover is fragile. This addresses a situation in which a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ; however, an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP.
Question 761At fictional Lakewood Carrier 191, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A service path references an LSP that is down, but its IP route remains visible in the route table. Which configuration or operational correction most directly addresses this failure? Interpret MPLS TTL and traceroute behavior using the configured transport model. Identify the ingress, transit, and egress LSR roles before modifying label rules. Restore the intended LSP or safe route resolution and verify the forwarding next hop. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. ExplanationCorrect Answer C:Restore the intended LSP or safe route resolution and verify the forwarding next hop. A route's presence is insufficient if its selected MPLS transport next hop is unusable. The route resolves through an operational LSP and test traffic reaches the remote endpoint. Incorrect Answers A:Interpret MPLS TTL and traceroute behavior using the configured transport model. This could help if traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut, but not when a service path references an LSP that is down, but its IP route remains visible in the route table. 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 a service path references an LSP that is down, but its IP route remains visible in the route table. D:Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. That relates to circumstances in which a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Here the problem is that a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 762At fictional Lakewood Carrier 191, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A service path references an LSP that is down, but its IP route remains visible in the route table. Which Junos forwarding or control-plane rule applies to this case? A prefix SID normally expresses reachability to a node or prefix along the underlying shortest path. LDP discovery and the TCP-based LDP session depend on usable transport reachability. Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. A route's presence is insufficient if its selected MPLS transport next hop is unusable. ExplanationCorrect Answer D:A route's presence is insufficient if its selected MPLS transport next hop is unusable. Restore the intended LSP or safe route resolution and verify the forwarding next hop. The route resolves through an operational LSP and test traffic reaches the remote endpoint. Incorrect Answers A:A prefix SID normally expresses reachability to a node or prefix along the underlying shortest path. It is relevant 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 the reported issue is that a service path references an LSP that is down, but its IP route remains visible in the route table. B:LDP discovery and the TCP-based LDP session depend on usable transport reachability. This could help if two core routers cannot form an LDP session even though they discover one another on the connected link, but not when a service path references an LSP that is down, but its IP route remains visible in the route table. C:Forwarding normally selects the longest matching prefix before route preference can choose among candidates for that prefix. This relates to a case where an operator changes route preference to make a broader prefix override a healthy more-specific prefix; the current situation is that a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 763At fictional Lakewood Carrier 191, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A service path references an LSP that is down, but its IP route remains visible in the route table. What operational evidence best establishes successful remediation? The link carries protected MPLS traffic only after the required label state is available. The route resolves through an operational LSP and test traffic reaches the remote endpoint. Forwarding tables and controlled trace results agree with documented TTL behavior. MAC entries stabilize on the intended interface after repairing the bridge path. ExplanationCorrect Answer B:The route resolves through an operational LSP and test traffic reaches the remote endpoint. A route's presence is insufficient if its selected MPLS transport next hop is unusable. Restore the intended LSP or safe route resolution and verify the forwarding next hop. Incorrect Answers A:The link carries protected MPLS traffic only after the required label state is available. This is applicable when a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage; the present condition is that a service path references an LSP that is down, but its IP route remains visible in the route table. C:Forwarding tables and controlled trace results agree with documented TTL behavior. This could help if traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut, but not when a service path references an LSP that is down, but its IP route remains visible in the route table. D:MAC entries stabilize on the intended interface after repairing the bridge path. This relates to a case where a MAC moves rapidly among provider ports after a cabling change, yet troubleshooting focuses only on IP routing tables; the current situation is that a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 764At fictional Lakewood Carrier 191, a regional service-provider network, during a planned PE-to-core handoff, operations observes: A service path references an LSP that is down, but its IP route remains visible in the route table. Which operational harm would persist without the intended correction? Customers experience a blackhole hidden by otherwise present route advertisements. Traffic is briefly blackholed during normal network convergence. The engineered service remains unavailable or overcommits transit capacity. GRE packets are discarded by a transit filter despite valid inner routes. ExplanationCorrect Answer A:Customers experience a blackhole hidden by otherwise present route advertisements. A route's presence is insufficient if its selected MPLS transport next hop is unusable. Restore the intended LSP or safe route resolution and verify the forwarding next hop. Incorrect Answers B:Traffic is briefly blackholed during normal network convergence. This is applicable when a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage; the present condition is that a service path references an LSP that is down, but its IP route remains visible in the route table. C:The engineered service remains unavailable or overcommits transit capacity. It is relevant if an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link, but the reported issue is that a service path references an LSP that is down, but its IP route remains visible in the route table. D:GRE packets are discarded by a transit filter despite valid inner routes. This could help if a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL, but not when a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 765In a separate fictional JNCIS-SP lab review for Summitfield Carrier 192, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A service path references an LSP that is down, but its IP route remains visible in the route table. What should the Junos specialist change first to resolve this specific fault? 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. Correct the RIB-group import/export table membership and verify only the intended route exchange. Restore the intended LSP or safe route resolution and verify the forwarding next hop. ExplanationCorrect Answer D:Restore the intended LSP or safe route resolution and verify the forwarding next hop. The route resolves through an operational LSP and test traffic reaches the remote endpoint. A route's presence is insufficient if its selected MPLS transport next hop is unusable. Incorrect Answers A:Verify renewed label forwarding entries after the IGP path change and correct stale state. This could matter when after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device. In this case, a service path references an LSP that is down, but its IP route remains visible in the route table. B:Review RSVP path constraints and explicit-route settings, then reestablish the LSP. That could help when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route; here, a service path references an LSP that is down, but its IP route remains visible in the route table. C:Correct the RIB-group import/export table membership and verify only the intended route exchange. This is applicable when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table; the present condition is that a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 766In a separate fictional JNCIS-SP lab review for Summitfield Carrier 192, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A service path references an LSP that is down, but its IP route remains visible in the route table. What technical principle underlies the right remedy? Penultimate-hop popping can remove the outer transport label before the final LSR. A route's presence is insufficient if its selected MPLS transport next hop is unusable. MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. The IS-IS overload indication can discourage transit use during control-plane recovery. ExplanationCorrect Answer B:A route's presence is insufficient if its selected MPLS transport next hop is unusable. The route resolves through an operational LSP and test traffic reaches the remote endpoint. Restore the intended LSP or safe route resolution and verify the forwarding next hop. Incorrect Answers A:Penultimate-hop popping can remove the outer transport label before the final LSR. It addresses a different problem: An operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. Here, a service path references an LSP that is down, but its IP route remains visible in the route table. C:MPLS transport cutovers need working end-to-end label forwarding, not just successful configuration commits. That could help when a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested; here, a service path references an LSP that is down, but its IP route remains visible in the route table. D:The IS-IS overload indication can discourage transit use during control-plane recovery. This is applicable when a newly rebooted core router attracts transit traffic while its forwarding state is still being restored; the present condition is that a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 767In a separate fictional JNCIS-SP lab review for Summitfield Carrier 192, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A service path references an LSP that is down, but its IP route remains visible in the route table. Which acceptance finding demonstrates the affected service has recovered? An MPLS-aware trace and service probe pass before and after the selected cutover. The route resolves through an operational LSP and test traffic reaches the remote endpoint. The RSVP LSP is up with the intended transit hop sequence. Peer SPF paths avoid the router while overloaded and normal paths return after it is cleared. ExplanationCorrect Answer B:The route resolves through an operational LSP and test traffic reaches the remote endpoint. Restore the intended LSP or safe route resolution and verify the forwarding next hop. A route's presence is insufficient if its selected MPLS transport next hop is unusable. Incorrect Answers A:An MPLS-aware trace and service probe pass before and after the selected cutover. That option concerns a new MPLS LSP is provisioned and traffic is moved before its end-to-end reachability has been tested. The problem here is different: A service path references an LSP that is down, but its IP route remains visible in the route table. C:The RSVP LSP is up with the intended transit hop sequence. This could matter when an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route. In this case, a service path references an LSP that is down, but its IP route remains visible in the route table. D:Peer SPF paths avoid the router while overloaded and normal paths return after it is cleared. That could help when a newly rebooted core router attracts transit traffic while its forwarding state is still being restored; here, a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 768In a separate fictional JNCIS-SP lab review for Summitfield Carrier 192, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: A service path references an LSP that is down, but its IP route remains visible in the route table. What is the direct residual network risk if the fault remains unresolved? An incorrect topology conclusion prompts needless routing changes. Customers experience a blackhole hidden by otherwise present route advertisements. Packets cannot travel the intended MPLS transport path. Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. ExplanationCorrect Answer B:Customers experience a blackhole hidden by otherwise present route advertisements. Restore the intended LSP or safe route resolution and verify the forwarding next hop. A route's presence is insufficient if its selected MPLS transport next hop is unusable. Incorrect Answers A:An incorrect topology conclusion prompts needless routing changes. The choice would be appropriate if traceroute across an MPLS core shows fewer visible routers than expected and engineers assume the packets are taking a forbidden shortcut. Here, a service path references an LSP that is down, but its IP route remains visible in the route table. C:Packets cannot travel the intended MPLS transport path. It addresses a different problem: An MPLS service route is reachable at IP level but its LDP label binding is missing on one hop. Here, a service path references an LSP that is down, but its IP route remains visible in the route table. D:Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. This could matter when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. In this case, a service path references an LSP that is down, but its IP route remains visible in the route table.
Question 769At fictional Brightstone Backbone 193, a regional service-provider network, during a two-site transit migration, operations observes: A tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. Which targeted remediation best fits the reported behavior? Apply the supported LDP and IGP synchronization design and verify staged activation. Align route resolution and LSP preference with the documented transport service intent. Recalculate the supported reservation and link bandwidth design before retrying. Correct the RIB-group import/export table membership and verify only the intended route exchange. ExplanationCorrect Answer B:Align route resolution and LSP preference with the documented transport service intent. LDP distributes reachability labels while RSVP-TE can enforce explicit traffic-engineering paths. The selected service resolves over the intended RSVP LSP and follows engineered hops. Incorrect Answers A:Apply the supported LDP and IGP synchronization design and verify staged activation. This addresses a situation in which a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage; however, a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. C:Recalculate the supported reservation and link bandwidth design before retrying. That option concerns an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. The problem here is different: A tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. D:Correct the RIB-group import/export table membership and verify only the intended route exchange. It addresses a different problem: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Here, a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change.
Question 770At fictional Brightstone Backbone 193, a regional service-provider network, during a two-site transit migration, operations observes: A tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. Why is this particular correction the best fit for the stated defect? A prefix SID normally expresses reachability to a node or prefix along the underlying shortest path. LDP distributes reachability labels while RSVP-TE can enforce explicit traffic-engineering paths. MPLS transit forwarding depends on installed label operations at each participating node. RSTP edge-port behavior is intended for ports without downstream bridge participation. ExplanationCorrect Answer B:LDP distributes reachability labels while RSVP-TE can enforce explicit traffic-engineering paths. Align route resolution and LSP preference with the documented transport service intent. The selected service resolves over the intended RSVP LSP and follows engineered hops. Incorrect Answers A:A prefix SID normally expresses reachability to a node or prefix along the underlying shortest path. That relates to circumstances in which a team assumes an SR prefix segment guarantees a strict hop-by-hop explicit path, but traffic follows the current IGP shortest path. Here the problem is that a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. C:MPLS transit forwarding depends on installed label operations at each participating node. The choice would be appropriate if an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. Here, a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change. D:RSTP edge-port behavior is intended for ports without downstream bridge participation. That option concerns a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. The problem here is different: A tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change.