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 36

Question 350

An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. What implementation step and validation result should be selected?

  1. Change: Check MTU and interface compatibility and inspect neighbor-state details. Test: The adjacency advances through database synchronization to Full.
  2. Implement: 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.
  3. Control: Constrain redistribution and test route policy acceptance for the intended prefixes. Accepted result: Only approved external prefixes appear in the OSPF domain.
  4. Action: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. Evidence: The segment passes route and database tests with the expected neighbor states.

Explanation

Correct Answer

A:

Correct diagnosis: Neighbor discovery can succeed even when database exchange parameters prevent completion. The appropriate action is: Check MTU and interface compatibility and inspect neighbor-state details. The follow-up evidence required is: The adjacency advances through database synchronization to Full.

Incorrect Answers

B:

The alternative addresses after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, not the present root cause. Here the selected correction must reflect neighbor discovery can succeed even when database exchange parameters prevent completion. Test for: The adjacency advances through database synchronization to Full.

C:

This answer would be more suitable when a provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy, where the corrective action is to constrain redistribution and test route policy acceptance for the intended prefixes. The failure here is different: Neighbor discovery can succeed even when database exchange parameters prevent completion. Required validation: The adjacency advances through database synchronization to Full.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF neighbor-state interpretation depends on multiaccess election roles, while this scenario depends on neighbor discovery can succeed even when database exchange parameters prevent completion. Verify the correction with: The adjacency advances through database synchronization to Full.

Question 351

An IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node. Which change best corrects the failure without losing the intended design?

  1. Apply this control: Compare NET area addresses and intended L1 or L2 adjacency mode.
  2. Remediation: Review current DIS election rules for the network and protocol instance.
  3. Recommended change: Review Level 1 and Level 2 routing roles and their intended boundaries.
  4. Next step: Verify negotiated address families and family-specific routing tables.

Explanation

Correct Answer

B:

The critical observation is: The designated system serves LAN pseudonode advertisement and election semantics. Correct it by taking this action: Review current DIS election rules for the network and protocol instance. Confirm the outcome with: The LAN's DIS and pseudonode LSP match the documented protocol state.

Incorrect Answers

A:

The proposed principle concerns another network fault: Area mismatch can affect Level 1 adjacency even when packets are received. Here, the designated system serves LAN pseudonode advertisement and election semantics. The most direct correction is to review current DIS election rules for the network and protocol instance, confirmed by the LAN's DIS and pseudonode LSP match the documented protocol state.

C:

This response would target a different source scenario: A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. It cannot establish the current acceptance requirement, which is: The LAN's DIS and pseudonode LSP match the documented protocol state. The relevant action is: Review current DIS election rules for the network and protocol instance.

D:

Verify negotiated address families and family-specific routing tables is a relevant step for the separate scenario in which a peer announces an IPv6 prefix but the operator checks only the IPv4 BGP route family. It does not directly fix this case. Instead review current DIS election rules for the network and protocol instance; verify: The LAN's DIS and pseudonode LSP match the documented protocol state.

Question 352

A provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. What is the primary routing or switching concept illustrated?

  1. Underlying principle: Different segment types express different routing or link steering semantics.
  2. Root design issue: Disabling loop prevention can introduce persistent interdomain routing loops.
  3. The governing rule is: MED is not guaranteed to override local policy or earlier attributes.
  4. The key distinction is: BGP group inheritance and policy direction govern which advertisements are modified.

Explanation

Correct Answer

B:

Correct diagnosis: Disabling loop prevention can introduce persistent interdomain routing loops. The appropriate action is: Restore standard AS-path checks and review any justified exception with design authority. The follow-up evidence required is: An unwanted looped route is rejected in a lab before production change.

Incorrect Answers

A:

This answer would be more suitable when a segment routing node uses a prefix segment but the operator treats it as a local adjacency segment, where the corrective action is to distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. The failure here is different: Disabling loop prevention can introduce persistent interdomain routing loops. Required validation: An unwanted looped route is rejected in a lab before production change.

C:

MED is not guaranteed to override local policy or earlier attributes describes a neighboring protocol concern. In this case the controlling fact is disabling loop prevention can introduce persistent interdomain routing loops. A correct remediation would restore standard AS-path checks and review any justified exception with design authority and demonstrate: An unwanted looped route is rejected in a lab before production change.

D:

The proposed principle concerns another network fault: BGP group inheritance and policy direction govern which advertisements are modified. Here, disabling loop prevention can introduce persistent interdomain routing loops. The most direct correction is to restore standard AS-path checks and review any justified exception with design authority, confirmed by an unwanted looped route is rejected in a lab before production change.

Question 353

An operator assumes MPLS labels are globally unique across the provider network. Which evidence would justify closing this troubleshooting case?

  1. The test confirms that a path test records locally valid incoming and outgoing label mappings.
  2. Expected observation: The summary is advertised only under the approved component-route conditions.
  3. Verification result: The repaired hop has the expected swap operation and carries a test packet.
  4. Closeout evidence: The labeled service route resolves after the intended LSP is restored.

Explanation

Correct Answer

A:

Underlying cause: Labels are generally meaningful within the forwarding context where they are allocated. Corrective action: explain local label significance and neighbor label binding. Verify the outcome: A path test records locally valid incoming and outgoing label mappings.

Incorrect Answers

B:

Distinguish aggregate reachability from specific-route forwarding and test loss of component routes is a relevant step for the separate scenario in which a summary route is advertised even though the operator expects every more-specific customer route to remain reachable. It does not directly fix this case. Instead explain local label significance and neighbor label binding; verify: A path test records locally valid incoming and outgoing label mappings.

C:

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 labels are generally meaningful within the forwarding context where they are allocated. Test for: A path test records locally valid incoming and outgoing label mappings.

D:

This answer would be more suitable when a loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable, where the corrective action is to inspect label-switched next-hop resolution separately from generic IP reachability. The failure here is different: Labels are generally meaningful within the forwarding context where they are allocated. Required validation: A path test records locally valid incoming and outgoing label mappings.

Question 354

An operator configured an explicit RSVP path through a link that is now administratively down. What operational check demonstrates that the intended outcome occurred?

  1. Acceptance check: The repaired hop has the expected swap operation and carries a test packet.
  2. The test confirms that a segment trace follows the desired prefix or explicit adjacency.
  3. Expected observation: The backup LSP establishes on a permitted alternate path.
  4. Verification result: The rejected address remains excluded or a documented narrowly scoped exception is applied.

Explanation

Correct Answer

C:

Correct diagnosis: An LSP cannot follow an unavailable required hop. The appropriate action is: Update the engineered path constraints and verify candidate topology availability. The follow-up evidence required is: The backup LSP establishes on a permitted alternate path.

Incorrect Answers

A:

Label-switching errors can occur even when control-plane endpoint reachability is good describes a neighboring protocol concern. In this case the controlling fact is an LSP cannot follow an unavailable required hop. A correct remediation would update the engineered path constraints and verify candidate topology availability and demonstrate: The backup LSP establishes on a permitted alternate path.

B:

The proposed principle concerns another network fault: Different segment types express different routing or link steering semantics. Here, an LSP cannot follow an unavailable required hop. The most direct correction is to update the engineered path constraints and verify candidate topology availability, confirmed by the backup LSP establishes on a permitted alternate path.

D:

This response would target a different source scenario: An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. It cannot establish the current acceptance requirement, which is: The backup LSP establishes on a permitted alternate path. The relevant action is: Update the engineered path constraints and verify candidate topology availability.

Question 355

A route reflector receives a new branch prefix but one iBGP client never learns it. Which change best corrects the failure without losing the intended design?

  1. Remediation: Compare MED use with actual prior BGP decision attributes and neighbor policy.
  2. Recommended change: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions.
  3. Next step: Check client definitions, route-reflector session state and export policy.
  4. Corrective action: Map inbound and outbound policy points and confirm the intended communities.

Explanation

Correct Answer

C:

The selected response implements the principle that route reflection can fail due to session or policy scope even when the route exists centrally. The engineer should check client definitions, route-reflector session state and export policy. Successful confirmation means: The missing client receives the correct next-hop-resolvable route.

Incorrect Answers

A:

The alternative addresses an operator changes MED and sees no route change because the target AS prioritizes other attributes, not the present root cause. Here the selected correction must reflect route reflection can fail due to session or policy scope even when the route exists centrally. Test for: The missing client receives the correct next-hop-resolvable route.

B:

This answer would be more suitable when a segment routing node uses a prefix segment but the operator treats it as a local adjacency segment, where the corrective action is to distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. The failure here is different: Route reflection can fail due to session or policy scope even when the route exists centrally. Required validation: The missing client receives the correct next-hop-resolvable route.

D:

BGP group inheritance and policy direction govern which advertisements are modified describes a neighboring protocol concern. In this case the controlling fact is route reflection can fail due to session or policy scope even when the route exists centrally. A correct remediation would check client definitions, route-reflector session state and export policy and demonstrate: The missing client receives the correct next-hop-resolvable route.

Question 356

A MAC table is empty after a restart and an operator manually inserts dozens of addresses before sending test traffic. Which combined repair and acceptance criterion is strongest?

  1. Repair: Generate controlled frames and observe normal learning on the correct bridge domain. Check: A source MAC appears on the expected port after a test frame.
  2. Change: Verify VLAN-to-IRB interface binding, addresses and active route entries. Test: A test host ARPs or discovers its gateway and routes to the intended subnet.
  3. Implement: Set appropriate port mode and tag handling at the service edge. Verify: The test frame is accepted only under the approved tagging plan.
  4. Control: Distinguish member-link redundancy from a single physical failure domain. Accepted result: A member link failure leaves traffic flowing through a remaining usable member.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Dynamic MAC tables are populated by observed frames and need not be prefilled. Remedy: Generate controlled frames and observe normal learning on the correct bridge domain. Proof: A source MAC appears on the expected port after a test frame.

Incorrect Answers

B:

This response would target a different source scenario: A router-on-a-stick replacement with IRB stops reachability between a bridge domain and an L3 subnet. It cannot establish the current acceptance requirement, which is: A source MAC appears on the expected port after a test frame. The relevant action is: Generate controlled frames and observe normal learning on the correct bridge domain.

C:

Set appropriate port mode and tag handling at the service edge is a relevant step for the separate scenario in which an Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. It does not directly fix this case. Instead generate controlled frames and observe normal learning on the correct bridge domain; verify: A source MAC appears on the expected port after a test frame.

D:

The alternative addresses a failover plan relies on one physical interface carrying several links and calls it a redundant LAG, not the present root cause. Here the selected correction must reflect dynamic MAC tables are populated by observed frames and need not be prefilled. Test for: A source MAC appears on the expected port after a test frame.

Question 357

An operator expects an MPLS label to represent an entire customer IP packet header. Which protocol behavior most directly determines the correct diagnosis?

  1. Underlying principle: Route reflection can fail due to session or policy scope even when the route exists centrally.
  2. Root design issue: MPLS forwarding typically uses labels to select the next label-switched hop.
  3. The governing rule is: Labels have locally significant forwarding meaning on each LSP segment.
  4. The key distinction is: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults.

Explanation

Correct Answer

B:

The case turns on the distinction that mPLS forwarding typically uses labels to select the next label-switched hop. Apply this concrete engineering step: Distinguish the MPLS shim label stack from the encapsulated payload. An acceptable verification outcome is: A packet decode identifies label fields separately from the carried IP packet.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is route reflection can fail due to session or policy scope even when the route exists centrally, while this scenario depends on mPLS forwarding typically uses labels to select the next label-switched hop. Verify the correction with: A packet decode identifies label fields separately from the carried IP packet.

C:

The proposed principle concerns another network fault: Labels have locally significant forwarding meaning on each LSP segment. Here, mPLS forwarding typically uses labels to select the next label-switched hop. The most direct correction is to distinguish the MPLS shim label stack from the encapsulated payload, confirmed by a packet decode identifies label fields separately from the carried IP packet.

D:

That result would be useful for a different failure, namely: One branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. 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.

Question 358

A router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table. What implementation step and validation result should be selected?

  1. Control: Review filter-based forwarding classification and the intended next-table selection. Accepted result: A trace of matching and nonmatching packets shows the approved lookup table.
  2. Action: Restore standard AS-path checks and review any justified exception with design authority. Evidence: An unwanted looped route is rejected in a lab before production change.
  3. Repair: Validate forwarding load-sharing configuration and run representative multi-flow traffic. Check: A documented multi-flow test matches the configured distribution policy.
  4. Change: Verify route contribution and the conditions for route generation. Test: The generated prefix appears only when the required contributing route is active.

Explanation

Correct Answer

A:

Correct diagnosis: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. The appropriate action is: Review filter-based forwarding classification and the intended next-table selection. The follow-up evidence required is: A trace of matching and nonmatching packets shows the approved lookup table.

Incorrect Answers

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 policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Test for: A trace of matching and nonmatching packets shows the approved lookup table.

C:

This answer would be more suitable when an equal-cost path test sends nearly all flows across one member while both links remain operational, where the corrective action is to validate forwarding load-sharing configuration and run representative multi-flow traffic. The failure here is different: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Required validation: A trace of matching and nonmatching packets shows the approved lookup table.

D:

This option overlooks the decisive condition. Its supporting principle is a generated route depends on its contributing-route conditions rather than mere configuration presence, while this scenario depends on policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Verify the correction with: A trace of matching and nonmatching packets shows the approved lookup table.

Question 359

A network design assumes RSVP and LDP use identical path signaling and traffic engineering controls. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Implement: Distinguish the MPLS shim label stack from the encapsulated payload. Verify: A packet decode identifies label fields separately from the carried IP packet.
  2. Control: Validate forwarding load-sharing configuration and run representative multi-flow traffic. Accepted result: A documented multi-flow test matches the configured distribution policy.
  3. Action: Review reservation constraints and available resources rather than resetting all label sessions. Evidence: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  4. Repair: Separate RSVP-signaled LSP functions from LDP label distribution. Check: The chosen protocol establishes the intended type of LSP.

Explanation

Correct Answer

D:

Underlying cause: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Corrective action: separate RSVP-signaled LSP functions from LDP label distribution. Verify the outcome: The chosen protocol establishes the intended type of LSP.

Incorrect Answers

A:

The proposed principle concerns another network fault: MPLS forwarding typically uses labels to select the next label-switched hop. Here, rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. The most direct correction is to separate RSVP-signaled LSP functions from LDP label distribution, confirmed by the chosen protocol establishes the intended type of LSP.

B:

That result would be useful for a different failure, namely: An equal-cost path test sends nearly all flows across one member while both links remain operational. The current case specifically calls for: Separate RSVP-signaled LSP functions from LDP label distribution. The required observed result is: The chosen protocol establishes the intended type of LSP.

C:

This response would target a different source scenario: An RSVP-signaled LSP enters a failed state after a link bandwidth change. It cannot establish the current acceptance requirement, which is: The chosen protocol establishes the intended type of LSP. The relevant action is: Separate RSVP-signaled LSP functions from LDP label distribution.

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.

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