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 55

Question 540

After a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors. Which combined repair and acceptance criterion is strongest?

  1. Implement: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Verify: The test demonstrates loop prevention without advertising false service reachability.
  2. Control: Inspect the configuration, active route state and next-hop reachability before changing preference. Accepted result: The static route becomes active after the actual next-hop fault is corrected.
  3. Action: Confirm the configured local and peer AS values with the authoritative design. Evidence: The session reaches Established only with the documented correct peer AS.
  4. Repair: Review route preference before considering equivalent forwarding paths. Check: The selected path and its preference match the intended backup policy.

Explanation

Correct Answer

B:

Because operational route troubleshooting starts with active state and resolution evidence, the best response is to inspect the configuration, active route state and next-hop reachability before changing preference. A reviewer can close the technical case only after confirming that the static route becomes active after the actual next-hop fault is corrected.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop. The current case specifically calls for: Inspect the configuration, active route state and next-hop reachability before changing preference. The required observed result is: The static route becomes active after the actual next-hop fault is corrected.

C:

Confirm the configured local and peer AS values with the authoritative design is a relevant step for the separate scenario in which a remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. It does not directly fix this case. Instead inspect the configuration, active route state and next-hop reachability before changing preference; verify: The static route becomes active after the actual next-hop fault is corrected.

D:

The alternative addresses two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic, not the present root cause. Here the selected correction must reflect operational route troubleshooting starts with active state and resolution evidence. Test for: The static route becomes active after the actual next-hop fault is corrected.

Question 541

A BGP peer is stuck in Active after a maintenance window even though the remote address is configured. What action-and-test pairing directly resolves the case?

  1. Change: Verify IP reachability, routing instance context, TCP transport and session authentication. Test: The TCP peering session reaches Established and remains stable.
  2. Implement: Confirm the configured local and peer AS values with the authoritative design. Verify: The session reaches Established only with the documented correct peer AS.
  3. Control: Differentiate neighbor discovery from database synchronization message types. Accepted result: The packet trace shows each message at its appropriate adjacency stage.
  4. Action: Evaluate routing-policy local preference before later BGP path-selection attributes. Evidence: The intended local preference policy selects the approved egress.

Explanation

Correct Answer

A:

The critical observation is: Neighbor state must be traced through transport before modifying route policy. Correct it by taking this action: Verify IP reachability, routing instance context, TCP transport and session authentication. Confirm the outcome with: The TCP peering session reaches Established and remains stable.

Incorrect Answers

B:

BGP OPEN negotiation includes AS identity that must match peering intent describes a neighboring protocol concern. In this case the controlling fact is neighbor state must be traced through transport before modifying route policy. A correct remediation would verify IP reachability, routing instance context, TCP transport and session authentication and demonstrate: The TCP peering session reaches Established and remains stable.

C:

The proposed principle concerns another network fault: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Here, neighbor state must be traced through transport before modifying route policy. The most direct correction is to verify IP reachability, routing instance context, TCP transport and session authentication, confirmed by the TCP peering session reaches Established and remains stable.

D:

That result would be useful for a different failure, namely: Two BGP paths have different local preferences and a technician expects the shorter AS path always to win. The current case specifically calls for: Verify IP reachability, routing instance context, TCP transport and session authentication. The required observed result is: The TCP peering session reaches Established and remains stable.

Question 542

A RIB group leak forwards a VPN service toward the wrong next hop after a route update. Which post-change observation most strongly confirms the correction?

  1. Verification result: Each customer route is visible only in the tables approved by the design.
  2. Closeout evidence: Each router is uniquely identified and the link-state database converges.
  3. Acceptance check: A primary-link test chooses the expected primary then fails to backup on loss.
  4. The test confirms that the receiving instance shows the correct route and installed next hop after correction.

Explanation

Correct Answer

D:

This is the model-intended best choice because imported routes must be validated in the destination lookup context. The targeted correction is to check import destinations, next-hop resolution and effective routes in every receiving table. Validate it by observing that the receiving instance shows the correct route and installed next hop after correction.

Incorrect Answers

A:

Define the intended route-leaking boundary between the customer's instance and the master routing table is a relevant step for the separate scenario in which a provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. It does not directly fix this case. Instead check import destinations, next-hop resolution and effective routes in every receiving table; verify: The receiving instance shows the correct route and installed next hop after correction.

B:

The alternative addresses two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent, not the present root cause. Here the selected correction must reflect imported routes must be validated in the destination lookup context. Test for: The receiving instance shows the correct route and installed next hop after correction.

C:

This answer would be more suitable when a backup path becomes primary after a preference edit even though the design called for failover only, where the corrective action is to restore the intended route preferences and check selected forwarding next hops. The failure here is different: Imported routes must be validated in the destination lookup context. Required validation: The receiving instance shows the correct route and installed next hop after correction.

Question 543

A BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared. Which cause-and-remedy pairing reflects the observed problem?

  1. Cause: IPv4 operational success does not prove IPv6 forwarding configuration. Response: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.
  2. Diagnosis: BGP family negotiation and route policy control IPv6 NLRI exchange. Action: Enable and verify the intended IPv6 BGP family and export policy.
  3. Explanation: Tunnel endpoint parameters must correspond to actual reachable interfaces. Repair: Verify configured tunnel source and destination and their active underlay routing.
  4. Fault mechanism: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Remediation: Apply longest-prefix-match route lookup to the IPv6 destination.

Explanation

Correct Answer

B:

The critical observation is: BGP family negotiation and route policy control IPv6 NLRI exchange. Correct it by taking this action: Enable and verify the intended IPv6 BGP family and export policy. Confirm the outcome with: The selected inet6 route appears on the authorized IPv6 peer.

Incorrect Answers

A:

The proposed principle concerns another network fault: IPv4 operational success does not prove IPv6 forwarding configuration. 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.

C:

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: The selected inet6 route appears on the authorized IPv6 peer. The relevant action is: Enable and verify the intended IPv6 BGP family and export policy.

D:

Apply longest-prefix-match route lookup to the IPv6 destination is a relevant step for the separate scenario in which an engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. It does not directly fix this case. Instead enable and verify the intended IPv6 BGP family and export policy; verify: The selected inet6 route appears on the authorized IPv6 peer.

Question 544

An access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame. Which post-change observation most strongly confirms the correction?

  1. The test confirms that an end-host packet enters the correct VLAN without requiring endpoint tagging.
  2. Expected observation: A packet capture shows the intended outer and inner VLAN tags end to end.
  3. Verification result: The MAC table stabilizes on the authorized port after loop or miswire correction.
  4. Closeout evidence: A region status check shows the intended shared instance mapping.

Explanation

Correct Answer

A:

This is the model-intended best choice because port mode determines which customer frames are tagged or untagged at the boundary. The targeted correction is to distinguish access port traffic from trunk tagging behavior. Validate it by observing that an end-host packet enters the correct VLAN without requiring endpoint tagging.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is stacked VLAN services require compatible tagging interpretation at both ends, while this scenario depends on port mode determines which customer frames are tagged or untagged at the boundary. Verify the correction with: An end-host packet enters the correct VLAN without requiring endpoint tagging.

C:

MAC learning reflects observed source location and may churn during loops or mobility describes a neighboring protocol concern. In this case the controlling fact is port mode determines which customer frames are tagged or untagged at the boundary. A correct remediation would distinguish access port traffic from trunk tagging behavior and demonstrate: An end-host packet enters the correct VLAN without requiring endpoint tagging.

D:

The proposed principle concerns another network fault: MSTP region agreement affects how instances interoperate across links. Here, port mode determines which customer frames are tagged or untagged at the boundary. The most direct correction is to distinguish access port traffic from trunk tagging behavior, confirmed by an end-host packet enters the correct VLAN without requiring endpoint tagging.

Question 545

A Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. Which technical explanation and controlled action address the symptom?

  1. Fault mechanism: A backup path requires functional forwarding, not merely topology presence. Remediation: Rehearse the failure and inspect active next hops and IS-IS route changes.
  2. Root issue: Route reflection can fail due to session or policy scope even when the route exists centrally. Correction: Check client definitions, route-reflector session state and export policy.
  3. Cause: An operational interface is not evidence of matching IS-IS protocol configuration. Response: Inspect IS-IS interface enablement, levels, area identifiers and link type.
  4. Diagnosis: IS-IS Level 1 adjacency formation depends on common area context. Action: Verify compatible area membership or use the designed Level 2 boundary.

Explanation

Correct Answer

C:

The critical observation is: An operational interface is not evidence of matching IS-IS protocol configuration. Correct it by taking this action: Inspect IS-IS interface enablement, levels, area identifiers and link type. Confirm the outcome with: The corrected circuit shows the expected neighbor and link-state entries.

Incorrect Answers

A:

This response would target a different source scenario: A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. It cannot establish the current acceptance requirement, which is: The corrected circuit shows the expected neighbor and link-state entries. The relevant action is: Inspect IS-IS interface enablement, levels, area identifiers and link type.

B:

Check client definitions, route-reflector session state and export policy is a relevant step for the separate scenario in which a route reflector receives a new branch prefix but one iBGP client never learns it. It does not directly fix this case. Instead inspect IS-IS interface enablement, levels, area identifiers and link type; verify: The corrected circuit shows the expected neighbor and link-state entries.

D:

This answer would be more suitable when an IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship, where the corrective action is to verify compatible area membership or use the designed Level 2 boundary. The failure here is different: An operational interface is not evidence of matching IS-IS protocol configuration. Required validation: The corrected circuit shows the expected neighbor and link-state entries.

Question 546

OSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path. Which test result would best confirm a successful fix?

  1. Closeout evidence: A post-change route view selects the approved shortest path.
  2. Acceptance check: Each router is uniquely identified and the link-state database converges.
  3. The test confirms that the segment passes route and database tests with the expected neighbor states.
  4. Expected observation: A protocol decode identifies the expected advertised TLV information.

Explanation

Correct Answer

A:

Because oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone, the best response is to review each interface's OSPF metric and compare end-to-end computed costs. A reviewer can close the technical case only after confirming that a post-change route view selects the approved shortest path.

Incorrect Answers

B:

The proposed principle concerns another network fault: OSPF identifies speakers by router ID, which must be unique inside a routing domain. Here, oSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. The most direct correction is to review each interface's OSPF metric and compare end-to-end computed costs, confirmed by a post-change route view selects the approved shortest path.

C:

That result would be useful for a different failure, namely: A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. The current case specifically calls for: Review each interface's OSPF metric and compare end-to-end computed costs. The required observed result is: A post-change route view selects the approved shortest path.

D:

This response would target a different source scenario: An operator calls an IS-IS TLV a transport packet and ignores its role in link-state information. It cannot establish the current acceptance requirement, which is: A post-change route view selects the approved shortest path. The relevant action is: Review each interface's OSPF metric and compare end-to-end computed costs.

Question 547

A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. Which cause-and-remedy pairing reflects the observed problem?

  1. Diagnosis: Discard routes may intentionally bound routing loops while dynamic specifics converge. Action: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.
  2. Explanation: Neighbor state must be traced through transport before modifying route policy. Repair: Verify IP reachability, routing instance context, TCP transport and session authentication.
  3. Fault mechanism: Control-plane route visibility and installed forwarding state are distinct evidence. Remediation: Compare RIB selection with forwarding-table installation and next-hop resolution.
  4. Root issue: Moving route information between tables does not remove the need for a valid forwarding next hop. Correction: Evaluate routing-table relationships and next-hop resolution when using RIB groups.

Explanation

Correct Answer

C:

The selected response implements the principle that control-plane route visibility and installed forwarding state are distinct evidence. The engineer should compare RIB selection with forwarding-table installation and next-hop resolution. Successful confirmation means: The forwarding entry uses the correct next hop for the active route.

Incorrect Answers

A:

The alternative addresses an engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop, not the present root cause. Here the selected correction must reflect control-plane route visibility and installed forwarding state are distinct evidence. Test for: The forwarding entry uses the correct next hop for the active route.

B:

This answer would be more suitable when a BGP peer is stuck in Active after a maintenance window even though the remote address is configured, where the corrective action is to verify IP reachability, routing instance context, TCP transport and session authentication. The failure here is different: Control-plane route visibility and installed forwarding state are distinct evidence. Required validation: The forwarding entry uses the correct next hop for the active route.

D:

Moving route information between tables does not remove the need for a valid forwarding next hop describes a neighboring protocol concern. In this case the controlling fact is control-plane route visibility and installed forwarding state are distinct evidence. A correct remediation would compare RIB selection with forwarding-table installation and next-hop resolution and demonstrate: The forwarding entry uses the correct next hop for the active route.

Question 548

An operator expects an MPLS label to represent an entire customer IP packet header. Which root-cause explanation and corrective action fit the case?

  1. Cause: Preference edits can change route selection without any interface outage. Response: Restore the intended route preferences and check selected forwarding next hops.
  2. Diagnosis: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Action: Separate RSVP-signaled LSP functions from LDP label distribution.
  3. Explanation: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Repair: Compare ingress label imposition with transit LFIB and egress disposition.
  4. Fault mechanism: MPLS forwarding typically uses labels to select the next label-switched hop. Remediation: Distinguish the MPLS shim label stack from the encapsulated payload.

Explanation

Correct Answer

D:

Correct diagnosis: MPLS forwarding typically uses labels to select the next label-switched hop. The appropriate action is: Distinguish the MPLS shim label stack from the encapsulated payload. The follow-up evidence required is: A packet decode identifies label fields separately from the carried IP packet.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A backup path becomes primary after a preference edit even though the design called for failover only. The current case specifically calls for: Distinguish the MPLS shim label stack from the encapsulated payload. The required observed result is: A packet decode identifies label fields separately from the carried IP packet.

B:

This response would target a different source scenario: A network design assumes RSVP and LDP use identical path signaling and traffic engineering controls. It cannot establish the current acceptance requirement, which is: A packet decode identifies label fields separately from the carried IP packet. The relevant action is: Distinguish the MPLS shim label stack from the encapsulated payload.

C:

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 distinguish the MPLS shim label stack from the encapsulated payload; verify: A packet decode identifies label fields separately from the carried IP packet.

Question 549

A provider switch receives an unknown destination MAC and a new engineer expects it to unicast to a random uplink. What diagnosis and engineering response are most appropriate?

  1. Root issue: Traditional spanning-tree root election favors the lowest bridge ID. Correction: Review root bridge priority and MAC-based bridge identifier comparison.
  2. Cause: MAC learning reflects observed source location and may churn during loops or mobility. Response: Investigate MAC movement, loops and correct bridge-domain membership.
  3. Diagnosis: Bridges learn source MAC locations and flood unknown destinations within a permitted domain. Action: Review MAC learning and unknown-unicast handling within the correct bridge domain.
  4. Explanation: Customer-facing encapsulation must match the traffic format at ingress. Repair: Set appropriate port mode and tag handling at the service edge.

Explanation

Correct Answer

C:

Underlying cause: Bridges learn source MAC locations and flood unknown destinations within a permitted domain. Corrective action: review MAC learning and unknown-unicast handling within the correct bridge domain. Verify the outcome: A frame trace shows only expected domain members receive the unknown destination.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is traditional spanning-tree root election favors the lowest bridge ID, while this scenario depends on bridges learn source MAC locations and flood unknown destinations within a permitted domain. Verify the correction with: A frame trace shows only expected domain members receive the unknown destination.

B:

MAC learning reflects observed source location and may churn during loops or mobility 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.

D:

That result would be useful for a different failure, namely: An Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. The current case specifically calls for: Review MAC learning and unknown-unicast handling within the correct bridge domain. The required observed result is: A frame trace shows only expected domain members receive the unknown destination.

Question 550

An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Inspect IS-IS interface enablement, levels, area identifiers and link type.
  2. Next step: Review Level 1 and Level 2 routing roles and their intended boundaries.
  3. Corrective action: Check client definitions, route-reflector session state and export policy.
  4. Apply this control: Collect protocol adjacency, LSP and routing-table outputs for the affected route.

Explanation

Correct Answer

D:

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

A:

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 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.

B:

The alternative addresses a router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view, not the present root cause. Here the selected correction must reflect structured protocol-layer evidence separates link health from routing convergence issues. Test for: The report explains the fault from interface through neighbor to selected route.

C:

This answer would be more suitable when a route reflector receives a new branch prefix but one iBGP client never learns it, where the corrective action is to check client definitions, route-reflector session state and export policy. The failure here is different: Structured protocol-layer evidence separates link health from routing convergence issues. Required validation: The report explains the fault from interface through neighbor to selected route.

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