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 59

Question 580

A provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Implement: Review route preference before considering equivalent forwarding paths. Verify: The selected path and its preference match the intended backup policy.
  2. 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.
  3. Action: Verify IP reachability, routing instance context, TCP transport and session authentication. Evidence: The TCP peering session reaches Established and remains stable.
  4. Repair: Define the intended route-leaking boundary between the customer's instance and the master routing table. Check: Each customer route is visible only in the tables approved by the design.

Explanation

Correct Answer

D:

Correct diagnosis: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. The appropriate action is: Define the intended route-leaking boundary between the customer's instance and the master routing table. The follow-up evidence required is: Each customer route is visible only in the tables approved by the design.

Incorrect Answers

A:

That result would be useful for a different failure, namely: Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. The current case specifically calls for: Define the intended route-leaking boundary between the customer's instance and the master routing table. The required observed result is: Each customer route is visible only in the tables approved by the design.

B:

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: Each customer route is visible only in the tables approved by the design. The relevant action is: Define the intended route-leaking boundary between the customer's instance and the master routing table.

C:

Verify IP reachability, routing instance context, TCP transport and session authentication is a relevant step for the separate scenario in which a BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It does not directly fix this case. Instead define the intended route-leaking boundary between the customer's instance and the master routing table; verify: Each customer route is visible only in the tables approved by the design.

Question 581

A Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart. What observable result most directly verifies the intended configuration?

  1. Closeout evidence: A controlled election yields the approved root with documented path changes.
  2. Acceptance check: A planned switchover test documents forwarding and neighbor behavior against the HA design.
  3. The test confirms that a controlled forwarding failure is detected within the approved target.
  4. Expected observation: The fault is visible and surviving members carry traffic within the approved limits.

Explanation

Correct Answer

B:

The case turns on the distinction that forwarding-plane continuity does not prove control-plane routing continuity. Apply this concrete engineering step: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. An acceptable verification outcome is: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is configuration intent must be verified against the actual elected spanning-tree root, while this scenario depends on forwarding-plane continuity does not prove control-plane routing continuity. Verify the correction with: A planned switchover test documents forwarding and neighbor behavior against the HA design.

C:

The proposed principle concerns another network fault: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Here, forwarding-plane continuity does not prove control-plane routing continuity. The most direct correction is to check whether GRES is paired with the intended GR or NSR support and verify protocol state, confirmed by a planned switchover test documents forwarding and neighbor behavior against the HA design.

D:

That result would be useful for a different failure, namely: One LAG member fails silently and the service loses capacity even though the logical interface remains active. The current case specifically calls for: Check whether GRES is paired with the intended GR or NSR support and verify protocol state. The required observed result is: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Question 582

An IS-IS route disappears after a policy update while the LSP database still contains the topology. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Differentiate community tags from reachability and forwarding attributes.
  2. Remediation: Inspect link quality, interface settings and DIS state before forcing election behavior.
  3. Recommended change: Inspect route import policy and forwarding selection separately from LSP presence.
  4. Next step: Compute total advertised IS-IS metrics instead of assuming capacity implies preference.

Explanation

Correct Answer

C:

Because a learned LSP does not ensure a destination is selected into the active routing table, the best response is to inspect route import policy and forwarding selection separately from LSP presence. A reviewer can close the technical case only after confirming that the route policy and active table agree with the approved advertised prefixes.

Incorrect Answers

A:

Differentiate community tags from reachability and forwarding attributes is a relevant step for the separate scenario in which an engineer treats a BGP community value as a standalone forwarding next hop. It does not directly fix this case. Instead inspect route import policy and forwarding selection separately from LSP presence; verify: The route policy and active table agree with the approved advertised prefixes.

B:

The alternative addresses an IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss, not the present root cause. Here the selected correction must reflect a learned LSP does not ensure a destination is selected into the active routing table. Test for: The route policy and active table agree with the approved advertised prefixes.

D:

This option overlooks the decisive condition. Its supporting principle is iS-IS path selection is based on link-state topology and metrics, while this scenario depends on a learned LSP does not ensure a destination is selected into the active routing table. Verify the correction with: The route policy and active table agree with the approved advertised prefixes.

Question 583

An engineer expects a designated router to be elected on a point-to-point OSPF circuit. What diagnosis and engineering response are most appropriate?

  1. Cause: Route preference determines the selected route before any multipath decision. Response: Review route preference before considering equivalent forwarding paths.
  2. Diagnosis: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Action: Select the correct network-type behavior and inspect the neighbor-state model.
  3. Explanation: Protocol timers need reliable packet delivery and should not mask an unstable link. Repair: Compare Hello/Dead event logs with loss and interface errors before tuning timers.
  4. Fault mechanism: OSPF route selection follows each router's synchronized topology view. Remediation: Inspect link-state databases and SPF output on affected routers.

Explanation

Correct Answer

B:

The critical observation is: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Correct it by taking this action: Select the correct network-type behavior and inspect the neighbor-state model. Confirm the outcome with: The point-to-point adjacency forms without an unnecessary DR election.

Incorrect Answers

A:

The proposed principle concerns another network fault: Route preference determines the selected route before any multipath decision. Here, dR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. The most direct correction is to select the correct network-type behavior and inspect the neighbor-state model, confirmed by the point-to-point adjacency forms without an unnecessary DR election.

C:

This response would target a different source scenario: Several routers report intermittent OSPF neighbor resets on a saturated transit circuit. It cannot establish the current acceptance requirement, which is: The point-to-point adjacency forms without an unnecessary DR election. The relevant action is: Select the correct network-type behavior and inspect the neighbor-state model.

D:

Inspect link-state databases and SPF output on affected routers is a relevant step for the separate scenario in which a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. It does not directly fix this case. Instead select the correct network-type behavior and inspect the neighbor-state model; verify: The point-to-point adjacency forms without an unnecessary DR election.

Question 584

One LAG member fails silently and the service loses capacity even though the logical interface remains active. What observable result most directly verifies the intended configuration?

  1. The test confirms that a controlled forwarding failure is detected within the approved target.
  2. Expected observation: A planned switchover test documents forwarding and neighbor behavior against the HA design.
  3. Verification result: The fault is visible and surviving members carry traffic within the approved limits.
  4. Closeout evidence: The point-to-point adjacency forms without an unnecessary DR election.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Aggregated links need operational member health monitoring and suitable capacity planning. Remedy: Inspect member states, traffic distribution and configured minimum link expectations. Proof: The fault is visible and surviving members carry traffic within the approved limits.

Incorrect Answers

A:

This answer would be more suitable when a routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up, where the corrective action is to evaluate BFD liveness detection with the associated routing protocol. The failure here is different: Aggregated links need operational member health monitoring and suitable capacity planning. Required validation: The fault is visible and surviving members carry traffic within the approved limits.

B:

This option overlooks the decisive condition. Its supporting principle is forwarding-plane continuity does not prove control-plane routing continuity, while this scenario depends on aggregated links need operational member health monitoring and suitable capacity planning. Verify the correction with: The fault is visible and surviving members carry traffic within the approved limits.

D:

The proposed principle concerns another network fault: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Here, aggregated links need operational member health monitoring and suitable capacity planning. The most direct correction is to inspect member states, traffic distribution and configured minimum link expectations, confirmed by the fault is visible and surviving members carry traffic within the approved limits.

Question 585

Small probes pass through GRE but large customer packets are intermittently dropped. What observable result most directly verifies the intended configuration?

  1. Acceptance check: The tunnel endpoints pass test traffic after source correction.
  2. The test confirms that the test service label is retained and accepted at the target PE.
  3. Expected observation: Only authorized customer prefixes enter or leave the decapsulated routing context.
  4. Verification result: A controlled large-payload test succeeds after MTU or MSS adjustment.

Explanation

Correct Answer

D:

The case turns on the distinction that gRE encapsulation overhead can expose MTU blackholes for larger payloads. Apply this concrete engineering step: Test effective MTU and path MTU discovery across the encapsulated route. An acceptable verification outcome is: A controlled large-payload test succeeds after MTU or MSS adjustment.

Incorrect Answers

A:

This response would target a different source scenario: A GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. 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.

B:

Inspect outer transport and inner service label handling separately is a relevant step for the separate scenario in which a customer overlay fails across an MPLS core only for one service label. It does not directly fix this case. Instead test effective MTU and path MTU discovery across the encapsulated route; verify: A controlled large-payload test succeeds after MTU or MSS adjustment.

C:

The alternative addresses a provider tunnels traffic for customer isolation but makes no decision about routing-policy exposure at the tunnel edge, not the present root cause. Here the selected correction must reflect gRE encapsulation overhead can expose MTU blackholes for larger payloads. Test for: A controlled large-payload test succeeds after MTU or MSS adjustment.

Question 586

A backup path becomes primary after a preference edit even though the design called for failover only. Which corrective action and confirmation pair is most appropriate?

  1. Change: Restore the intended route preferences and check selected forwarding next hops. Test: A primary-link test chooses the expected primary then fails to backup on loss.
  2. Implement: Compare RIB selection with forwarding-table installation and next-hop resolution. Verify: The forwarding entry uses the correct next hop for the active route.
  3. 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.
  4. Action: Differentiate neighbor discovery from database synchronization message types. Evidence: The packet trace shows each message at its appropriate adjacency stage.

Explanation

Correct Answer

A:

Because preference edits can change route selection without any interface outage, the best response is to restore the intended route preferences and check selected forwarding next hops. A reviewer can close the technical case only after confirming that a primary-link test chooses the expected primary then fails to backup on loss.

Incorrect Answers

B:

The proposed principle concerns another network fault: Control-plane route visibility and installed forwarding state are distinct evidence. Here, preference edits can change route selection without any interface outage. The most direct correction is to restore the intended route preferences and check selected forwarding next hops, confirmed by a primary-link test chooses the expected primary then fails to backup on loss.

C:

That result would be useful for a different failure, namely: A RIB group leak forwards a VPN service toward the wrong next hop after a route update. The current case specifically calls for: Restore the intended route preferences and check selected forwarding next hops. The required observed result is: A primary-link test chooses the expected primary then fails to backup on loss.

D:

This response would target a different source scenario: A technician treats an OSPF Link State Request as the same message as a Hello packet. It cannot establish the current acceptance requirement, which is: A primary-link test chooses the expected primary then fails to backup on loss. The relevant action is: Restore the intended route preferences and check selected forwarding next hops.

Question 587

A route shows as active but the interface destination still drops traffic after an interface move. Which statement identifies the key design assumption that failed?

  1. Root design issue: Forwarding-table and interface evidence localize faults beyond RIB reachability.
  2. The governing rule is: Neighbor discovery can succeed even when database exchange parameters prevent completion.
  3. The key distinction is: A configured static route need not become usable forwarding state when its next hop cannot resolve.
  4. Protocol behavior: Imported routes must be validated in the destination lookup context.

Explanation

Correct Answer

A:

The case turns on the distinction that forwarding-table and interface evidence localize faults beyond RIB reachability. Apply this concrete engineering step: Compare installed forwarding entries with interface operational status and adjacency resolution. An acceptable verification outcome is: A test packet follows the expected active forwarding next hop and interface.

Incorrect Answers

B:

This answer would be more suitable when an OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange, where the corrective action is to check MTU and interface compatibility and inspect neighbor-state details. The failure here is different: Forwarding-table and interface evidence localize faults beyond RIB reachability. Required validation: A test packet follows the expected active forwarding next hop and interface.

C:

This option overlooks the decisive condition. Its supporting principle is a configured static route need not become usable forwarding state when its next hop cannot resolve, while this scenario depends on forwarding-table and interface evidence localize faults beyond RIB reachability. Verify the correction with: A test packet follows the expected active forwarding next hop and interface.

D:

Imported routes must be validated in the destination lookup context describes a neighboring protocol concern. In this case the controlling fact is forwarding-table and interface evidence localize faults beyond RIB reachability. A correct remediation would compare installed forwarding entries with interface operational status and adjacency resolution and demonstrate: A test packet follows the expected active forwarding next hop and interface.

Question 588

A service provider tunnels IPv6 over an IPv4 core but expects native IPv6 forwarding at every transit hop. Which combined repair and acceptance criterion is strongest?

  1. Action: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU. Evidence: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.
  2. Repair: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. Check: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.
  3. Change: Inspect IS-IS interface enablement, levels, area identifiers and link type. Test: The corrected circuit shows the expected neighbor and link-state entries.
  4. Implement: Distinguish IPv6 Neighbor Discovery from IPv4 ARP. Verify: The neighbor cache resolves the IPv6 next hop and traffic passes.

Explanation

Correct Answer

B:

Because tunneling carries one protocol over an underlay that may not route that payload natively, the best response is to model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. A reviewer can close the technical case only after confirming that a tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

Incorrect Answers

A:

That result would be useful for a different failure, namely: IPv6-over-IPv4 tunnel endpoints reach each other using IPv4 but IPv6 payloads fail after a firewall update. The current case specifically calls for: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. The required observed result is: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

C:

Inspect IS-IS interface enablement, levels, area identifiers and link type is a relevant step for the separate scenario in which a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. It does not directly fix this case. Instead model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport; verify: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

D:

The alternative addresses a provider configures an IPv6 static route but assumes IPv4 ARP will resolve its IPv6 neighbor, not the present root cause. Here the selected correction must reflect tunneling carries one protocol over an underlay that may not route that payload natively. Test for: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

Question 589

A new redundant uplink produces a broadcast storm on an access VLAN. Which change best corrects the failure without losing the intended design?

  1. Next step: Align region identity, revision and VLAN mapping as required.
  2. Corrective action: Review root bridge priority and MAC-based bridge identifier comparison.
  3. Apply this control: Set appropriate port mode and tag handling at the service edge.
  4. Remediation: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain.

Explanation

Correct Answer

D:

The selected response implements the principle that loop prevention depends on compatible STP participation across redundant Ethernet links. The engineer should inspect STP state and enable the approved spanning-tree protocol for that bridge domain. Successful confirmation means: The ring converges with no forwarding loop and sustained connectivity.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is mSTP region agreement affects how instances interoperate across links, while this scenario depends on loop prevention depends on compatible STP participation across redundant Ethernet links. Verify the correction with: The ring converges with no forwarding loop and sustained connectivity.

B:

Traditional spanning-tree root election favors the lowest bridge ID describes a neighboring protocol concern. In this case the controlling fact is loop prevention depends on compatible STP participation across redundant Ethernet links. A correct remediation would inspect STP state and enable the approved spanning-tree protocol for that bridge domain and demonstrate: The ring converges with no forwarding loop and sustained connectivity.

C:

The proposed principle concerns another network fault: Customer-facing encapsulation must match the traffic format at ingress. Here, loop prevention depends on compatible STP participation across redundant Ethernet links. The most direct correction is to inspect STP state and enable the approved spanning-tree protocol for that bridge domain, confirmed by the ring converges with no forwarding loop and sustained connectivity.

Question 590

An NSR configuration fails commit after an operator adds graceful restart on the same device. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: Conflicting local GR and NSR configuration must be resolved before activation. Remediation: Remove the incompatible local mode and validate the supported HA configuration.
  2. Root issue: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Correction: Select the correct network-type behavior and inspect the neighbor-state model.
  3. Cause: Forwarding-plane continuity does not prove control-plane routing continuity. Response: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.
  4. Diagnosis: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Action: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.

Explanation

Correct Answer

A:

Correct diagnosis: Conflicting local GR and NSR configuration must be resolved before activation. The appropriate action is: Remove the incompatible local mode and validate the supported HA configuration. The follow-up evidence required is: The corrected candidate commits and the Routing Engine synchronization check passes.

Incorrect Answers

B:

The alternative addresses an engineer expects a designated router to be elected on a point-to-point OSPF circuit, 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.

C:

This answer would be more suitable when a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart, where the corrective action is to check whether GRES is paired with the intended GR or NSR support and verify protocol state. 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.

D:

This option overlooks the decisive condition. Its supporting principle is nonstop bridging protects relevant Layer 2 control-protocol state during switchover, while this scenario depends on conflicting local GR and NSR configuration must be resolved before activation. Verify the correction with: The corrected candidate commits and the Routing Engine synchronization check passes.

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