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 39
Question 380
A fictional Junos service-provider engineer encounters this scenario: After a maintenance event, a transit router swaps an incoming label to a value not expected by the downstream peer for the same FEC. Distinguishing evidence: Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment. Which bounded approval scope avoids unintended changes to other provider or customer services?
Answer and Explanation
Correct Answer: D
An alternative approval would approve only the bounded change (Inspect supported SR-MPLS advertisement, segment routing global block assumptions and underlay route consistency before changing the planned transport policy.) after independently checking (Node SID and relevant label entries agree across the intended nodes and measured transport follows the computed shortest path.), without quietly widening the provider or customer network scope. The relevant evidence and acceptance are Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment and the neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed, respectively.
Another proposed approval would approve only the bounded change (Use LSP-aware OAM and node label-table checks at the actual affected hop, while retaining separate underlay reachability evidence.) after independently checking (The MPLS-aware path test and customer service probes agree on a working labeled route without masking unresolved transport problems.), without quietly widening the provider or customer network scope. The present scope must instead be justified by Label binding and forwarding entries on adjacent devices show inconsistent outgoing and expected incoming values for the affected path segment.
A separate release decision would approve only the bounded change (Inspect spanning-tree interface states, alternate paths and convergence behavior and tune only supported Layer 2 features within the validated topology.) after independently checking (A link failover test shows stable alternate Layer 2 forwarding without persistent loops and unchanged unrelated BGP routing.), without quietly widening the provider or customer network scope. It does not match the current change: Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.
The bounded proposal is: Approve only the bounded change (Verify label distribution source, FEC identity and session state on adjacent routers, and correct the scoped label protocol fault through normal change control.) after independently checking (The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.), without quietly widening the provider or customer network scope. The separate acceptance measure remains: The neighboring label bindings and forwarding operations agree and both control-plane and data-plane path verification succeed.
Question 381
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 specific bounded Junos routing or switching correction best addresses this service-provider issue?
Answer and Explanation
Correct Answer: A
The issue turns on OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The relevant rule is that OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state. The targeted correction is: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.
Another proposed action is: Verify reachable IPv4 tunnel endpoints, permitted encapsulation and the specific IPv6 routing path before correcting endpoint configuration. It targets a different dependency; the evidence here is OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Another option proposes: Confirm both peers' approved IPv6 unicast family configuration and import/export policies before enabling the specific family. The specific correction is: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope. The deciding evidence is: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
That alternative concerns: Inspect LAG member speed, LACP participation and physical health, then repair or isolate the anomalous member under approved redundancy policy. The relevant evidence is OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The corresponding fix is: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.
Question 382
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. Which observed operational evidence most strongly isolates the actual protocol or forwarding condition?
Answer and Explanation
Correct Answer: D
This other option describes: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The problem to explain is different: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
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 OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Another piece of evidence concerns the route table has the destination IP, but MPLS forwarding-table inspection lacks the expected incoming label operation on the affected transit router. The current incident instead shows: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. This distinction supports the action: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.
The deciding evidence is: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. This distinguishes the problem because OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state. The response it supports is: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.
Question 383
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 Junos networking principle best explains the relevant engineering decision?
Answer and Explanation
Correct Answer: B
The competing option invokes: 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 is: 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 principle is: OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state.
OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state. This distinction accounts for OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope; another unrelated mechanism would not address the same condition.
A different principle is: IPv6-over-IPv4 tunneling relies on functional outer transport and independent inner IPv6 reachability. Evidence for this case: Tunnel interface and IPv4 underlay checks show an obsolete remote endpoint while the IPv6 routes point toward the tunnel logical interface. The present evidence, however, is OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The relevant rule is: OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state.
This alternative invokes: MPLS label-switched path tests diagnose forwarding beyond a generic IP connectivity probe. Evidence for this case: Ordinary ping succeeds, but an MPLS LSP operational probe identifies label-path failure at a middle hop while service traffic drops. The governing distinction for the recorded case is OSPFv3 adjacency and IPv6 route advertisement require appropriate address-family topology and routing state.
Question 384
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. Intended bounded correction: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope. Which independently verifiable test best demonstrates the intended correction worked?
Answer and Explanation
Correct Answer: A
The expected outcome is the advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution. It links the scoped action to the documented condition: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Passing that test would not establish resolution of the stated issue. The relevant proof is: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.
That result would assess another condition: The GRE remote destination resolves through the physical transport interface while desired inner prefixes use the tunnel and probes complete. The correct criterion is directly linked to the finding: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Another proposed result is: IPv6 routes appear only in the authorized routing tables and scoped IPv6 forwarding succeeds without altering existing IPv4 policy. It would not independently establish the required outcome: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.
Question 385
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 material service-availability, routing, switching or security risk most directly needs control?
Answer and Explanation
Correct Answer: C
Another caution is: Link-local IPv6 addresses require interface context; a similar address on a different segment is not the intended peer. The key risk in this case is: IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing.
Another emphasis concerns: Only checking ordinary IPv4 routes can overlook missing swap or pop operations on a labeled path. The current change is Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope; the material limitation is IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing.
The risk to retain is: IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing. The original evidence is OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope; widening the change beyond it is not justified.
Another caution is: An established BGP TCP session does not guarantee every requested network layer address family is negotiated. The key risk in this case is: IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing.
Question 386
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 focused investigation is the most useful before modifying the network configuration?
Answer and Explanation
Correct Answer: A
The pre-change check should 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. That check directly concerns OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Another check would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: The penultimate node advertises implicit-null behavior and forwarding views show a legitimate penultimate-hop-pop operation for the relevant LSP. The case observation to isolate is OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. The focused check here is: 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.
Another investigation would compare active Junos routing, protocol and forwarding displays with this differentiating observed evidence: Session summary is established for the transport, yet address-family negotiation and received route views show no active IPv6 unicast exchange. It does not directly establish the reported condition: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
That check concerns a different signal: 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. The case-relevant check is: 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.
Question 387
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 controlled operational implementation sequence best protects the related provider service?
Answer and Explanation
Correct Answer: C
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 interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope, verified by the advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.
Another potential sequence is: First verify the observed failure (The configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link.); review and authorize the bounded correction (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.); then independently verify the intended outcome (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.) before production rollout. It has no direct link to the distinguishing evidence: 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 evidence indicates: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope. Apply the scoped action: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope. Confirm its effect independently: The advertised customer IPv6 prefix installs in the intended table and a scoped IPv6 path test completes with correct next-hop resolution.
An alternative plan 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 does not test the case-specific condition: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Question 388
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 set of evidence, limited change and independent validation best justifies authorization?
Answer and Explanation
Correct Answer: A
The change-control boundary is: 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 evidence for this scope is OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
An alternative release decision is: Observed evidence (The configured IPv6 link-local next hop exists on multiple segments but operational route resolution references the former interface rather than the active neighbor link.), limited correction (Validate the intended outgoing interface and on-link IPv6 next-hop scope, then correct only the affected static route interface association.), independently measurable result (Neighbor discovery and route displays resolve through the correct active interface and IPv6 service probes work over the approved path.). It does not match the current change: Validate interface family inet6, OSPFv3 topology and policy controlling IPv6 reachability before modifying the relevant scope.
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 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 approval package concerns: 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.), limited correction (Compare reserved path constraints and actual underlay topology, then update the approved explicit route and resource availability before signaling again.), independently measurable result (The RSVP LSP establishes on a feasible approved path and measured forwarding follows its effective label-switched path.). 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.
Question 389
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. If the change fails its expected acceptance test, which controlled recovery approach is most appropriate?
Answer and Explanation
Correct Answer: C
Another fallback concerns pausing 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. The current change concerns OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Another recovery route would 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. It does not preserve the condition of 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 bounded fallback is: 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.
If the change fails acceptance, the bounded recovery is: 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. The case-specific risk is IPv4 route reachability or a single OSPFv3 neighbor state does not establish end-to-end IPv6 prefix routing. The original evidence remains: OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
Another fallback concerns pausing 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 current change concerns OSPFv3 neighbor output is full but route-family-specific database and export inspection show the intended prefix absent from an approved advertisement scope.
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.
Service Provider Routing and Switching, Specialist (JNCIS-SP) (JN0-364) Practice Tests
- Juniper JN0-364 Practice Test 37 - 10 Questions (Last Reviewed 13-Oct-2026)
- 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)