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 65

Question 640

A new OSPF uplink remains down at the adjacency stage after a router replacement. What should the operations engineer do first to address the stated fault?

  1. Apply this control: Review each interface's OSPF metric and compare end-to-end computed costs.
  2. Remediation: Compare area, interface mode, timers, authentication and physical status on both endpoints.
  3. Recommended change: Review route preference before considering equivalent forwarding paths.
  4. Next step: Verify compatible network and Hello parameters including mask where applicable.

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 oSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path, where the corrective action is to review each interface's OSPF metric and compare end-to-end computed costs. 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:

Route preference determines the selected route before any multipath decision 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 network-type and Hello compatibility can prevent adjacency 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 641

An IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. Which evidence would justify closing this troubleshooting case?

  1. Expected observation: Each direction's active route matches the documented costs and design.
  2. Verification result: A link-level packet trace observes the relevant IS-IS PDUs.
  3. Closeout evidence: The backup next hop resolves and carries test traffic after the primary link fails.
  4. Acceptance check: Only approved customer prefixes enter the provider's active routing table.

Explanation

Correct Answer

A:

Underlying cause: Common topology information can still produce direction-dependent shortest paths. Corrective action: compare path metrics and each router's route selection before altering LSP state. Verify the outcome: Each direction's active route matches the documented costs and design.

Incorrect Answers

B:

Recognize IS-IS as a link-layer routing protocol with its own PDUs is a relevant step for the separate scenario in which a technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. It does not directly fix this case. Instead compare path metrics and each router's route selection before altering LSP state; verify: Each direction's active route matches the documented costs and design.

C:

The alternative addresses a provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution, not the present root cause. Here the selected correction must reflect common topology information can still produce direction-dependent shortest paths. Test for: Each direction's active route matches the documented costs and design.

D:

This answer would be more suitable when a new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes, where the corrective action is to create explicit import policy and prefix limits aligned to customer contracts. The failure here is different: Common topology information can still produce direction-dependent shortest paths. Required validation: Each direction's active route matches the documented costs and design.

Question 642

A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. What diagnosis and engineering response are most appropriate?

  1. Root issue: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Correction: Verify VLAN or bridge-domain membership and its L3 IRB binding.
  2. Cause: Loop protection can prevent unsafe forwarding when control-plane information is missing. Response: Inspect spanning-tree loop-protection events, root path and link state.
  3. Diagnosis: 802.1Q VLAN identifiers have reserved values and platform constraints. Action: Validate the usable VLAN-ID range and reserved tag values.
  4. Explanation: MAC learning reflects observed source location and may churn during loops or mobility. Repair: Investigate MAC movement, loops and correct bridge-domain membership.

Explanation

Correct Answer

C:

Correct diagnosis: 802.1Q VLAN identifiers have reserved values and platform constraints. The appropriate action is: Validate the usable VLAN-ID range and reserved tag values. The follow-up evidence required is: The service uses a valid supported customer VLAN ID.

Incorrect Answers

A:

Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated describes a neighboring protocol concern. In this case the controlling fact is 802.1Q VLAN identifiers have reserved values and platform constraints. A correct remediation would validate the usable VLAN-ID range and reserved tag values and demonstrate: The service uses a valid supported customer VLAN ID.

B:

The proposed principle concerns another network fault: Loop protection can prevent unsafe forwarding when control-plane information is missing. Here, 802.1Q VLAN identifiers have reserved values and platform constraints. The most direct correction is to validate the usable VLAN-ID range and reserved tag values, confirmed by the service uses a valid supported customer VLAN ID.

D:

This response would target a different source scenario: A carrier receives the same source MAC from two access ports and sees frequent forwarding-table moves. It cannot establish the current acceptance requirement, which is: The service uses a valid supported customer VLAN ID. The relevant action is: Validate the usable VLAN-ID range and reserved tag values.

Question 643

An eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed. Which corrective action and confirmation pair is most appropriate?

  1. Implement: Restore the required transport route and inspect label-signaling and next-hop state. Verify: The transport endpoint again resolves and a labeled probe succeeds.
  2. Control: Investigate AS-path loop prevention rather than overriding it without risk review. Accepted result: The route is accepted only after the AS-path design is corrected.
  3. Action: Compare negotiated timers and protocol logs with routing-engine and packet conditions. Evidence: The restored session remains stable while meeting the approved detection target.
  4. Repair: Separate session liveness from prefix acceptance and RIB installation. Check: Both neighbor state and selected prefix route evidence are verified independently.

Explanation

Correct Answer

D:

The critical observation is: An Established BGP session can exist with zero accepted routes or unusable next hops. Correct it by taking this action: Separate session liveness from prefix acceptance and RIB installation. Confirm the outcome with: Both neighbor state and selected prefix route evidence are verified independently.

Incorrect Answers

A:

The alternative addresses a route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes, not the present root cause. Here the selected correction must reflect an Established BGP session can exist with zero accepted routes or unusable next hops. Test for: Both neighbor state and selected prefix route evidence are verified independently.

B:

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: An Established BGP session can exist with zero accepted routes or unusable next hops. Required validation: Both neighbor state and selected prefix route evidence are verified independently.

C:

This option overlooks the decisive condition. Its supporting principle is aggressive liveness settings can magnify loss or processing delays, while this scenario depends on an Established BGP session can exist with zero accepted routes or unusable next hops. Verify the correction with: Both neighbor state and selected prefix route evidence are verified independently.

Question 644

A GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. Which protocol behavior most directly determines the correct diagnosis?

  1. The governing rule is: Tunnel endpoint parameters must correspond to actual reachable interfaces.
  2. The key distinction is: Label-switching errors can occur even when control-plane endpoint reachability is good.
  3. Protocol behavior: GRE encapsulation overhead can expose MTU blackholes for larger payloads.
  4. Underlying principle: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Tunnel endpoint parameters must correspond to actual reachable interfaces. Remedy: Verify configured tunnel source and destination and their active underlay routing. Proof: The tunnel endpoints pass test traffic after source correction.

Incorrect Answers

B:

This response would target a different source scenario: An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. It cannot establish the current acceptance requirement, which is: The tunnel endpoints pass test traffic after source correction. The relevant action is: Verify configured tunnel source and destination and their active underlay routing.

C:

Test effective MTU and path MTU discovery across the encapsulated route is a relevant step for the separate scenario in which small probes pass through GRE but large customer packets are intermittently dropped. It does not directly fix this case. Instead verify configured tunnel source and destination and their active underlay routing; verify: The tunnel endpoints pass test traffic after source correction.

D:

The alternative addresses an engineer expects a GRE tunnel to preserve the same maximum payload size as a native Ethernet path, not the present root cause. Here the selected correction must reflect tunnel endpoint parameters must correspond to actual reachable interfaces. Test for: The tunnel endpoints pass test traffic after source correction.

Question 645

A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. What diagnosis and engineering response are most appropriate?

  1. Diagnosis: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. Action: Define the intended route-leaking boundary between the customer's instance and the master routing table.
  2. Explanation: A configured static route need not become usable forwarding state when its next hop cannot resolve. Repair: Verify recursive next-hop reachability before relying on the static route.
  3. Fault mechanism: Neighbor state must be traced through transport before modifying route policy. Remediation: Verify IP reachability, routing instance context, TCP transport and session authentication.
  4. Root issue: Small reversible route-policy changes simplify troubleshooting and rollback. Correction: Separate route-selection and lookup-table changes and test each with candidate configuration.

Explanation

Correct Answer

B:

The case turns on the distinction that a configured static route need not become usable forwarding state when its next hop cannot resolve. Apply this concrete engineering step: Verify recursive next-hop reachability before relying on the static route. An acceptable verification outcome is: A route lookup shows an active reachable next hop and traffic reaches the customer.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is routing instances isolate routing tables unless explicit import or export mechanisms connect them, while this scenario depends on a configured static route need not become usable forwarding state when its next hop cannot resolve. Verify the correction with: A route lookup shows an active reachable next hop and traffic reaches the customer.

C:

The proposed principle concerns another network fault: Neighbor state must be traced through transport before modifying route policy. Here, a configured static route need not become usable forwarding state when its next hop cannot resolve. The most direct correction is to verify recursive next-hop reachability before relying on the static route, confirmed by a route lookup shows an active reachable next hop and traffic reaches the customer.

D:

That result would be useful for a different failure, namely: A policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit. The current case specifically calls for: Verify recursive next-hop reachability before relying on the static route. The required observed result is: A route lookup shows an active reachable next hop and traffic reaches the customer.

Question 646

Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. Which change best corrects the failure without losing the intended design?

  1. Corrective action: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  2. Apply this control: Audit aggregate or generated-route contributors and policy conditions.
  3. Remediation: Review route preference before considering equivalent forwarding paths.
  4. Recommended change: Define the intended route-leaking boundary between the customer's instance and the master routing table.

Explanation

Correct Answer

C:

Because route preference determines the selected route before any multipath decision, the best response is to review route preference before considering equivalent forwarding paths. A reviewer can close the technical case only after confirming that the selected path and its preference match the intended backup policy.

Incorrect Answers

A:

Inspect TCP reachability, permitted port 179, and authentication on the transport path is a relevant step for the separate scenario in which an EBGP peer drops repeatedly after a firewall change despite clean interface counters. It does not directly fix this case. Instead review route preference before considering equivalent forwarding paths; verify: The selected path and its preference match the intended backup policy.

B:

The alternative addresses an aggregated customer advertisement persists while all contributing specifics have withdrawn, not the present root cause. Here the selected correction must reflect route preference determines the selected route before any multipath decision. Test for: The selected path and its preference match the intended backup policy.

D:

This option overlooks the decisive condition. Its supporting principle is routing instances isolate routing tables unless explicit import or export mechanisms connect them, while this scenario depends on route preference determines the selected route before any multipath decision. Verify the correction with: The selected path and its preference match the intended backup policy.

Question 647

A switch operator treats the highest bridge ID as the guaranteed STP root. What action-and-test pairing directly resolves the case?

  1. Control: Review root bridge priority and MAC-based bridge identifier comparison. Accepted result: The intended device is root under the tested priorities and tie-breakers.
  2. Action: Inspect interface faults and control-plane events before changing STP timers. Evidence: After fiber repair the port converges and remains in a stable role.
  3. Repair: Review root protection at the provider-facing boundary. Check: A superior BPDU test does not move the approved provider root.
  4. Change: Trace trunk authorization, bridge-domain membership and MAC learning across the path. Test: Both local and remote MACs learn in the intended bridge domain and hosts communicate.

Explanation

Correct Answer

A:

The selected response implements the principle that traditional spanning-tree root election favors the lowest bridge ID. The engineer should review root bridge priority and MAC-based bridge identifier comparison. Successful confirmation means: The intended device is root under the tested priorities and tie-breakers.

Incorrect Answers

B:

That result would be useful for a different failure, namely: An RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. The current case specifically calls for: Review root bridge priority and MAC-based bridge identifier comparison. The required observed result is: The intended device is root under the tested priorities and tie-breakers.

C:

This response would target a different source scenario: A carrier attachment must not allow a customer switch to become the provider's root bridge. It cannot establish the current acceptance requirement, which is: The intended device is root under the tested priorities and tie-breakers. The relevant action is: Review root bridge priority and MAC-based bridge identifier comparison.

D:

Trace trunk authorization, bridge-domain membership and MAC learning across the path is a relevant step for the separate scenario in which a site complains an IRB gateway answers locally but the downstream VLAN has no remote MAC learning. It does not directly fix this case. Instead review root bridge priority and MAC-based bridge identifier comparison; verify: The intended device is root under the tested priorities and tie-breakers.

Question 648

A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. Which post-change observation most strongly confirms the correction?

  1. Acceptance check: Each router is uniquely identified and the link-state database converges.
  2. The test confirms that a controlled neighbor check reaches Full after configuration correction.
  3. Expected observation: When the primary fails the documented backup path is selected without loops.
  4. Verification result: The receiving instance shows the correct route and installed next hop after correction.

Explanation

Correct Answer

B:

Correct diagnosis: OSPF network-type and Hello compatibility can prevent adjacency formation. The appropriate action is: Verify compatible network and Hello parameters including mask where applicable. The follow-up evidence required is: A controlled neighbor check reaches Full after configuration correction.

Incorrect Answers

A:

This answer would be more suitable when two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent, where the corrective action is to assign distinct stable router IDs and clear stale protocol state using an approved procedure. The failure here is different: OSPF network-type and Hello compatibility can prevent adjacency formation. Required validation: A controlled neighbor check reaches Full after configuration correction.

C:

Failover paths are governed by their actual configured metrics describes a neighboring protocol concern. In this case the controlling fact is oSPF network-type and Hello compatibility can prevent adjacency formation. A correct remediation would verify compatible network and Hello parameters including mask where applicable and demonstrate: A controlled neighbor check reaches Full after configuration correction.

D:

The proposed principle concerns another network fault: Imported routes must be validated in the destination lookup context. Here, oSPF network-type and Hello compatibility can prevent adjacency formation. The most direct correction is to verify compatible network and Hello parameters including mask where applicable, confirmed by a controlled neighbor check reaches Full after configuration correction.

Question 649

An engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. Which underlying Junos networking principle explains the failure?

  1. The governing rule is: Dual-stack IS-IS troubleshooting requires family-specific advertisement evidence.
  2. The key distinction is: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers.
  3. Protocol behavior: IPv6 route selection follows prefix matching and route eligibility, not textual address order.
  4. Underlying principle: Tunneling carries one protocol over an underlay that may not route that payload natively.

Explanation

Correct Answer

C:

The critical observation is: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Correct it by taking this action: Apply longest-prefix-match route lookup to the IPv6 destination. Confirm the outcome with: A destination lookup chooses the intended most specific valid route.

Incorrect Answers

A:

This response would target a different source scenario: An IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE. It cannot establish the current acceptance requirement, which is: A destination lookup chooses the intended most specific valid route. The relevant action is: Apply longest-prefix-match route lookup to the IPv6 destination.

B:

Account for outer IP and GRE header overhead in the MTU design is a relevant step for the separate scenario in which an engineer expects a GRE tunnel to preserve the same maximum payload size as a native Ethernet path. It does not directly fix this case. Instead apply longest-prefix-match route lookup to the IPv6 destination; verify: A destination lookup chooses the intended most specific valid route.

D:

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: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Required validation: A destination lookup chooses the intended most specific valid route.

Question 650

A provider switch receives an unknown destination MAC and a new engineer expects it to unicast to a random uplink. Which statement identifies the key design assumption that failed?

  1. Root design issue: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity.
  2. The governing rule is: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching.
  3. The key distinction is: Bridges learn source MAC locations and flood unknown destinations within a permitted domain.
  4. Protocol behavior: Layer 2 bridging does not by itself provide IP intersubnet routing.

Explanation

Correct Answer

C:

Correct diagnosis: Bridges learn source MAC locations and flood unknown destinations within a permitted domain. The appropriate action is: Review MAC learning and unknown-unicast handling within the correct bridge domain. The follow-up evidence required is: A frame trace shows only expected domain members receive the unknown destination.

Incorrect Answers

A:

Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity describes a neighboring protocol concern. In this case the controlling fact is bridges learn source MAC locations and flood unknown destinations within a permitted domain. A correct remediation would review MAC learning and unknown-unicast handling within the correct bridge domain and demonstrate: A frame trace shows only expected domain members receive the unknown destination.

B:

The proposed principle concerns another network fault: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Here, bridges learn source MAC locations and flood unknown destinations within a permitted domain. The most direct correction is to review MAC learning and unknown-unicast handling within the correct bridge domain, confirmed by a frame trace shows only expected domain members receive the unknown destination.

D:

This response would target a different source scenario: A VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain. It cannot establish the current acceptance requirement, which is: A frame trace shows only expected domain members receive the unknown destination. The relevant action is: Review MAC learning and unknown-unicast handling within the correct bridge domain.

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