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 37

Question 360

A BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared. Which post-change observation most strongly confirms the correction?

  1. Closeout evidence: The neighbor table shows the intended level and stable adjacency.
  2. Acceptance check: The selected inet6 route appears on the authorized IPv6 peer.
  3. The test confirms that the IPv6 FIB resolves the intended next hop and a test packet crosses the link.
  4. Expected observation: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

Explanation

Correct Answer

B:

Correct diagnosis: BGP family negotiation and route policy control IPv6 NLRI exchange. The appropriate action is: Enable and verify the intended IPv6 BGP family and export policy. The follow-up evidence required is: The selected inet6 route appears on the authorized IPv6 peer.

Incorrect Answers

A:

This answer would be more suitable when an IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment, where the corrective action is to compare interface level settings and area configuration. 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:

A configured IPv6 static route still depends on reachable forwarding next hops 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.

D:

The proposed principle concerns another network fault: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Here, bGP family negotiation and route policy control IPv6 NLRI exchange. The most direct correction is to enable and verify the intended IPv6 BGP family and export policy, confirmed by the selected inet6 route appears on the authorized IPv6 peer.

Question 361

An EBGP peer drops repeatedly after a firewall change despite clean interface counters. What is the most defensible network engineering correction?

  1. Apply this control: Investigate AS-path loop prevention rather than overriding it without risk review.
  2. Remediation: Compare received LSAs with route selection, area eligibility and next-hop resolution.
  3. Recommended change: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  4. Next step: Restore standard AS-path checks and review any justified exception with design authority.

Explanation

Correct Answer

C:

The critical observation is: BGP sessions require sustained TCP connectivity independent of physical interface health. Correct it by taking this action: Inspect TCP reachability, permitted port 179, and authentication on the transport path. Confirm the outcome with: An authenticated TCP session stays Established after the rule correction.

Incorrect Answers

A:

This response would target a different source scenario: A provider advertises a customer prefix with its own AS number already present in the return AS path. It cannot establish the current acceptance requirement, which is: An authenticated TCP session stays Established after the rule correction. The relevant action is: Inspect TCP reachability, permitted port 179, and authentication on the transport path.

B:

Compare received LSAs with route selection, area eligibility and next-hop resolution is a relevant step for the separate scenario in which an OSPF packet capture shows Link State Updates but the route remains hidden from the active table. It does not directly fix this case. Instead inspect TCP reachability, permitted port 179, and authentication on the transport path; verify: An authenticated TCP session stays Established after the rule correction.

D:

This answer would be more suitable when a provider accepts a route with its own AS in the received path after a risky bypass of loop prevention, where the corrective action is to restore standard AS-path checks and review any justified exception with design authority. The failure here is different: BGP sessions require sustained TCP connectivity independent of physical interface health. Required validation: An authenticated TCP session stays Established after the rule correction.

Question 362

A site complains an IRB gateway answers locally but the downstream VLAN has no remote MAC learning. Which evidence would justify closing this troubleshooting case?

  1. Expected observation: The test frame is accepted only under the approved tagging plan.
  2. Verification result: The fault is visible and surviving members carry traffic within the approved limits.
  3. Closeout evidence: A test host ARPs or discovers its gateway and routes to the intended subnet.
  4. Acceptance check: Both local and remote MACs learn in the intended bridge domain and hosts communicate.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: A working IRB gateway does not validate all L2 paths and trunk members. Remedy: Trace trunk authorization, bridge-domain membership and MAC learning across the path. Proof: Both local and remote MACs learn in the intended bridge domain and hosts communicate.

Incorrect Answers

A:

Customer-facing encapsulation must match the traffic format at ingress describes a neighboring protocol concern. In this case the controlling fact is a working IRB gateway does not validate all L2 paths and trunk members. A correct remediation would trace trunk authorization, bridge-domain membership and MAC learning across the path and demonstrate: Both local and remote MACs learn in the intended bridge domain and hosts communicate.

B:

The proposed principle concerns another network fault: Aggregated links need operational member health monitoring and suitable capacity planning. Here, a working IRB gateway does not validate all L2 paths and trunk members. The most direct correction is to trace trunk authorization, bridge-domain membership and MAC learning across the path, confirmed by both local and remote MACs learn in the intended bridge domain and hosts communicate.

C:

That result would be useful for a different failure, namely: A router-on-a-stick replacement with IRB stops reachability between a bridge domain and an L3 subnet. The current case specifically calls for: Trace trunk authorization, bridge-domain membership and MAC learning across the path. The required observed result is: Both local and remote MACs learn in the intended bridge domain and hosts communicate.

Question 363

A peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. Which technical explanation and controlled action address the symptom?

  1. Root issue: Label-switching errors can occur even when control-plane endpoint reachability is good. Correction: Inspect the incoming label, outgoing label and interface on each affected LSR.
  2. Cause: BGP transport connectivity does not guarantee every address family is negotiated and active. Response: Verify negotiated address families and family-specific routing tables.
  3. Diagnosis: BGP sessions require sustained TCP connectivity independent of physical interface health. Action: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  4. Explanation: iBGP can preserve externally learned next-hop information that internal speakers must resolve. Repair: Review BGP next-hop reachability and explicit next-hop handling.

Explanation

Correct Answer

B:

Underlying cause: BGP transport connectivity does not guarantee every address family is negotiated and active. Corrective action: verify negotiated address families and family-specific routing tables. Verify the outcome: The intended inet6 family receives and selects the IPv6 prefix.

Incorrect Answers

A:

The alternative addresses an ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label, not the present root cause. Here the selected correction must reflect bGP transport connectivity does not guarantee every address family is negotiated and active. Test for: The intended inet6 family receives and selects the IPv6 prefix.

C:

This option overlooks the decisive condition. Its supporting principle is bGP sessions require sustained TCP connectivity independent of physical interface health, while this scenario depends on bGP transport connectivity does not guarantee every address family is negotiated and active. Verify the correction with: The intended inet6 family receives and selects the IPv6 prefix.

D:

iBGP can preserve externally learned next-hop information that internal speakers must resolve describes a neighboring protocol concern. In this case the controlling fact is bGP transport connectivity does not guarantee every address family is negotiated and active. A correct remediation would verify negotiated address families and family-specific routing tables and demonstrate: The intended inet6 family receives and selects the IPv6 prefix.

Question 364

A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. What assessment accurately links the fault to its correction?

  1. Fault mechanism: RSTP can converge faster using explicit roles and handshakes where conditions allow. Remediation: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.
  2. Root issue: Customer-facing encapsulation must match the traffic format at ingress. Correction: Set appropriate port mode and tag handling at the service edge.
  3. Cause: Protective edge-port shutdown is evidence of BPDU policy enforcement. Response: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.
  4. Diagnosis: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Action: Evaluate MSTP instances and explicit VLAN-to-instance mapping.

Explanation

Correct Answer

D:

Correct diagnosis: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. The appropriate action is: Evaluate MSTP instances and explicit VLAN-to-instance mapping. The follow-up evidence required is: Each VLAN maps to its intended instance and designated root.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. The current case specifically calls for: Evaluate MSTP instances and explicit VLAN-to-instance mapping. The required observed result is: Each VLAN maps to its intended instance and designated root.

B:

This response would target a different source scenario: An Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. It cannot establish the current acceptance requirement, which is: Each VLAN maps to its intended instance and designated root. The relevant action is: Evaluate MSTP instances and explicit VLAN-to-instance mapping.

C:

Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards is a relevant step for the separate scenario in which a customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. It does not directly fix this case. Instead evaluate MSTP instances and explicit VLAN-to-instance mapping; verify: Each VLAN maps to its intended instance and designated root.

Question 365

An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. Which protocol behavior most directly determines the correct diagnosis?

  1. The governing rule is: IS-IS routing levels determine topology knowledge and area reachability.
  2. The key distinction is: IS-IS Level 1 adjacency formation depends on common area context.
  3. Protocol behavior: Structured protocol-layer evidence separates link health from routing convergence issues.
  4. Underlying principle: Neighbor discovery can succeed even when database exchange parameters prevent completion.

Explanation

Correct Answer

B:

The case turns on the distinction that iS-IS Level 1 adjacency formation depends on common area context. Apply this concrete engineering step: Verify compatible area membership or use the designed Level 2 boundary. An acceptable verification outcome is: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is iS-IS routing levels determine topology knowledge and area reachability, while this scenario depends on iS-IS Level 1 adjacency formation depends on common area context. Verify the correction with: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

C:

The proposed principle concerns another network fault: Structured protocol-layer evidence separates link health from routing convergence issues. Here, iS-IS Level 1 adjacency formation depends on common area context. The most direct correction is to verify compatible area membership or use the designed Level 2 boundary, confirmed by the intended Level 1 or Level 2 adjacency forms with the expected topology scope.

D:

That result would be useful for a different failure, namely: An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. The current case specifically calls for: Verify compatible area membership or use the designed Level 2 boundary. The required observed result is: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Question 366

An RSVP-signaled LSP enters a failed state after a link bandwidth change. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults.
  2. The governing rule is: Disabling loop prevention can introduce persistent interdomain routing loops.
  3. The key distinction is: RSVP LSP setup can fail resource or path constraints even with valid IP reachability.
  4. Protocol behavior: MPLS forwarding relies on label bindings and compatible next-hop state.

Explanation

Correct Answer

C:

Because rSVP LSP setup can fail resource or path constraints even with valid IP reachability, the best response is to review reservation constraints and available resources rather than resetting all label sessions. A reviewer can close the technical case only after confirming that a compatible bandwidth or path choice allows the target RSVP LSP to establish.

Incorrect Answers

A:

Compare ingress label imposition with transit LFIB and egress disposition is a relevant step for the separate scenario in which one branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. It does not directly fix this case. Instead review reservation constraints and available resources rather than resetting all label sessions; verify: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

B:

The alternative addresses a provider accepts a route with its own AS in the received path after a risky bypass of loop prevention, not the present root cause. Here the selected correction must reflect rSVP LSP setup can fail resource or path constraints even with valid IP reachability. Test for: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

D:

This option overlooks the decisive condition. Its supporting principle is mPLS forwarding relies on label bindings and compatible next-hop state, while this scenario depends on rSVP LSP setup can fail resource or path constraints even with valid IP reachability. Verify the correction with: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

Question 367

An edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. Which statement identifies the key design assumption that failed?

  1. Underlying principle: VRRP provides a master and backup mechanism for a shared virtual default gateway.
  2. Root design issue: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters.
  3. The governing rule is: STP instability can be secondary to physical link churn.
  4. The key distinction is: BPDU protection can prevent rogue switching from affecting a designated edge port.

Explanation

Correct Answer

D:

Underlying cause: BPDU protection can prevent rogue switching from affecting a designated edge port. Corrective action: apply suitable BPDU protection according to edge-port policy. Verify the outcome: A controlled BPDU causes the expected protected-port response.

Incorrect Answers

A:

The proposed principle concerns another network fault: VRRP provides a master and backup mechanism for a shared virtual default gateway. Here, bPDU protection can prevent rogue switching from affecting a designated edge port. The most direct correction is to apply suitable BPDU protection according to edge-port policy, confirmed by a controlled BPDU causes the expected protected-port response.

B:

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: Apply suitable BPDU protection according to edge-port policy. The required observed result is: A controlled BPDU causes the expected protected-port response.

C:

This response would target a different source scenario: An RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. 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.

Question 368

An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. What diagnosis and engineering response are most appropriate?

  1. Root issue: Structured protocol-layer evidence separates link health from routing convergence issues. Correction: Collect protocol adjacency, LSP and routing-table outputs for the affected route.
  2. Cause: Policy placement determines which prefixes influence a routing table or advertisement. Response: Apply and verify supported route policy at the intended routing import or export boundary.
  3. Diagnosis: OSPF route type and LSA scope depend on where routing information originates. Action: Distinguish internal LSAs from externally originated route information.
  4. Explanation: IS-IS Level 1 adjacency formation depends on common area context. Repair: Verify compatible area membership or use the designed Level 2 boundary.

Explanation

Correct Answer

A:

This is the model-intended best choice because structured protocol-layer evidence separates link health from routing convergence issues. The targeted correction is to collect protocol adjacency, LSP and routing-table outputs for the affected route. Validate it by observing that the report explains the fault from interface through neighbor to selected route.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is policy placement determines which prefixes influence a routing table or advertisement, while this scenario depends on structured protocol-layer evidence separates link health from routing convergence issues. Verify the correction with: The report explains the fault from interface through neighbor to selected route.

C:

OSPF route type and LSA scope depend on where routing information originates describes a neighboring protocol concern. In this case the controlling fact is structured protocol-layer evidence separates link health from routing convergence issues. A correct remediation would collect protocol adjacency, LSP and routing-table outputs for the affected route and demonstrate: The report explains the fault from interface through neighbor to selected route.

D:

The proposed principle concerns another network fault: IS-IS Level 1 adjacency formation depends on common area context. 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.

Question 369

An NSR configuration fails commit after an operator adds graceful restart on the same device. What is the most defensible network engineering correction?

  1. Recommended change: Remove the incompatible local mode and validate the supported HA configuration.
  2. Next step: Review session type, supported distributed behavior and switchover-appropriate intervals.
  3. Corrective action: Review VRRP virtual router roles, priority and failover behavior.
  4. Apply this control: Inspect link-state databases and SPF output on affected routers.

Explanation

Correct Answer

A:

Underlying cause: Conflicting local GR and NSR configuration must be resolved before activation. Corrective action: remove the incompatible local mode and validate the supported HA configuration. Verify the outcome: The corrected candidate commits and the Routing Engine synchronization check passes.

Incorrect Answers

B:

Review session type, supported distributed behavior and switchover-appropriate intervals is a relevant step for the separate scenario in which a BFD session flaps during Routing Engine switchover after aggressive timer tuning. It does not directly fix this case. Instead remove the incompatible local mode and validate the supported HA configuration; verify: The corrected candidate commits and the Routing Engine synchronization check passes.

C:

The alternative addresses two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan, 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.

D:

This answer would be more suitable when a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, where the corrective action is to inspect link-state databases and SPF output on affected routers. The failure here is different: Conflicting local GR and NSR configuration must be resolved before activation. Required validation: The corrected candidate commits and the Routing Engine synchronization check passes.

Question 370

A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. What assessment accurately links the fault to its correction?

  1. Explanation: Aggregation can hide individual component failures if advertisement policy is not controlled. Repair: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.
  2. Fault mechanism: Operational route troubleshooting starts with active state and resolution evidence. Remediation: Inspect the configuration, active route state and next-hop reachability before changing preference.
  3. Root issue: OSPF route selection follows each router's synchronized topology view. Correction: Inspect link-state databases and SPF output on affected routers.
  4. Cause: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. Response: Restrict routing-policy matches and validate the import and export boundary.

Explanation

Correct Answer

A:

Because aggregation can hide individual component failures if advertisement policy is not controlled, the best response is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes. A reviewer can close the technical case only after confirming that the summary is advertised only under the approved component-route conditions.

Incorrect Answers

B:

The proposed principle concerns another network fault: Operational route troubleshooting starts with active state and resolution evidence. Here, aggregation can hide individual component failures if advertisement policy is not controlled. The most direct correction is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes, confirmed by the summary is advertised only under the approved component-route conditions.

C:

That result would be useful for a different failure, namely: A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. The current case specifically calls for: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes. The required observed result is: The summary is advertised only under the approved component-route conditions.

D:

This response would target a different source scenario: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. It cannot establish the current acceptance requirement, which is: The summary is advertised only under the approved component-route conditions. The relevant action is: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.

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