Question 730At fictional Harborview ISP 183, a regional service-provider network, during a two-site transit migration, operations observes: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. Which Junos forwarding or control-plane rule applies to this case? Signaled label-switched paths have distinct control-plane establishment and error states. LDP discovery and the TCP-based LDP session depend on usable transport reachability. MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs. ExplanationCorrect Answer A:Signaled label-switched paths have distinct control-plane establishment and error states. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. The failing RSVP hop is identified and the LSP reports Up after correction. Incorrect Answers B:LDP discovery and the TCP-based LDP session depend on usable transport reachability. This could matter when two core routers cannot form an LDP session even though they discover one another on the connected link. In this case, an RSVP LSP stays down but engineers only examine the ingress router's IP default route. C:MPLS forwards labeled packets using label-stack information rather than only the customer IP destination. That could help when operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header; here, an RSVP LSP stays down but engineers only examine the ingress router's IP default route. D:Loop protection guards against unsafe forwarding transitions caused by missing control BPDUs. This is applicable when a blocked redundant link unexpectedly starts forwarding when BPDUs cease on a faulty remote bridge; the present condition is that an RSVP LSP stays down but engineers only examine the ingress router's IP default route.
Question 731At fictional Harborview ISP 183, a regional service-provider network, during a two-site transit migration, operations observes: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. What operational evidence best establishes successful remediation? The target prefix SID resolves to the planned node and the corresponding SR LSP is active. The penultimate and egress forwarding entries match the intended label disposition. The unauthorized prefix is absent and approved transit routes remain usable. The failing RSVP hop is identified and the LSP reports Up after correction. ExplanationCorrect Answer D:The failing RSVP hop is identified and the LSP reports Up after correction. Signaled label-switched paths have distinct control-plane establishment and error states. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. Incorrect Answers A:The target prefix SID resolves to the planned node and the corresponding SR LSP is active. That option concerns a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation. The problem here is different: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. B:The penultimate and egress forwarding entries match the intended label disposition. 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, an RSVP LSP stays down but engineers only examine the ingress router's IP default route. C:The unauthorized prefix is absent and approved transit routes remain usable. This could matter when a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. In this case, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.
Question 732At fictional Harborview ISP 183, a regional service-provider network, during a two-site transit migration, operations observes: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. Which operational harm would persist without the intended correction? MPLS traffic cannot use the planned engineered transport path. Traffic is briefly blackholed during normal network convergence. Packets cannot travel the intended MPLS transport path. An unnoticed bridging loop can trigger widespread broadcast storms. ExplanationCorrect Answer A:MPLS traffic cannot use the planned engineered transport path. Signaled label-switched paths have distinct control-plane establishment and error states. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. Incorrect Answers B:Traffic is briefly blackholed during normal network convergence. That option concerns a new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. The problem here is different: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. 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, an RSVP LSP stays down but engineers only examine the ingress router's IP default route. D:An unnoticed bridging loop can trigger widespread broadcast storms. This could matter when a switch port connecting another bridge is incorrectly marked as an edge port, weakening normal loop-avoidance behavior. In this case, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.
Question 733In a separate fictional JNCIS-SP lab review for Greenbridge ISP 184, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. What should the Junos specialist change first to resolve this specific fault? Recalculate the supported reservation and link bandwidth design before retrying. Restore the intended LSP or safe route resolution and verify the forwarding next hop. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. Check MAC aging and traffic timing before adding disruptive forwarding restrictions. ExplanationCorrect Answer C:Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. The failing RSVP hop is identified and the LSP reports Up after correction. Signaled label-switched paths have distinct control-plane establishment and error states. Incorrect Answers A:Recalculate the supported reservation and link bandwidth design before retrying. This addresses a situation in which an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; however, an RSVP LSP stays down but engineers only examine the ingress router's IP default route. B:Restore the intended LSP or safe route resolution and verify the forwarding next hop. The choice would be appropriate if a service path references an LSP that is down, but its IP route remains visible in the route table. Here, an RSVP LSP stays down but engineers only examine the ingress router's IP default route. D:Check MAC aging and traffic timing before adding disruptive forwarding restrictions. It addresses a different problem: A customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop. Here, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.
Question 734In a separate fictional JNCIS-SP lab review for Greenbridge ISP 184, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. What technical principle underlies the right remedy? Protocol adjacency health does not prove every required MPLS forwarding entry exists. MPLS label forwarding must follow the current resolved transport topology. Signaled label-switched paths have distinct control-plane establishment and error states. Layer 2 bridges select egress ports using MAC/VLAN information before any routed-hop lookup. ExplanationCorrect Answer C:Signaled label-switched paths have distinct control-plane establishment and error states. The failing RSVP hop is identified and the LSP reports Up after correction. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. Incorrect Answers A:Protocol adjacency health does not prove every required MPLS forwarding entry exists. 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 an RSVP LSP stays down but engineers only examine the ingress router's IP default route. B:MPLS label forwarding must follow the current resolved transport topology. This addresses a situation in which after an IGP reconvergence, an old MPLS label still points to a failed interface on one transit device; however, an RSVP LSP stays down but engineers only examine the ingress router's IP default route. D:Layer 2 bridges select egress ports using MAC/VLAN information before any routed-hop lookup. That option concerns an operator adds an IP route to fix traffic that never leaves a local bridge domain because its destination MAC is unknown. The problem here is different: An RSVP LSP stays down but engineers only examine the ingress router's IP default route.
Question 735In a separate fictional JNCIS-SP lab review for Greenbridge ISP 184, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. Which acceptance finding demonstrates the affected service has recovered? The target loopback FEC has a valid binding and corresponding programmed label action. LSP signaling succeeds with compatible reservation values and reported resource state. The failing RSVP hop is identified and the LSP reports Up after correction. The intended distribution bridge is root and access ports show expected roles. ExplanationCorrect Answer C:The failing RSVP hop is identified and the LSP reports Up after correction. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. Signaled label-switched paths have distinct control-plane establishment and error states. Incorrect Answers A:The target loopback FEC has a valid binding and corresponding programmed label action. It is useful for situations where monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback; the reported fault, though, is that an RSVP LSP stays down but engineers only examine the ingress router's IP default route. B:LSP signaling succeeds with compatible reservation values and reported resource state. That relates to circumstances in which an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link. Here the problem is that an RSVP LSP stays down but engineers only examine the ingress router's IP default route. D:The intended distribution bridge is root and access ports show expected roles. The choice would be appropriate if a low-capacity access switch becomes STP root after a new bridge priority setting. Here, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.
Question 736In a separate fictional JNCIS-SP lab review for Greenbridge ISP 184, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: An RSVP LSP stays down but engineers only examine the ingress router's IP default route. What is the direct residual network risk if the fault remains unresolved? MPLS traffic cannot use the planned engineered transport path. A partial label-distribution failure persists without an alert. Transport LSPs are absent despite healthy basic IP routing. Control-plane churn follows repeated elections among unsuitable devices. ExplanationCorrect Answer A:MPLS traffic cannot use the planned engineered transport path. Inspect RSVP signaling errors and hop-level LSP state to isolate the path failure. Signaled label-switched paths have distinct control-plane establishment and error states. Incorrect Answers B:A partial label-distribution failure persists without an alert. It is useful for situations where monitoring checks only LDP adjacency state and never detects missing forwarding labels for a critical PE loopback; the reported fault, though, is that an RSVP LSP stays down but engineers only examine the ingress router's IP default route. C:Transport LSPs are absent despite healthy basic IP routing. That relates to circumstances in which two core routers cannot form an LDP session even though they discover one another on the connected link. Here the problem is that an RSVP LSP stays down but engineers only examine the ingress router's IP default route. D:Control-plane churn follows repeated elections among unsuitable devices. This addresses a situation in which an unplanned access router becomes designated router after its interface receives an unexpectedly high priority; however, an RSVP LSP stays down but engineers only examine the ingress router's IP default route.
Question 737At fictional Fairhaven Broadband 185, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. Which targeted remediation best fits the reported behavior? Align route resolution and LSP preference with the documented transport service intent. Check transit MPLS forwarding state and repair the missing label operation. Correct the SID assignment and confirm the intended segment path resolves to that node. Review DIS selection parameters and verify pseudonode origination for the LAN. ExplanationCorrect Answer B:Check transit MPLS forwarding state and repair the missing label operation. MPLS transit forwarding depends on installed label operations at each participating node. A targeted incoming label maps to the intended outgoing label and interface. Incorrect Answers A:Align route resolution and LSP preference with the documented transport service intent. This could help if a tunnel intended for RSVP engineering instead uses unconstrained LDP forwarding after a route-resolution change, but not when an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. C:Correct the SID assignment and confirm the intended segment path resolves to that node. It is useful for situations where a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation; the reported fault, though, is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. D:Review DIS selection parameters and verify pseudonode origination for the LAN. That relates to circumstances in which operators see two possible LAN-designated routers and assume the wrong one leads routing for the shared segment. Here the problem is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing.
Question 738At fictional Fairhaven Broadband 185, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. Why is this particular correction the best fit for the stated defect? Segment routing uses advertised segment identifiers to steer packets across an MPLS topology. LDP distributes label mappings needed for label-switched forwarding paths. MPLS transit forwarding depends on installed label operations at each participating node. Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS. ExplanationCorrect Answer C:MPLS transit forwarding depends on installed label operations at each participating node. Check transit MPLS forwarding state and repair the missing label operation. A targeted incoming label maps to the intended outgoing label and interface. Incorrect Answers A:Segment routing uses advertised segment identifiers to steer packets across an MPLS topology. It is relevant if a provider uses MPLS segment routing but a node advertises a prefix SID inconsistent with the intended domain allocation, but the reported issue is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. B:LDP distributes label mappings needed for label-switched forwarding paths. This could help if an MPLS service route is reachable at IP level but its LDP label binding is missing on one hop, but not when an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. D:Route policy controls which eligible nonnative prefixes are intentionally originated into IS-IS. It is useful for situations where a customer service route never reaches another IS-IS area because the required export policy omits it; the reported fault, though, is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing.
Question 739At fictional Fairhaven Broadband 185, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. What direct observation would prove the corrective action worked? A targeted incoming label maps to the intended outgoing label and interface. The failing RSVP hop is identified and the LSP reports Up after correction. The RSVP LSP is up with the intended transit hop sequence. The affected VLAN has the desired root and its forwarding path recovers. ExplanationCorrect Answer A:A targeted incoming label maps to the intended outgoing label and interface. MPLS transit forwarding depends on installed label operations at each participating node. Check transit MPLS forwarding state and repair the missing label operation. Incorrect Answers B:The failing RSVP hop is identified and the LSP reports Up after correction. It is relevant if an RSVP LSP stays down but engineers only examine the ingress router's IP default route, but the reported issue is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. C:The RSVP LSP is up with the intended transit hop sequence. This could help if an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route, but not when an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. D:The affected VLAN has the desired root and its forwarding path recovers. This relates to a case where one VLAN becomes unavailable after administrators assume the same spanning-tree root applies identically to all VLANs; the current situation is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing.
Question 740At fictional Fairhaven Broadband 185, a regional service-provider network, during a preproduction design validation, operations observes: An MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. Which failure consequence follows most closely from ignoring this issue? A correct label stack is broken by applying the wrong role assumption. The engineered service remains unavailable or overcommits transit capacity. Half the expected capacity is unavailable and link failover is fragile. Labeled packets are discarded at the affected core node. ExplanationCorrect Answer D:Labeled packets are discarded at the affected core node. MPLS transit forwarding depends on installed label operations at each participating node. Check transit MPLS forwarding state and repair the missing label operation. Incorrect Answers A:A correct label stack is broken by applying the wrong role assumption. That could help when a network test expects the ingress PE to swap a label that it should actually impose; here, an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. B:The engineered service remains unavailable or overcommits transit capacity. This is applicable when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; the present condition is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing. C:Half the expected capacity is unavailable and link failover is fragile. It is relevant if a bundled uplink has two configured members but only one is usable because the second member's operational parameters differ, but the reported issue is that an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing.