Juniper JN0-364 Practice Test 38 - 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 38

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.

Question 371

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
  2. Bounded remedy: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.
  3. 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.
  4. Bounded remedy: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.

Answer and Explanation

Correct Answer: C

A.

Another proposed action is: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction. That does not directly address the observed condition: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The more targeted correction is: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.

B.

Another proposed action is: Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority. It targets a different dependency; the evidence here is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

C.

Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class. The appropriate response is: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control. Confirm it with: The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.

D.

That alternative concerns: Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy. The relevant evidence is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The corresponding fix is: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.

Question 372

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.
  2. Differentiating observation: MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.
  3. Differentiating observation: 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. Differentiating observation: 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: A

A.

Consider this evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The applicable explanation is: LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class. The matching response is: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.

B.

Another alternative would address MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration as decisive. The actual evidence in this case is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

C.

This other option describes: 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 problem to explain is different: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

D.

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

Question 373

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. Which Junos networking principle best explains the relevant engineering decision?

  1. 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.
  2. Applicable protocol principle: LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class. Evidence for this case: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.
  3. Applicable protocol principle: SR-MPLS needs consistent segment information and forwarding entries coordinated with the underlay IGP. Evidence for this case: 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. Applicable protocol principle: BGP IPv6 route exchange requires compatible activated address families and route policy. Evidence for this case: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.

Answer and Explanation

Correct Answer: B

A.

A different principle is: 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. The present evidence, however, is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The relevant rule is: LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class.

B.

The relevant principle is: LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class. The case evidence is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The practical response is: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.

C.

The competing option invokes: SR-MPLS needs consistent segment information and forwarding entries coordinated with the underlay IGP. Evidence for this case: 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 present evidence is: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The case-relevant principle is: LDP and other MPLS signaling must maintain consistent per-hop label bindings for each forwarding equivalence class.

D.

That principle concerns another fact pattern: BGP IPv6 route exchange requires compatible activated address families and route policy. Evidence for this case: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange. Here the key fact is: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

Question 374

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Intended bounded correction: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.
  2. Independent verification: The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.
  3. Independent verification: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.
  4. Independent verification: LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.

Answer and Explanation

Correct Answer: B

A.

That result would assess another condition: The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems. The correct criterion is directly linked to the finding: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

B.

The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed. This verifies the required result rather than merely stating the action; the original issue was Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

C.

A different option checks: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution. The case-specific acceptance condition is instead the neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.

D.

Passing that test would not establish resolution of the stated issue. The relevant proof is: The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.

Question 375

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer.
  2. Meaningful operational caution: Treating normal PHP as corruption can cause disruptive changes and incorrect data-plane conclusions.
  3. Meaningful operational caution: Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services.
  4. Meaningful operational caution: A reachable IP destination does not prove that the MPLS labeled data path has an active next-hop binding.

Answer and Explanation

Correct Answer: C

A.

Another emphasis concerns: Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer. The current change is Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control; the material limitation is Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services.

B.

This limitation concerns another setting: Treating normal PHP as corruption can cause disruptive changes and incorrect data-plane conclusions. The observed facts here make a different caution decisive: Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services.

C.

The relevant boundary is: Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services. It matters when applying the specific response: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.

D.

Another emphasis concerns: A reachable IP destination does not prove that the MPLS labeled data path has an active next-hop binding. The current change is Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control; the material limitation is Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services.

Question 376

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. 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 penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.
  2. 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.
  3. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge.

Answer and Explanation

Correct Answer: C

A.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The case observation to isolate is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

B.

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: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

C.

The current finding is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. Use it to distinguish the problem from an unrelated symptom.

D.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: RSTP operational detail shows the new attachment advertising superior BPDUs and becoming root instead of the designated provider bridge. The case observation to isolate is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The focused check here is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

Question 377

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. 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 (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.); review and authorize the bounded correction (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.); then independently verify the intended outcome (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.); review and authorize the bounded correction (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.); then independently verify the intended outcome (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.); review and authorize the bounded correction (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.); then independently verify the intended outcome (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.) before production rollout.

Answer and Explanation

Correct Answer: B

A.

Another action-and-check pairing 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 evidence here is Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The required action and proof are Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control and the neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.

B.

The correction is Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control. The matching proof is the neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed. Both address the finding that Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

C.

Another possible combination is: First verify the observed failure (IGP reachability information contains the router identifiers while SR-specific label advertisements or local SID state do not match the expected segment routing configuration.); review and authorize the bounded correction (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.); then independently verify the intended outcome (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.) before production rollout. The current record instead supports Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control, verified by the neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.

D.

Another potential sequence is: First verify the observed failure (Port diagnostics show a BPDU-protection event as the cause of the interface state transition rather than an optical error.); review and authorize the bounded correction (Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.); then independently verify the intended outcome (The approved access segment forwards safely while a repeat unauthorized BPDU test triggers the intended control with an audit trail.) before production rollout. It has no direct link to the distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

Question 378

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. 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 (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.), limited correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.), independently measurable result (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.).
  3. Approval package: observed evidence (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.), limited correction (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.), independently measurable result (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.).
  4. Approval package: observed evidence (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.), limited correction (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.), independently measurable result (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.).

Answer and Explanation

Correct Answer: A

A.

The approval decision should consider Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The specific proposal 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.). Its measurable outcome is: The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.

B.

Another approval action is: Observed evidence (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.), limited correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.), independently measurable result (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.). The relevant evidence and acceptance are Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment and the neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed, respectively.

C.

Another approval package concerns: Observed evidence (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.), limited correction (Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.), independently measurable result (The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.). The present scope must instead be justified by Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

D.

An alternative release decision is: Observed evidence (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.), limited correction (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.), independently measurable result (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.). It does not match the current change: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.

Question 379

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. 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 (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), restore the last approved safe network state and reassess a core change advertises the wrong label to a downstream router.
  2. If testing fails: pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess segment routing node-sid advertisement is present but path is absent.
  3. If testing fails: pause changes, preserve the differentiating evidence (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.), restore the last approved safe network state and reassess mpls label lookup is confused with an ip route table entry.
  4. If testing fails: pause changes, preserve the differentiating evidence (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.), restore the last approved safe network state and reassess mstp instance mapping creates an unexpected blocked path.

Answer and Explanation

Correct Answer: A

A.

If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), restore the last approved safe network state and reassess a core change advertises the wrong label to a downstream router. The case-specific risk is Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services. The original evidence remains: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

B.

Another option proposes: Pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess segment routing node-sid advertisement is present but path is absent. Its assumptions differ from the observed failure; the appropriate recovery is: Pause changes, preserve the differentiating evidence (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), restore the last approved safe network state and reassess a core change advertises the wrong label to a downstream router.

C.

Another fallback concerns pausing changes, preserve the differentiating evidence (The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.), restore the last approved safe network state and reassess mpls label lookup is confused with an ip route table entry. The current change concerns Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

D.

Another recovery route would pause changes, preserve the differentiating evidence (MSTP instance membership and region parameters show the second VLAN mapped into the first spanning-tree instance and mismatched neighboring regional configuration.), restore the last approved safe network state and reassess mstp instance mapping creates an unexpected blocked path. It does not preserve the condition of this case: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. The bounded fallback is: Pause changes, preserve the differentiating evidence (Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.), restore the last approved safe network state and reassess a core change advertises the wrong label to a downstream router.

Question 380

A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. 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.
  2. 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.
  3. Approve only the bounded change (Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.) after independently checking (A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.), without quietly widening the provider or customer network scope.
  4. 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.

Answer and Explanation

Correct Answer: D

A.

An alternative 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 relevant evidence and acceptance are Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment and the neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed, respectively.

B.

Another proposed approval would 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 present scope must instead be justified by Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

C.

A separate release decision would approve only the bounded change (Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.) after independently checking (A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.), without quietly widening the provider or customer network scope. It does not match the current change: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.

D.

The bounded proposal is: 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 separate acceptance measure remains: The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.

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