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

Question 410

A fictional Junos service-provider engineer encounters this scenario: Two service-provider BGP neighbors have an established IPv4 session but the newly requested IPv6 prefixes never enter the expected inet6 routing table. Distinguishing evidence: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.) after independently checking (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.) after independently checking (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.) after independently checking (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: A

A.

The bounded proposal is: Approve only the bounded change (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.) after independently checking (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.

B.

Another proposed approval would approve only the bounded change (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.) after independently checking (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.

C.

A separate release decision would approve only the bounded change (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.) after independently checking (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.), without quietly widening the provider or customer network scope. It does not match the current change: Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.

D.

An alternative approval would approve only the bounded change (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.) after independently checking (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange and IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy, respectively.

Question 411

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?

  1. Bounded remedy: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
  2. Bounded remedy: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.
  3. Bounded remedy: Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy.
  4. Bounded remedy: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.

Answer and Explanation

Correct Answer: B

A.

Another proposed action is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association. That does not directly address the observed condition: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The more targeted correction is: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.

B.

The observed condition is: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. This calls for the scoped change: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration. The acceptance measure is: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

C.

Another option proposes: Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy. The specific correction is: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration. The deciding evidence is: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

D.

That alternative concerns: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope. The relevant evidence is Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The corresponding fix is: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.

Question 412

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?

  1. Differentiating observation: High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed.
  2. Differentiating observation: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.
  3. Differentiating observation: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.
  4. 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.

Answer and Explanation

Correct Answer: B

A.

Another piece of evidence concerns High-availability operational output shows graceful Routing Engine switchover not ready and state synchronization warnings despite both engines being installed. The current incident instead shows: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. This distinction supports the action: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.

B.

The deciding evidence is: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. This distinguishes the problem because IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. The response it supports is: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.

C.

This other option describes: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange. The problem to explain is different: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

D.

Another proposed finding is: 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. It is not the recorded discriminator, which is Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

Question 413

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Which Junos networking principle best explains the relevant engineering decision?

  1. Applicable protocol principle: IPv6 next-hop resolution must respect link-local address scope and actual interface adjacency. Evidence for this case: 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. 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.
  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: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. Evidence for this case: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

Answer and Explanation

Correct Answer: D

A.

A different principle is: IPv6 next-hop resolution must respect link-local address scope and actual interface adjacency. Evidence for this case: 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 present evidence, however, is Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The relevant rule is: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability.

B.

This alternative invokes: 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. The governing distinction for the recorded case is IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability.

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: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The case-relevant principle is: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability.

D.

IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. This distinction accounts for Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface; another unrelated mechanism would not address the same condition.

Question 414

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Intended bounded correction: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration. Which independently verifiable test best demonstrates the intended correction worked?

  1. Independent verification: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.
  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: IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.
  4. Independent verification: Redundancy status becomes ready and the approved test preserves operational interface state within documented continuity targets.

Answer and Explanation

Correct Answer: A

A.

Confirm the correction by demonstrating: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route. This directly tests the intended change, Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.

B.

Another proposed result is: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution. It would not independently establish the required outcome: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

C.

A different option checks: IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy. The case-specific acceptance condition is instead Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

D.

Passing that test would not establish resolution of the stated issue. The relevant proof is: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

Question 415

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Which material service-availability, routing, switching or security risk most directly needs control?

  1. Meaningful operational caution: A valid IGP route alone is not proof that an SR-MPLS data plane is programmed consistently across the area.
  2. Meaningful operational caution: Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer.
  3. Meaningful operational caution: IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing.
  4. Meaningful operational caution: Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint.

Answer and Explanation

Correct Answer: D

A.

Another caution is: A valid IGP route alone is not proof that an SR-MPLS data plane is programmed consistently across the area. The key risk in this case is: Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint.

B.

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 reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration; the material limitation is Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint.

C.

This limitation concerns another setting: IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing. The observed facts here make a different caution decisive: Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint.

D.

Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint. That boundary protects the documented change, Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration, from introducing an unrelated problem.

Question 416

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. 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 route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing.
  2. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.
  3. 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.
  4. Focused Junos investigation: Compare active Junos routing, protocol and forwarding displays with this differentiating 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.

Answer and Explanation

Correct Answer: B

A.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The route to the GRE remote destination shows the tunnel itself as next hop instead of an ordinary physical underlay path, and decapsulation counters stop increasing. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

B.

The current finding is Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The specific pre-change check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Use it to distinguish the problem from an unrelated symptom.

C.

Another investigation 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. It does not directly establish the reported condition: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

D.

That check concerns a different signal: Compare active Junos routing, protocol and forwarding displays with this differentiating 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. The case-relevant check is: Compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

Question 417

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Which controlled operational implementation sequence best protects the related provider service?

  1. Controlled engineering sequence: First verify the observed failure (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.); review and authorize the bounded correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.); then independently verify the intended outcome (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.) before production rollout.
  2. Controlled engineering sequence: First verify the observed failure (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.); review and authorize the bounded correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.); then independently verify the intended outcome (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.) before production rollout.
  3. Controlled engineering sequence: First verify the observed failure (OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.); review and authorize the bounded correction (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.); then independently verify the intended outcome (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.) before production rollout.
  4. Controlled engineering sequence: First verify the observed failure (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.); review and authorize the bounded correction (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.); then independently verify the intended outcome (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.) before production rollout.

Answer and Explanation

Correct Answer: B

A.

Another action-and-check pairing is: First verify the observed failure (The underlay IP route remains present but the affected next hop lacks an expected LDP label binding and LDP adjacency has dropped.); review and authorize the bounded correction (Check LDP session transport, adjacency and matching labeled next hops before choosing a narrow protocol or underlay correction.); then independently verify the intended outcome (LDP neighbors and label bindings recover for the intended FEC and payload forwarding resumes over the authorized LSP.) before production rollout. The evidence here is Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The required action and proof are Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration and Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

B.

The correction is Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration. The matching proof is Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route. Both address the finding that Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

C.

Another possible combination is: First verify the observed failure (OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.); review and authorize the bounded correction (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.); then independently verify the intended outcome (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.) before production rollout. The current record instead supports Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration, verified by Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

D.

Another potential sequence is: First verify the observed failure (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.); review and authorize the bounded correction (Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family.); then independently verify the intended outcome (IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy.) before production rollout. It has no direct link to the distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

Question 418

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Which set of evidence, limited change and independent validation best justifies authorization?

  1. 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.).
  2. Approval package: observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.).
  3. 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.).
  4. Approval package: 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.), limited correction (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.), independently measurable result (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.).

Answer and Explanation

Correct Answer: B

A.

Another approval package concerns: 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.). The present scope must instead be justified by Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

B.

The bounded proposal is: Observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.). The separate acceptance measure remains: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

C.

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 Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface and Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route, respectively.

D.

Another approval package concerns: 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.), limited correction (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.), independently measurable result (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.). The present scope must instead be justified by Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

Question 419

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. 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 (OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.), restore the last approved safe network state and reassess ospfv3 adjacency is healthy but destination ipv6 route is missing.
  2. If testing fails: pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess ipv6 static route selects a link-local next hop on the wrong interface.
  3. If testing fails: pause changes, preserve the differentiating evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), restore the last approved safe network state and reassess ipv6-over-ipv4 tunnel has return path but wrong encapsulation endpoint.
  4. 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.

Answer and Explanation

Correct Answer: C

A.

Another fallback concerns pausing changes, preserve the differentiating evidence (OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.), restore the last approved safe network state and reassess ospfv3 adjacency is healthy but destination ipv6 route is missing. The current change concerns Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

B.

Another recovery route would pause changes, preserve the differentiating 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.), restore the last approved safe network state and reassess ipv6 static route selects a link-local next hop on the wrong interface. It does not preserve the condition of this case: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The bounded fallback is: Pause changes, preserve the differentiating evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), restore the last approved safe network state and reassess ipv6-over-ipv4 tunnel has return path but wrong encapsulation endpoint.

C.

If the change fails acceptance, the bounded recovery is: Pause changes, preserve the differentiating evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), restore the last approved safe network state and reassess ipv6-over-ipv4 tunnel has return path but wrong encapsulation endpoint. The case-specific risk is Changing IPv6 routes alone cannot repair an unreachable outer IPv4 encapsulation endpoint. The original evidence remains: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

D.

Another fallback concerns pausing changes, preserve the differentiating evidence (Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops.), restore the last approved safe network state and reassess lsp traceroute yields a different failure boundary than ordinary ping. The current change concerns Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

Question 420

A fictional Junos service-provider engineer encounters this scenario: A provider supports an IPv6 island across an IPv4-only core, but the tunnel fails after one IPv4 transport endpoint is renumbered. Distinguishing evidence: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. Which bounded approval scope avoids unintended changes to other provider or customer services?

  1. Approve only the bounded change (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.) after independently checking (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.), without quietly widening the provider or customer network scope.
  2. Approve only the bounded change (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.) after independently checking (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.), without quietly widening the provider or customer network scope.
  3. Approve only the bounded change (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.) after independently checking (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.), without quietly widening the provider or customer network scope.
  4. Approve only the bounded change (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.) after independently checking (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.), without quietly widening the provider or customer network scope.

Answer and Explanation

Correct Answer: A

A.

The approval decision should consider Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The specific proposal is: Approve only the bounded change (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.) after independently checking (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.), without quietly widening the provider or customer network scope. Its measurable outcome is: Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.

B.

An alternative approval would approve only the bounded change (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.) after independently checking (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface and Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route, respectively.

C.

Another proposed approval would approve only the bounded change (Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.) after independently checking (The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.

D.

A separate release decision would approve only the bounded change (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.) after independently checking (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.), without quietly widening the provider or customer network scope. It does not match the current change: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.

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