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

Question 340

A fictional Junos service-provider engineer encounters this scenario: A backbone operator sees an active inet destination route and concludes an MPLS traffic-engineered flow is working although customer packets stop at an intermediate hop. Distinguishing evidence: The route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.) after independently checking (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.) after independently checking (Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.), without quietly widening the provider or customer network scope.
  3. 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.
  4. 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.

Answer and Explanation

Correct Answer: C

A.

Another proposed approval would approve only the bounded change (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.) after independently checking (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.), without quietly widening the provider or customer network scope. The present scope must instead be justified by the route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.

B.

A separate release decision would approve only the bounded change (Confirm the authorized MSTP region, instance mappings and topology design, then align the relevant VLAN-to-instance definitions across participants.) after independently checking (Per-instance operational port states match approved paths and both service VLAN groups retain loop-free reachability during a controlled link failure.), without quietly widening the provider or customer network scope. It does not match the current change: Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.

C.

The approval decision should consider the route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. The specific proposal is: 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. Its measurable outcome is: The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.

D.

Another proposed 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 present scope must instead be justified by the route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router.

Question 341

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop.
  2. Bounded remedy: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.
  3. Bounded remedy: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes.
  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: D

A.

Another proposed action is: Inspect the label forwarding information base, push-swap-pop behavior and corresponding tunnel state on each relevant hop. That does not directly address the observed condition: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The more targeted correction is: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

B.

Another proposed action is: Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction. It targets a different dependency; the evidence here is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

C.

Another option proposes: Validate whether the port must be a genuine edge-facing endpoint and preserve or redesign BPDU protection under approved topology changes. The specific correction is: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device. The deciding evidence is: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

D.

The evidence is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The relevant principle is that MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding. The correction is: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device. The separate success check is: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

Question 342

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: 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.
  2. Differentiating observation: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.
  3. Differentiating observation: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.
  4. Differentiating observation: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.

Answer and Explanation

Correct Answer: C

A.

This other option describes: 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. The problem to explain is different: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

B.

Another proposed finding is: The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped. It is not the recorded discriminator, which is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

C.

Consider this evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The applicable explanation is: MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding. The matching response is: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

D.

Another alternative would address Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment as decisive. The actual evidence in this case is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

Question 343

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. Which Junos networking principle best explains the relevant engineering decision?

  1. 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.
  2. 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.
  3. Applicable protocol principle: MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding. Evidence for this case: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.
  4. Applicable protocol principle: GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling. Evidence for this case: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.

Answer and Explanation

Correct Answer: C

A.

The competing option 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 present evidence is: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The case-relevant principle is: MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding.

B.

That principle concerns another fact pattern: 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. Here the key fact is: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

C.

MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding. The recorded evidence is: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The corresponding action is: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

D.

This alternative invokes: GRE encapsulation adds overhead and must be validated against underlay MTU and packet handling. Evidence for this case: Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter. The governing distinction for the recorded case is MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding.

Question 344

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Intended bounded correction: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP.
  2. Independent verification: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.
  3. Independent verification: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.
  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: C

A.

A different option checks: The expected label entry and forwarding action appear at the designated hop and end-to-end customer traffic crosses the intended LSP. The case-specific acceptance condition is instead Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

B.

Passing that test would not establish resolution of the stated issue. The relevant proof is: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

C.

Confirm the correction by demonstrating: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop. This directly tests the intended change, Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

D.

Another proposed result is: LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP. It would not independently establish the required outcome: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

Question 345

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation.
  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: Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic.

Answer and Explanation

Correct Answer: B

A.

Another emphasis concerns: Blindly disabling BPDU protection on an untrusted edge can open the switching domain to loops and root manipulation. The current change is Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device; the material limitation is Treating normal PHP as corruption can cause disruptive changes and incorrect data-plane conclusions.

B.

Treating normal PHP as corruption can cause disruptive changes and incorrect data-plane conclusions. That boundary protects the documented change, Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device, from introducing an unrelated problem.

C.

Another caution is: Manually assigning arbitrary transport label values can conflict with dynamic label allocation and other customers' services. The key risk in this case is: Treating normal PHP as corruption can cause disruptive changes and incorrect data-plane conclusions.

D.

Another emphasis concerns: Relaxing all RSVP admission constraints can displace other bandwidth-reserved customer traffic. The current change is Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device; the material limitation is Treating normal PHP as corruption can cause disruptive changes and incorrect data-plane conclusions.

Question 346

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. 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: RSVP session state and explicit path display show an outdated strict hop, while IGP reachability has already moved to a different core next hop.
  2. 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.
  3. 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.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.

Answer and Explanation

Correct Answer: C

A.

Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed 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. The case observation to isolate is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The focused check here is: 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.

B.

Another investigation would 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. It does not directly establish the reported condition: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

C.

The current finding is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The specific pre-change check is: 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. 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: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The case observation to isolate is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The focused check here is: 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.

Question 347

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.); review and authorize the bounded correction (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.); then independently verify the intended outcome (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.) before production rollout.
  2. 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.
  3. 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.
  4. 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.

Answer and Explanation

Correct Answer: A

A.

MPLS label stack handling may include penultimate-hop popping as part of legitimate forwarding. For this issue, the appropriate bounded intervention is: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device. The acceptance test is: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

B.

Another potential sequence 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. It has no direct link to the distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

C.

Another action-and-check pairing 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. The evidence here is the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The required action and proof are Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device and Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

D.

An alternative plan is: 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. It does not test the case-specific condition: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

Question 348

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. 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 (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.), limited correction (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.), independently measurable result (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.).
  3. Approval package: observed evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), limited correction (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.), independently measurable result (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.).
  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: C

A.

An alternative release decision 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.). It does not match the current change: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

B.

Another approval action is: Observed evidence (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.), limited correction (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.), independently measurable result (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.). The relevant evidence and acceptance are the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP and Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop, respectively.

C.

The bounded proposal is: Observed evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), limited correction (Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.), independently measurable result (Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.). The separate acceptance measure remains: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

D.

An alternative release decision 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.). It does not match the current change: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

Question 349

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. 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 (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.
  2. If testing fails: pause changes, preserve the differentiating evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), restore the last approved safe network state and reassess php behavior makes a packet appear unlabeled before the destination.
  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 (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), restore the last approved safe network state and reassess gre tunnel reports up but payload mtu is too large.

Answer and Explanation

Correct Answer: B

A.

Another recovery route would 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. It does not preserve the condition of this case: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The bounded fallback is: Pause changes, preserve the differentiating evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), restore the last approved safe network state and reassess php behavior makes a packet appear unlabeled before the destination.

B.

A contingency plan would pause changes, preserve the differentiating evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), restore the last approved safe network state and reassess php behavior makes a packet appear unlabeled before the destination. This preserves control of the change linked to the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

C.

Another fallback concerns pausing 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. The current change concerns the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.

D.

Another recovery route would pause changes, preserve the differentiating evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), restore the last approved safe network state and reassess gre tunnel reports up but payload mtu is too large. It does not preserve the condition of this case: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The bounded fallback is: Pause changes, preserve the differentiating evidence (The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP.), restore the last approved safe network state and reassess php behavior makes a packet appear unlabeled before the destination.

Question 350

A fictional Junos service-provider engineer encounters this scenario: An engineer reports an MPLS failure because a capture on the final transit interface shows IP rather than an expected nonbottom service label. Distinguishing evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.) after independently checking (The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.), without quietly widening the provider or customer network scope.
  2. 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.
  3. 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.
  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: B

A.

An alternative approval would approve only the bounded change (Verify the intended root and edge-port topology, then apply supported root protection on the authorized boundary and restore correct bridge priority.) after independently checking (The provider bridge remains legitimate root and a controlled superior-BPDU test is contained without permanent loop formation.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP and Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop, respectively.

B.

The approval decision should consider the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The specific proposal is: 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. Its measurable outcome is: Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop.

C.

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: Confirm expected label advertisement and pop operation at the penultimate hop rather than forcing unnecessary labels through every device.

D.

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 the penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP and Captured traffic and destination forwarding demonstrate correct reachability with expected label disposition at each hop, respectively.

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