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 50

Question 490

A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. What is the primary routing or switching concept illustrated?

  1. Underlying principle: Configuration intent must be verified against the actual elected spanning-tree root.
  2. Root design issue: Protective edge-port shutdown is evidence of BPDU policy enforcement.
  3. The governing rule is: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters.
  4. The key distinction is: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching.

Explanation

Correct Answer

B:

This is the model-intended best choice because protective edge-port shutdown is evidence of BPDU policy enforcement. The targeted correction is to verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. Validate it by observing that the approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Incorrect Answers

A:

Configuration intent must be verified against the actual elected spanning-tree root describes a neighboring protocol concern. In this case the controlling fact is protective edge-port shutdown is evidence of BPDU policy enforcement. A correct remediation would verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards and demonstrate: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

C:

That result would be useful for a different failure, namely: A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. The current case specifically calls for: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. The required observed result is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

D:

This response would target a different source scenario: A port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. It cannot establish the current acceptance requirement, which is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled. The relevant action is: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.

Question 491

A planned root bridge migration is configured but the operational root remains on the old switch. Which next action best resolves this observed routing or switching failure?

  1. Next step: Apply supported root protection at the appropriate customer-facing boundary.
  2. Corrective action: Enable the appropriate spanning-tree protection and verify the blocked redundant path.
  3. Apply this control: Compare root priority, bridge identifiers and current STP topology status.
  4. Remediation: Align untagged or native VLAN behavior with explicit port configuration.

Explanation

Correct Answer

C:

The selected response implements the principle that configuration intent must be verified against the actual elected spanning-tree root. The engineer should compare root priority, bridge identifiers and current STP topology status. Successful confirmation means: A controlled election yields the approved root with documented path changes.

Incorrect Answers

A:

The alternative addresses a provider STP domain changes root when a customer sends superior BPDUs from an access port, not the present root cause. Here the selected correction must reflect configuration intent must be verified against the actual elected spanning-tree root. Test for: A controlled election yields the approved root with documented path changes.

B:

This answer would be more suitable when a Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected, where the corrective action is to enable the appropriate spanning-tree protection and verify the blocked redundant path. The failure here is different: Configuration intent must be verified against the actual elected spanning-tree root. Required validation: A controlled election yields the approved root with documented path changes.

D:

Untagged frame classification is local to the receiving interface describes a neighboring protocol concern. In this case the controlling fact is configuration intent must be verified against the actual elected spanning-tree root. A correct remediation would compare root priority, bridge identifiers and current STP topology status and demonstrate: A controlled election yields the approved root with documented path changes.

Question 492

Several routers report intermittent OSPF neighbor resets on a saturated transit circuit. Which technical explanation and controlled action address the symptom?

  1. Fault mechanism: IS-IS route dissemination follows hierarchical level boundaries. Remediation: Place the correct L1/L2 boundary and evaluate flooding scope.
  2. Root issue: Routing policy controls which external reachability is injected into OSPF. Correction: Constrain redistribution and test route policy acceptance for the intended prefixes.
  3. Cause: Interarea reachability depends on the ABR's view and allowed advertisements. Response: Inspect ABR area configuration, route export rules and summary policy.
  4. Diagnosis: Protocol timers need reliable packet delivery and should not mask an unstable link. Action: Compare Hello/Dead event logs with loss and interface errors before tuning timers.

Explanation

Correct Answer

D:

Correct diagnosis: Protocol timers need reliable packet delivery and should not mask an unstable link. The appropriate action is: Compare Hello/Dead event logs with loss and interface errors before tuning timers. The follow-up evidence required is: A measured link-quality improvement stabilizes OSPF adjacencies.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. The current case specifically calls for: Compare Hello/Dead event logs with loss and interface errors before tuning timers. The required observed result is: A measured link-quality improvement stabilizes OSPF adjacencies.

B:

This response would target a different source scenario: A provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy. It cannot establish the current acceptance requirement, which is: A measured link-quality improvement stabilizes OSPF adjacencies. The relevant action is: Compare Hello/Dead event logs with loss and interface errors before tuning timers.

C:

Inspect ABR area configuration, route export rules and summary policy is a relevant step for the separate scenario in which an area border router stops advertising an expected summarized interarea route after a policy change. It does not directly fix this case. Instead compare Hello/Dead event logs with loss and interface errors before tuning timers; verify: A measured link-quality improvement stabilizes OSPF adjacencies.

Question 493

A router has an IPv6 default route but no usable next-hop reachability on the egress link. Which post-change observation most strongly confirms the correction?

  1. Closeout evidence: Only authorized customer prefixes enter or leave the decapsulated routing context.
  2. Acceptance check: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.
  3. The test confirms that the intended IPv6 neighbor and destination routes appear and traffic succeeds.
  4. Expected observation: The selected inet6 route appears on the authorized IPv6 peer.

Explanation

Correct Answer

B:

The case turns on the distinction that a configured IPv6 static route still depends on reachable forwarding next hops. Apply this concrete engineering step: Confirm the IPv6 next-hop adjacency and active routing entry. An acceptable verification outcome is: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is encapsulation does not replace explicit customer route filtering and access policy, while this scenario depends on a configured IPv6 static route still depends on reachable forwarding next hops. Verify the correction with: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

C:

The proposed principle concerns another network fault: IPv4 operational success does not prove IPv6 forwarding configuration. Here, a configured IPv6 static route still depends on reachable forwarding next hops. The most direct correction is to confirm the IPv6 next-hop adjacency and active routing entry, confirmed by the IPv6 FIB resolves the intended next hop and a test packet crosses the link.

D:

That result would be useful for a different failure, namely: A BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared. The current case specifically calls for: Confirm the IPv6 next-hop adjacency and active routing entry. The required observed result is: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

Question 494

A provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: Conflicting local GR and NSR configuration must be resolved before activation.
  2. The governing rule is: Protocol timers need reliable packet delivery and should not mask an unstable link.
  3. The key distinction is: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover.
  4. Protocol behavior: NSR and graceful restart on the local restarting device are different approaches and can conflict.

Explanation

Correct Answer

D:

This is the model-intended best choice because nSR and graceful restart on the local restarting device are different approaches and can conflict. The targeted correction is to review supported mutual exclusivity and select the intended HA control-plane method. Validate it by observing that the configuration commits with an approved supported HA combination.

Incorrect Answers

A:

Remove the incompatible local mode and validate the supported HA configuration is a relevant step for the separate scenario in which an NSR configuration fails commit after an operator adds graceful restart on the same device. It does not directly fix this case. Instead review supported mutual exclusivity and select the intended HA control-plane method; verify: The configuration commits with an approved supported HA combination.

B:

The alternative addresses several routers report intermittent OSPF neighbor resets on a saturated transit circuit, not the present root cause. Here the selected correction must reflect nSR and graceful restart on the local restarting device are different approaches and can conflict. Test for: The configuration commits with an approved supported HA combination.

C:

This answer would be more suitable when an Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered, where the corrective action is to evaluate nonstop bridging together with the supported Routing Engine redundancy design. The failure here is different: NSR and graceful restart on the local restarting device are different approaches and can conflict. Required validation: The configuration commits with an approved supported HA combination.

Question 495

An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. Which combined repair and acceptance criterion is strongest?

  1. Action: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Evidence: A link-level packet trace observes the relevant IS-IS PDUs.
  2. Repair: Collect protocol adjacency, LSP and routing-table outputs for the affected route. Check: The report explains the fault from interface through neighbor to selected route.
  3. 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.
  4. Implement: Compare NET area addresses and intended L1 or L2 adjacency mode. Verify: A protocol check shows the authorized level and matching adjacency.

Explanation

Correct Answer

B:

The critical observation is: Structured protocol-layer evidence separates link health from routing convergence issues. Correct it by taking this action: Collect protocol adjacency, LSP and routing-table outputs for the affected route. Confirm the outcome with: The report explains the fault from interface through neighbor to selected route.

Incorrect Answers

A:

The proposed principle concerns another network fault: IS-IS packet exchange and transport differ from OSPF over IP. Here, structured protocol-layer evidence separates link health from routing convergence issues. The most direct correction is to collect protocol adjacency, LSP and routing-table outputs for the affected route, confirmed by the report explains the fault from interface through neighbor to selected route.

C:

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 report explains the fault from interface through neighbor to selected route. The relevant action is: Collect protocol adjacency, LSP and routing-table outputs for the affected route.

D:

Compare NET area addresses and intended L1 or L2 adjacency mode is a relevant step for the separate scenario in which two routers exchange IS-IS Hellos but one rejects the neighbor during area validation. It does not directly fix this case. Instead collect protocol adjacency, LSP and routing-table outputs for the affected route; verify: The report explains the fault from interface through neighbor to selected route.

Question 496

Two BGP paths have different local preferences and a technician expects the shorter AS path always to win. What assessment accurately links the fault to its correction?

  1. Root issue: BGP AS-path information can prevent routes from looping into an AS. Correction: Investigate AS-path loop prevention rather than overriding it without risk review.
  2. Cause: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Response: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  3. Diagnosis: BGP OPEN negotiation includes AS identity that must match peering intent. Action: Confirm the configured local and peer AS values with the authoritative design.
  4. Explanation: BGP best-path selection considers higher-priority decision attributes before AS-path length. Repair: Evaluate routing-policy local preference before later BGP path-selection attributes.

Explanation

Correct Answer

D:

Because bGP best-path selection considers higher-priority decision attributes before AS-path length, the best response is to evaluate routing-policy local preference before later BGP path-selection attributes. A reviewer can close the technical case only after confirming that the intended local preference policy selects the approved egress.

Incorrect Answers

A:

This answer would be more suitable when a provider advertises a customer prefix with its own AS number already present in the return AS path, where the corrective action is to investigate AS-path loop prevention rather than overriding it without risk review. The failure here is different: BGP best-path selection considers higher-priority decision attributes before AS-path length. Required validation: The intended local preference policy selects the approved egress.

B:

This option overlooks the decisive condition. Its supporting principle is end-to-end signaling state alone cannot pinpoint a data-plane label failure, while this scenario depends on bGP best-path selection considers higher-priority decision attributes before AS-path length. Verify the correction with: The intended local preference policy selects the approved egress.

C:

BGP OPEN negotiation includes AS identity that must match peering intent describes a neighboring protocol concern. In this case the controlling fact is bGP best-path selection considers higher-priority decision attributes before AS-path length. A correct remediation would evaluate routing-policy local preference before later BGP path-selection attributes and demonstrate: The intended local preference policy selects the approved egress.

Question 497

An edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: Each VLAN maps to its intended instance and designated root.
  2. The test confirms that a controlled election yields the approved root with documented path changes.
  3. Expected observation: A controlled BPDU causes the expected protected-port response.
  4. Verification result: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

Explanation

Correct Answer

C:

The critical observation is: BPDU protection can prevent rogue switching from affecting a designated edge port. Correct it by taking this action: Apply suitable BPDU protection according to edge-port policy. Confirm the outcome with: A controlled BPDU causes the expected protected-port response.

Incorrect Answers

A:

This response would target a different source scenario: A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. It cannot establish the current acceptance requirement, which is: A controlled BPDU causes the expected protected-port response. The relevant action is: Apply suitable BPDU protection according to edge-port policy.

B:

Compare root priority, bridge identifiers and current STP topology status is a relevant step for the separate scenario in which a planned root bridge migration is configured but the operational root remains on the old switch. It does not directly fix this case. Instead apply suitable BPDU protection according to edge-port policy; verify: A controlled BPDU causes the expected protected-port response.

D:

This answer would be more suitable when a Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly, where the corrective action is to assign distinct service encapsulation and verify edge translation rules. The failure here is different: BPDU protection can prevent rogue switching from affecting a designated edge port. Required validation: A controlled BPDU causes the expected protected-port response.

Question 498

An operator configured an explicit RSVP path through a link that is now administratively down. What should the operations engineer do first to address the stated fault?

  1. Remediation: Distinguish the MPLS shim label stack from the encapsulated payload.
  2. Recommended change: Verify the label action and egress handling for the intended service stack.
  3. Next step: Restrict routing-policy matches and validate the import and export boundary.
  4. Corrective action: Update the engineered path constraints and verify candidate topology availability.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: An LSP cannot follow an unavailable required hop. Remedy: Update the engineered path constraints and verify candidate topology availability. Proof: The backup LSP establishes on a permitted alternate path.

Incorrect Answers

A:

MPLS forwarding typically uses labels to select the next label-switched hop describes a neighboring protocol concern. In this case the controlling fact is an LSP cannot follow an unavailable required hop. A correct remediation would update the engineered path constraints and verify candidate topology availability and demonstrate: The backup LSP establishes on a permitted alternate path.

B:

The proposed principle concerns another network fault: Incorrect label removal can expose payload handling that the egress does not expect. Here, an LSP cannot follow an unavailable required hop. The most direct correction is to update the engineered path constraints and verify candidate topology availability, confirmed by the backup LSP establishes on a permitted alternate path.

C:

That result would be useful for a different failure, namely: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. The current case specifically calls for: Update the engineered path constraints and verify candidate topology availability. The required observed result is: The backup LSP establishes on a permitted alternate path.

Question 499

A BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared. What is the primary routing or switching concept illustrated?

  1. Root design issue: BGP family negotiation and route policy control IPv6 NLRI exchange.
  2. The governing rule is: Tunneling carries one protocol over an underlay that may not route that payload natively.
  3. The key distinction is: IS-IS shortest-path output depends on effective metrics across the route.
  4. Protocol behavior: IPv4 operational success does not prove IPv6 forwarding configuration.

Explanation

Correct Answer

A:

The case turns on the distinction that bGP family negotiation and route policy control IPv6 NLRI exchange. Apply this concrete engineering step: Enable and verify the intended IPv6 BGP family and export policy. An acceptable verification outcome is: The selected inet6 route appears on the authorized IPv6 peer.

Incorrect Answers

B:

This answer would be more suitable when a service provider tunnels IPv6 over an IPv4 core but expects native IPv6 forwarding at every transit hop, where the corrective action is to model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. The failure here is different: BGP family negotiation and route policy control IPv6 NLRI exchange. Required validation: The selected inet6 route appears on the authorized IPv6 peer.

C:

This option overlooks the decisive condition. Its supporting principle is iS-IS shortest-path output depends on effective metrics across the route, while this scenario depends on bGP family negotiation and route policy control IPv6 NLRI exchange. Verify the correction with: The selected inet6 route appears on the authorized IPv6 peer.

D:

IPv4 operational success does not prove IPv6 forwarding configuration describes a neighboring protocol concern. In this case the controlling fact is bGP family negotiation and route policy control IPv6 NLRI exchange. A correct remediation would enable and verify the intended IPv6 BGP family and export policy and demonstrate: The selected inet6 route appears on the authorized IPv6 peer.

Question 500

An NSR configuration fails commit after an operator adds graceful restart on the same device. What observable result most directly verifies the intended configuration?

  1. Expected observation: An authorized switchover maintains bridge control state and service reachability.
  2. Verification result: The fault is visible and surviving members carry traffic within the approved limits.
  3. Closeout evidence: The corrected candidate commits and the Routing Engine synchronization check passes.
  4. Acceptance check: A controlled neighbor check reaches Full after configuration correction.

Explanation

Correct Answer

C:

This is the model-intended best choice because conflicting local GR and NSR configuration must be resolved before activation. The targeted correction is to remove the incompatible local mode and validate the supported HA configuration. Validate it by observing that the corrected candidate commits and the Routing Engine synchronization check passes.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. The current case specifically calls for: Remove the incompatible local mode and validate the supported HA configuration. The required observed result is: The corrected candidate commits and the Routing Engine synchronization check passes.

B:

This response would target a different source scenario: One LAG member fails silently and the service loses capacity even though the logical interface remains active. It cannot establish the current acceptance requirement, which is: The corrected candidate commits and the Routing Engine synchronization check passes. The relevant action is: Remove the incompatible local mode and validate the supported HA configuration.

D:

The alternative addresses a router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link, not the present root cause. Here the selected correction must reflect conflicting local GR and NSR configuration must be resolved before activation. Test for: The corrected candidate commits and the Routing Engine synchronization check passes.

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