Juniper JN0-364 Practice Test 37 - Prepaway
Practice Exams:

Pass Juniper JN0-364 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers!

30 Days Free Updates, Instant Download!

Verified By Experts
Premium File
$69.99 $76.99

JN0-364 Premium ETE File


  • Premium File 69 Questions & Answers. Last Update: Nov 17, 2026
Whats Included:
  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates

Juniper JN0-364 Practice Test 37

Question 360

A fictional Junos service-provider engineer encounters this scenario: A provider enables SR-MPLS in a core area but newly commissioned router loopbacks are not reachable through the intended shortest-path LSP. Distinguishing evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.) after independently checking (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.) after independently checking (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.) after independently checking (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: C

A.

A separate release decision would approve only the bounded change (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.) after independently checking (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.), without quietly widening the provider or customer network scope. It does not match the current change: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.

B.

An alternative approval would approve only the bounded change (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.) after independently checking (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration and Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path, respectively.

C.

The bounded proposal is: Approve only the bounded change (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.) after independently checking (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.

D.

A separate release decision would approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope. It does not match the current change: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.

Question 361

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.
  2. Bounded remedy: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.
  3. Bounded remedy: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.
  4. Bounded remedy: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

Answer and Explanation

Correct Answer: C

A.

Another proposed action is: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope. That does not directly address the observed condition: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The more targeted correction is: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

B.

Another proposed action is: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control. It targets a different dependency; the evidence here is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

C.

The issue turns on Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The relevant rule is that MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe. The targeted correction is: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

D.

That alternative concerns: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device. The relevant evidence is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The corresponding fix is: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

Question 362

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.
  2. Differentiating observation: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.
  3. Differentiating observation: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.
  4. Differentiating observation: The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.

Answer and Explanation

Correct Answer: A

A.

Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. That fact identifies the relevant dependency, rather than a separate issue. MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe.

B.

Another proposed finding is: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. It is not the recorded discriminator, which is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

C.

Another piece of evidence concerns Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The current incident instead shows: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. This distinction supports the action: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

D.

Another alternative would address the route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router as decisive. The actual evidence in this case is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

Question 363

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. Evidence for this case: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.
  2. Applicable protocol principle: MPLS forwarding uses label-specific information and operations alongside underlying routing resolution. Evidence for this case: The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.
  3. Applicable protocol principle: MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe. Evidence for this case: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.
  4. Applicable protocol principle: RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability. Evidence for this case: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.

Answer and Explanation

Correct Answer: C

A.

The competing option invokes: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. Evidence for this case: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The present evidence is: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The case-relevant principle is: MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe.

B.

That principle concerns another fact pattern: MPLS forwarding uses label-specific information and operations alongside underlying routing resolution. Evidence for this case: The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. Here the key fact is: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

C.

MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe. The recorded evidence is: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The corresponding action is: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

D.

This alternative invokes: RSVP signaling requires feasible path constraints and available resources, distinct from ordinary IP route reachability. Evidence for this case: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop. The governing distinction for the recorded case is MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe.

Question 364

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Intended bounded correction: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.
  2. Independent verification: The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.
  3. Independent verification: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.
  4. Independent verification: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

Answer and Explanation

Correct Answer: B

A.

A different option checks: The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path. The case-specific acceptance condition is instead the MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.

B.

The independent verification condition is: The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems. That result checks whether the original evidence—Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops—has been addressed.

C.

That result would assess another condition: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete. The correct criterion is directly linked to the finding: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

D.

Another proposed result is: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop. It would not independently establish the required outcome: The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.

Question 365

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration.
  2. Meaningful operational caution: Only checking ordinary IPv4 routes can overlook missing swap or pop operations on a labeled path.
  3. Meaningful operational caution: Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic.
  4. Meaningful operational caution: Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services.

Answer and Explanation

Correct Answer: D

A.

This limitation concerns another setting: Unrestricted changes to every bridge priority can create wide reconvergence and uncontrolled root migration. The observed facts here make a different caution decisive: Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services.

B.

Another caution is: Only checking ordinary IPv4 routes can overlook missing swap or pop operations on a labeled path. The key risk in this case is: Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services.

C.

Another emphasis concerns: Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic. The current change is Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence; the material limitation is Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services.

D.

A necessary safeguard is: Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services. The proposed correction remains: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

Question 366

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Which focused investigation is the most useful before modifying the network configuration?

  1. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer.
  3. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

Answer and Explanation

Correct Answer: D

A.

Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. It does not directly establish the reported condition: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

B.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

C.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration. The case observation to isolate is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

D.

The current finding is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Use it to distinguish the problem from an unrelated symptom.

Question 367

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.); review and authorize the bounded correction (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.); then independently verify the intended outcome (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (The configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link.); review and authorize the bounded correction (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.); then independently verify the intended outcome (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.); review and authorize the bounded correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.); then independently verify the intended outcome (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.); review and authorize the bounded correction (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.); then independently verify the intended outcome (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.) before production rollout.

Answer and Explanation

Correct Answer: D

A.

Another possible combination is: First verify the observed failure (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.); review and authorize the bounded correction (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.); then independently verify the intended outcome (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.) before production rollout. The current record instead supports Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence, verified by the MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.

B.

Another potential sequence is: First verify the observed failure (The configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link.); review and authorize the bounded correction (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.); then independently verify the intended outcome (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.) before production rollout. It has no direct link to the distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

C.

Another action-and-check pairing is: First verify the observed failure (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.); review and authorize the bounded correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.); then independently verify the intended outcome (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.) before production rollout. The evidence here is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The required action and proof are Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence and the MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.

D.

The correction is Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence. The matching proof is the MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems. Both address the finding that Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

Question 368

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Which set of evidence, limited change and independent validation best justifies authorization?

  1. Approval package: observed evidence (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), limited correction (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.), independently measurable result (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.).
  2. Approval package: observed evidence (IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.), limited correction (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.), independently measurable result (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.).
  3. Approval package: observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.).
  4. Approval package: observed evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), limited correction (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.), independently measurable result (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.).

Answer and Explanation

Correct Answer: D

A.

Another approval action is: Observed evidence (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), limited correction (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.), independently measurable result (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.). The relevant evidence and acceptance are Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops and the MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems, respectively.

B.

Another approval package concerns: Observed evidence (IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.), limited correction (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.), independently measurable result (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.). The present scope must instead be justified by Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

C.

An alternative release decision is: Observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.). It does not match the current change: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

D.

The bounded proposal is: Observed evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), limited correction (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.), independently measurable result (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.). The separate acceptance measure remains: The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.

Question 369

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?

  1. If testing fails: pause changes, preserve the differentiating evidence (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.), restore the last approved safe network state and reassess ipv6 bgp family activation is omitted on a dual-stack peer.
  2. If testing fails: pause changes, preserve the differentiating evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), restore the last approved safe network state and reassess lsp traceroute yields a different failure boundary than ordinary ping.
  3. If testing fails: pause changes, preserve the differentiating evidence (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.), restore the last approved safe network state and reassess rsvp-signaled lsp does not match its expected traffic-engineering path.
  4. If testing fails: pause changes, preserve the differentiating evidence (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.), restore the last approved safe network state and reassess mpls forwarding stops after an ldp adjacency fails.

Answer and Explanation

Correct Answer: B

A.

Another option proposes: Pause changes, preserve the differentiating evidence (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.), restore the last approved safe network state and reassess ipv6 bgp family activation is omitted on a dual-stack peer. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), restore the last approved safe network state and reassess lsp traceroute yields a different failure boundary than ordinary ping.

B.

If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), restore the last approved safe network state and reassess lsp traceroute yields a different failure boundary than ordinary ping. The case-specific risk is Conflating underlay IP connectivity and labeled LSP health delays recovery of provider services. The original evidence remains: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

C.

Another recovery route would pause changes, preserve the differentiating evidence (RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.), restore the last approved safe network state and reassess rsvp-signaled lsp does not match its expected traffic-engineering path. It does not preserve the condition of this case: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The bounded fallback is: Pause changes, preserve the differentiating evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), restore the last approved safe network state and reassess lsp traceroute yields a different failure boundary than ordinary ping.

D.

Another option proposes: Pause changes, preserve the differentiating evidence (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.), restore the last approved safe network state and reassess mpls forwarding stops after an ldp adjacency fails. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), restore the last approved safe network state and reassess lsp traceroute yields a different failure boundary than ordinary ping.

Question 370

A fictional Junos service-provider engineer encounters this scenario: A core operator relies on a successful source-to-destination IP ping to declare an LDP-signaled path healthy for a private service. Distinguishing evidence: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.) after independently checking (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.) after independently checking (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.) after independently checking (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: A

A.

The change-control boundary is: Approve only the bounded change (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.) after independently checking (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.), without quietly widening the provider or customer network scope. The evidence for this scope is Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

B.

A separate release decision would approve only the bounded change (Validate the configured tunnel source and remote destination against the active underlay address and route, then update the scoped endpoints.) after independently checking (The correct outer source-destination pair appears in captures and inner tunnel routes carry only the intended authorized traffic.), without quietly widening the provider or customer network scope. It does not match the current change: Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.

C.

An alternative approval would approve only the bounded change (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.) after independently checking (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops and the MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems, respectively.

D.

Another proposed approval would approve only the bounded change (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.) after independently checking (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.

Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests