mcAfee Secure Website
exam =5
exam =6

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

Juniper JN0-364 Questions & Answers

Reliable & Actual Study Materials for JN0-364 Exam Success

69 Questions & Answers with Testing Engine

"JN0-364: Service Provider Routing and Switching, Specialist (JNCIS-SP)" Testing Engine covers all the knowledge points of the real Juniper JN0-364 exam.

The latest actual JN0-364 Questions & Answers from Pass4sure. Everything you need to prepare and get best score at JN0-364 exam easily and quickly.

exam =7
Guarantee

Satisfaction Guaranteed

Pass4sure has a remarkable Juniper Candidate Success record. We're confident of our products and provide no hassle product exchange. That's how confident we are!

99.3% Pass Rate
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 9

Question 80

An RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Implement: Check VRRP group, interface, priority, advertisements and tracking conditions. Verify: The backup assumes master role and clients retain access to the virtual gateway.
  2. Control: Apply supported root protection at the appropriate customer-facing boundary. Accepted result: A superior BPDU test preserves the intended root with a logged protective state.
  3. Action: Enable the appropriate spanning-tree protection and verify the blocked redundant path. Evidence: A topology test leaves one redundant path nonforwarding and traffic remains reachable.
  4. Repair: Inspect interface faults and control-plane events before changing STP timers. Check: After fiber repair the port converges and remains in a stable role.

Explanation

Correct Answer

D:

Because sTP instability can be secondary to physical link churn, the best response is to inspect interface faults and control-plane events before changing STP timers. A reviewer can close the technical case only after confirming that after fiber repair the port converges and remains in a stable role.

Incorrect Answers

A:

This answer would be more suitable when a VRRP backup router does not take over when the primary gateway interface is disabled, where the corrective action is to check VRRP group, interface, priority, advertisements and tracking conditions. The failure here is different: STP instability can be secondary to physical link churn. Required validation: After fiber repair the port converges and remains in a stable role.

B:

This option overlooks the decisive condition. Its supporting principle is customer control traffic must not displace the authorized provider root, while this scenario depends on sTP instability can be secondary to physical link churn. Verify the correction with: After fiber repair the port converges and remains in a stable role.

C:

Spanning tree prevents forwarding loops by selecting a loop-free active topology describes a neighboring protocol concern. In this case the controlling fact is sTP instability can be secondary to physical link churn. A correct remediation would inspect interface faults and control-plane events before changing STP timers and demonstrate: After fiber repair the port converges and remains in a stable role.

Question 81

An OSPF interface is accidentally set passive on a provider edge and its neighbor never appears. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Change: Align the area membership and verify OSPF interface settings on both sides. Test: The peers progress to the expected adjacency state and exchange LSAs.
  2. Implement: Review the passive-interface configuration and required active neighbor links. Verify: The intended backbone neighbor forms and customer-only passive interfaces remain passive.
  3. Control: Review route preference before considering equivalent forwarding paths. Accepted result: The selected path and its preference match the intended backup policy.
  4. Action: Compare received LSAs with route selection, area eligibility and next-hop resolution. Evidence: The routing table exposes the selection reason and the intended route is installed.

Explanation

Correct Answer

B:

The selected response implements the principle that passive OSPF interfaces can advertise networks without forming neighbors on that interface. The engineer should review the passive-interface configuration and required active neighbor links. Successful confirmation means: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Incorrect Answers

A:

This response would target a different source scenario: Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. It cannot establish the current acceptance requirement, which is: The intended backbone neighbor forms and customer-only passive interfaces remain passive. The relevant action is: Review the passive-interface configuration and required active neighbor links.

C:

The alternative addresses two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic, not the present root cause. Here the selected correction must reflect passive OSPF interfaces can advertise networks without forming neighbors on that interface. Test for: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

D:

This answer would be more suitable when an OSPF packet capture shows Link State Updates but the route remains hidden from the active table, where the corrective action is to compare received LSAs with route selection, area eligibility and next-hop resolution. The failure here is different: Passive OSPF interfaces can advertise networks without forming neighbors on that interface. Required validation: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Question 82

Small probes pass through GRE but large customer packets are intermittently dropped. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Test effective MTU and path MTU discovery across the encapsulated route.
  2. Remediation: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport.
  3. Recommended change: Verify reachability between tunnel source and destination addresses.
  4. Next step: Verify instance ownership and route policy at both tunnel endpoints.

Explanation

Correct Answer

A:

Because gRE encapsulation overhead can expose MTU blackholes for larger payloads, the best response is to test effective MTU and path MTU discovery across the encapsulated route. A reviewer can close the technical case only after confirming that a controlled large-payload test succeeds after MTU or MSS adjustment.

Incorrect Answers

B:

The proposed principle concerns another network fault: Tunneling carries one protocol over an underlay that may not route that payload natively. Here, gRE encapsulation overhead can expose MTU blackholes for larger payloads. The most direct correction is to test effective MTU and path MTU discovery across the encapsulated route, confirmed by a controlled large-payload test succeeds after MTU or MSS adjustment.

C:

That result would be useful for a different failure, namely: A GRE design includes a virtual tunnel interface but omits routable IPv4 underlay access to the remote endpoint. The current case specifically calls for: Test effective MTU and path MTU discovery across the encapsulated route. The required observed result is: A controlled large-payload test succeeds after MTU or MSS adjustment.

D:

This response would target a different source scenario: A GRE tunnel is reachable from one routing instance but the remote customer route leaks into a different instance. It cannot establish the current acceptance requirement, which is: A controlled large-payload test succeeds after MTU or MSS adjustment. The relevant action is: Test effective MTU and path MTU discovery across the encapsulated route.

Question 83

A broadcast OSPF segment experiences repeated DR elections after interface priority changes. What implementation step and validation result should be selected?

  1. Action: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Evidence: The test demonstrates loop prevention without advertising false service reachability.
  2. Repair: Review router priorities and the nonpreemptive properties of DR elections. Check: The elected DR and BDR align with the tested election conditions.
  3. Change: Revisit additive path cost and verify SPF outcomes across alternative links. Test: The intended lower-total-cost path wins under steady-state conditions.
  4. Implement: Coordinate authentication parameters and test the key change under maintenance controls. Verify: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Explanation

Correct Answer

B:

Underlying cause: OSPF DR selection depends on eligible routers and the current election event. Corrective action: review router priorities and the nonpreemptive properties of DR elections. Verify the outcome: The elected DR and BDR align with the tested election conditions.

Incorrect Answers

A:

The alternative addresses an engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop, not the present root cause. Here the selected correction must reflect oSPF DR selection depends on eligible routers and the current election event. Test for: The elected DR and BDR align with the tested election conditions.

C:

This option overlooks the decisive condition. Its supporting principle is oSPF normally prefers the least accumulated metric to a destination, while this scenario depends on oSPF DR selection depends on eligible routers and the current election event. Verify the correction with: The elected DR and BDR align with the tested election conditions.

D:

Authentication mismatches can reject otherwise valid OSPF protocol packets describes a neighboring protocol concern. In this case the controlling fact is oSPF DR selection depends on eligible routers and the current election event. A correct remediation would review router priorities and the nonpreemptive properties of DR elections and demonstrate: The elected DR and BDR align with the tested election conditions.

Question 84

An IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. Which statement identifies the key design assumption that failed?

  1. Protocol behavior: Common topology information can still produce direction-dependent shortest paths.
  2. Underlying principle: IS-IS route dissemination follows hierarchical level boundaries.
  3. Root design issue: OSPF broadcast topology reduces unnecessary full adjacency mesh formation.
  4. The governing rule is: Frequent topology churn can stem from physical and configuration issues rather than DIS alone.

Explanation

Correct Answer

D:

Correct diagnosis: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. The appropriate action is: Inspect link quality, interface settings and DIS state before forcing election behavior. The follow-up evidence required is: A stable neighbor and LAN LSP remain after link faults are corrected.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. The current case specifically calls for: Inspect link quality, interface settings and DIS state before forcing election behavior. The required observed result is: A stable neighbor and LAN LSP remain after link faults are corrected.

B:

This response would target a different source scenario: A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. It cannot establish the current acceptance requirement, which is: A stable neighbor and LAN LSP remain after link faults are corrected. The relevant action is: Inspect link quality, interface settings and DIS state before forcing election behavior.

C:

Check the expected DR/BDR versus DROther neighbor-state relationships is a relevant step for the separate scenario in which an engineer assumes both routers must reach Full with every speaker on a broadcast network. It does not directly fix this case. Instead inspect link quality, interface settings and DIS state before forcing election behavior; verify: A stable neighbor and LAN LSP remain after link faults are corrected.

Question 85

A virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed. Which combined repair and acceptance criterion is strongest?

  1. Implement: Review root bridge priority and MAC-based bridge identifier comparison. Verify: The intended device is root under the tested priorities and tie-breakers.
  2. Control: Separate customer bridge domains and validate virtual-switch membership. Accepted result: A cross-customer unknown-unicast probe remains isolated from the other tenant.
  3. Action: Compare candidate and committed configurations and confirm actual bridge membership. Evidence: The active configuration and forwarding table reflect the approved VLAN change.
  4. Repair: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. Check: Separate tagged tests pass in both permitted VLANs.

Explanation

Correct Answer

C:

Underlying cause: Junos candidate configuration changes are not active until committed. Corrective action: compare candidate and committed configurations and confirm actual bridge membership. Verify the outcome: The active configuration and forwarding table reflect the approved VLAN change.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is traditional spanning-tree root election favors the lowest bridge ID, while this scenario depends on junos candidate configuration changes are not active until committed. Verify the correction with: The active configuration and forwarding table reflect the approved VLAN change.

B:

Layer 2 isolation depends on bridge-domain and logical switch boundaries describes a neighboring protocol concern. In this case the controlling fact is junos candidate configuration changes are not active until committed. A correct remediation would compare candidate and committed configurations and confirm actual bridge membership and demonstrate: The active configuration and forwarding table reflect the approved VLAN change.

D:

That result would be useful for a different failure, namely: After a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink. The current case specifically calls for: Compare candidate and committed configurations and confirm actual bridge membership. The required observed result is: The active configuration and forwarding table reflect the approved VLAN change.

Question 86

An LDP binding exists for a remote destination but the forwarding interface points to a failed next hop. What observable result most directly verifies the intended configuration?

  1. Closeout evidence: The selected LDP label uses a live next-hop interface after convergence.
  2. Acceptance check: A packet trace verifies the intended stack at the penultimate and egress hops.
  3. The test confirms that a compatible bandwidth or path choice allows the target RSVP LSP to establish.
  4. Expected observation: Only approved customer prefixes enter the provider's active routing table.

Explanation

Correct Answer

A:

Correct diagnosis: A stale label binding cannot compensate for unusable transport forwarding. The appropriate action is: Compare label bindings with the active IGP next hop and installed forwarding entries. The follow-up evidence required is: The selected LDP label uses a live next-hop interface after convergence.

Incorrect Answers

B:

The alternative addresses a penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label, not the present root cause. Here the selected correction must reflect a stale label binding cannot compensate for unusable transport forwarding. Test for: The selected LDP label uses a live next-hop interface after convergence.

C:

This answer would be more suitable when an RSVP-signaled LSP enters a failed state after a link bandwidth change, where the corrective action is to review reservation constraints and available resources rather than resetting all label sessions. The failure here is different: A stale label binding cannot compensate for unusable transport forwarding. Required validation: The selected LDP label uses a live next-hop interface after convergence.

D:

This option overlooks the decisive condition. Its supporting principle is bGP route acceptance must be constrained rather than inferred from neighbor identity, while this scenario depends on a stale label binding cannot compensate for unusable transport forwarding. Verify the correction with: The selected LDP label uses a live next-hop interface after convergence.

Question 87

A branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. Which post-change observation most strongly confirms the correction?

  1. Verification result: The corrected link reaches stable Full adjacency and exchanges the intended routes.
  2. Closeout evidence: Each router is uniquely identified and the link-state database converges.
  3. Acceptance check: The neighbor table shows the intended level and stable adjacency.
  4. The test confirms that the intended lower-total-cost path wins under steady-state conditions.

Explanation

Correct Answer

D:

Underlying cause: OSPF normally prefers the least accumulated metric to a destination. Corrective action: revisit additive path cost and verify SPF outcomes across alternative links. Verify the outcome: The intended lower-total-cost path wins under steady-state conditions.

Incorrect Answers

A:

The proposed principle concerns another network fault: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Here, oSPF normally prefers the least accumulated metric to a destination. The most direct correction is to revisit additive path cost and verify SPF outcomes across alternative links, confirmed by the intended lower-total-cost path wins under steady-state conditions.

B:

That result would be useful for a different failure, namely: Two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent. The current case specifically calls for: Revisit additive path cost and verify SPF outcomes across alternative links. The required observed result is: The intended lower-total-cost path wins under steady-state conditions.

C:

This response would target a different source scenario: An IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment. It cannot establish the current acceptance requirement, which is: The intended lower-total-cost path wins under steady-state conditions. The relevant action is: Revisit additive path cost and verify SPF outcomes across alternative links.

Question 88

A new OSPF uplink remains down at the adjacency stage after a router replacement. Which underlying Junos networking principle explains the failure?

  1. Underlying principle: Authentication mismatches can reject otherwise valid OSPF protocol packets.
  2. Root design issue: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches.
  3. The governing rule is: Compatible IS-IS levels and area information determine available adjacency types.
  4. The key distinction is: OSPF broadcast topology reduces unnecessary full adjacency mesh formation.

Explanation

Correct Answer

B:

Correct diagnosis: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. The appropriate action is: Compare area, interface mode, timers, authentication and physical status on both endpoints. The follow-up evidence required is: The corrected link reaches stable Full adjacency and exchanges the intended routes.

Incorrect Answers

A:

This answer would be more suitable when a customer edge loses its OSPF neighbor after an authentication key rollover, where the corrective action is to coordinate authentication parameters and test the key change under maintenance controls. The failure here is different: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Required validation: The corrected link reaches stable Full adjacency and exchanges the intended routes.

C:

Compatible IS-IS levels and area information determine available adjacency types describes a neighboring protocol concern. In this case the controlling fact is layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. A correct remediation would compare area, interface mode, timers, authentication and physical status on both endpoints and demonstrate: The corrected link reaches stable Full adjacency and exchanges the intended routes.

D:

The proposed principle concerns another network fault: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. Here, layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. The most direct correction is to compare area, interface mode, timers, authentication and physical status on both endpoints, confirmed by the corrected link reaches stable Full adjacency and exchanges the intended routes.

Question 89

A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. What action-and-test pairing directly resolves the case?

  1. Control: Check import destinations, next-hop resolution and effective routes in every receiving table. Accepted result: The receiving instance shows the correct route and installed next hop after correction.
  2. Action: Review segment identifiers and forwarding under SR-MPLS. Evidence: A test packet follows its segment list through installed SR forwarding.
  3. Repair: Collect hop-local LFIB, label forwarding and interface counters along the LSP. Check: The corrected transit hop forwards the expected incoming label to its planned outgoing label.
  4. Change: Inspect label-switched next-hop resolution separately from generic IP reachability. Test: The labeled service route resolves after the intended LSP is restored.

Explanation

Correct Answer

B:

The selected response implements the principle that sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. The engineer should review segment identifiers and forwarding under SR-MPLS. Successful confirmation means: A test packet follows its segment list through installed SR forwarding.

Incorrect Answers

A:

This response would target a different source scenario: A RIB group leak forwards a VPN service toward the wrong next hop after a route update. It cannot establish the current acceptance requirement, which is: A test packet follows its segment list through installed SR forwarding. The relevant action is: Review segment identifiers and forwarding under SR-MPLS.

C:

The alternative addresses a maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress, not the present root cause. Here the selected correction must reflect sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Test for: A test packet follows its segment list through installed SR forwarding.

D:

This answer would be more suitable when a loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable, where the corrective action is to inspect label-switched next-hop resolution separately from generic IP reachability. The failure here is different: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Required validation: A test packet follows its segment list through installed SR forwarding.

Question 90

A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. Which technical explanation and controlled action address the symptom?

  1. Fault mechanism: Labels are generally meaningful within the forwarding context where they are allocated. Remediation: Explain local label significance and neighbor label binding.
  2. Root issue: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Correction: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  3. Cause: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong. Response: Document the discard behavior and determine whether the aggregate should remain advertised.
  4. Diagnosis: LDP and SR-MPLS may coexist but each needs its own valid label/route state. Action: Check SR label advertisements, segment configuration and installed MPLS forwarding.

Explanation

Correct Answer

B:

This is the model-intended best choice because end-to-end signaling state alone cannot pinpoint a data-plane label failure. The targeted correction is to collect hop-local LFIB, label forwarding and interface counters along the LSP. Validate it by observing that the corrected transit hop forwards the expected incoming label to its planned outgoing label.

Incorrect Answers

A:

Labels are generally meaningful within the forwarding context where they are allocated describes a neighboring protocol concern. In this case the controlling fact is end-to-end signaling state alone cannot pinpoint a data-plane label failure. A correct remediation would collect hop-local LFIB, label forwarding and interface counters along the LSP and demonstrate: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

C:

That result would be useful for a different failure, namely: A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. The current case specifically calls for: Collect hop-local LFIB, label forwarding and interface counters along the LSP. The required observed result is: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

D:

This response would target a different source scenario: A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. It cannot establish the current acceptance requirement, which is: The corrected transit hop forwards the expected incoming label to its planned outgoing label. The relevant action is: Collect hop-local LFIB, label forwarding and interface counters along the LSP.

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