Pass Juniper JN0-364 Exam in First Attempt Guaranteed!
Get 100% Latest Exam Questions, Accurate & Verified Answers!
30 Days Free Updates, Instant Download!
Juniper JN0-364 Practice Test 40
Question 390
A fictional Junos service-provider engineer encounters this scenario: A provider edge forms an OSPFv3 adjacency on a backbone link yet a newly commissioned downstream IPv6 customer prefix is unavailable. Distinguishing evidence: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
A separate release decision would approve only the bounded change (Check supported BFD interval, multiplier, processing and path-loss evidence, then align an achievable detection profile and validate actual loss behavior.) after independently checking (BFD remains stable under representative load and a controlled link failure triggers timely protected-route convergence.), without quietly widening the provider or customer network scope. It does not match the current change: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.
An alternative approval 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. The relevant evidence and acceptance are OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope and the advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution, respectively.
Another proposed approval would 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. The present scope must instead be justified by OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
The approval decision should consider OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The specific proposal is: 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. Its measurable outcome is: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.
Question 391
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. Which specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: B
Another proposed action is: Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family. That does not directly address the observed condition: 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 more targeted correction is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
The evidence 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. The relevant principle is that IPv6 next-hop resolution must respect link-local address scope and actual interface adjacency. The correction is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association. The separate success check is: Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.
Another option proposes: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope. The specific correction is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association. The deciding evidence 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.
That alternative concerns: Check GRES prerequisites, chassis versions and redundancy synchronization before authorizing a controlled Routing Engine switchover. The relevant evidence 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. The corresponding fix is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
Question 392
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: A
Consider this 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 applicable explanation is: IPv6 next-hop resolution must respect link-local address scope and actual interface adjacency. The matching response is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
Another alternative would address Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface as decisive. The actual evidence in this case 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.
This other option describes: Change review shows graceful restart configured but NSR or other high-availability capabilities absent and a test exposes a temporary control-plane adjacency resynchronization. The problem to explain is different: 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.
Another proposed finding is: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange. It is not the recorded discriminator, which 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.
Question 393
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. Which Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
A different principle is: IP tunnels require reachable correctly configured outer endpoints independently of the inner routed service. Evidence for this case: The configured GRE local source address no longer exists on the intended router and captures show no matching encapsulated traffic at the peer. The present evidence, however, 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. The relevant rule is: IPv6 next-hop resolution must respect link-local address scope and actual interface adjacency.
The relevant principle is: IPv6 next-hop resolution must respect link-local address scope and actual interface adjacency. The case evidence 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. The practical response is: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
The competing option invokes: OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state. Evidence for this case: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The present evidence 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. The case-relevant principle is: IPv6 next-hop resolution must respect link-local address scope and actual interface adjacency.
That principle concerns another fact pattern: 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. Here the key fact 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.
Question 394
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Intended bounded correction: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: B
That result would assess another condition: Controlled primary failure and recovery show a predictable gateway master role and preserved host connectivity. The correct criterion is directly linked to the finding: 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.
Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path. This verifies the required result rather than merely stating the action; the original issue was 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.
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 Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.
Passing that test would not establish resolution of the stated issue. The relevant proof is: Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.
Question 395
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. Which material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: B
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: Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer.
A necessary safeguard is: Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer. The proposed correction remains: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
Another emphasis concerns: Ignoring encapsulation overhead can create hard-to-diagnose selective loss despite a nominally up tunnel interface. The current change is Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association; the material limitation is Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer.
This limitation concerns another setting: An established BGP TCP session does not guarantee every requested network layer address family is negotiated. The observed facts here make a different caution decisive: Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer.
Question 396
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. Which focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: D
Another investigation would 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. It does not directly establish the reported condition: 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.
That check concerns a different signal: 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-relevant check is: 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.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design. The case observation to isolate 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. The focused check here is: 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 current 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. The specific pre-change check is: 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. Use it to distinguish the problem from an unrelated symptom.
Question 397
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. Which controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: B
Another action-and-check pairing 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 evidence here 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. The required action and proof are Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association and Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.
The correction is Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association. The matching proof is Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path. Both address the finding that 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.
Another possible combination is: 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. The current record instead supports Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association, verified by Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.
Another potential sequence is: First verify the observed failure (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.); review and authorize the bounded correction (Correct the remote-endpoint underlay route so it remains independent of the GRE inner route, then validate inner and outer forwarding separately.); then independently verify the intended outcome (The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete.) before production rollout. It has no direct link to the distinguishing 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.
Question 398
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. Which set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The bounded proposal 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.). The separate acceptance measure remains: Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.
Another approval package concerns: Observed evidence (Underlay connectivity works and GRE endpoints match, yet packet captures show oversized encapsulated traffic and path MTU feedback being dropped by a filter.), limited correction (Assess encapsulation overhead and actual path MTU, permit needed diagnostics and apply the approved size or MSS treatment without indiscriminately disabling controls.), independently measurable result (Large and small customer test packets pass the tunnel with no fragmentation-related blackholing and filter policy remains appropriately scoped.). The present scope must instead be justified by 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.
An alternative release decision is: Observed evidence (Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface.), limited correction (Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration.), independently measurable result (Encapsulated IPv6 traffic reaches the remote island with expected IPv4 outer endpoints and a tested return route.). It does not match the current change: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
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 configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link and Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path, respectively.
Question 399
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: D
Another option proposes: Pause changes, preserve the differentiating evidence (VRRP state displays show changed effective priorities, interface tracking, or configured preemption behavior that differs from the approved failback design.), restore the last approved safe network state and reassess vrrp backup becomes master after an expected preemption check. Its assumptions differ from the observed failure; the appropriate recovery is: 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.
Another fallback concerns pausing changes, preserve the differentiating evidence (Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange.), restore the last approved safe network state and reassess ipv6 bgp family activation is omitted on a dual-stack peer. The current change concerns 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.
Another recovery route would 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. It does not preserve the condition of 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 bounded fallback is: 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.
A recovery option is to 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. The intended change was Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association, and acceptance must still be judged against Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.
Question 400
A fictional Junos service-provider engineer encounters this scenario: A dual-stack managed customer network loses IPv6 static reachability after its core uplink changes interface numbering. Distinguishing 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. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: 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 configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link.
A separate release decision would 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. It does not match the current change: Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.
An alternative approval would 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 relevant evidence and acceptance are 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 and Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path, respectively.
The change-control boundary is: 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. The evidence for this scope 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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 38 - 10 Questions (Last Reviewed 12-Oct-2026)
- Juniper JN0-364 Practice Test 39 - 10 Questions (Last Reviewed 11-Oct-2026)
- Juniper JN0-364 Practice Test 40 - 10 Questions (Last Reviewed 10-Oct-2026)
- Juniper JN0-364 Practice Test 41 - 10 Questions (Last Reviewed 09-Oct-2026)
- Juniper JN0-364 Practice Test 42 - 10 Questions (Last Reviewed 08-Oct-2026)