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 58

Question 570

An engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. Which next action best resolves this observed routing or switching failure?

  1. Recommended change: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport.
  2. Next step: Distinguish the inner routed payload from outer unicast encapsulation.
  3. Corrective action: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.
  4. Apply this control: Apply longest-prefix-match route lookup to the IPv6 destination.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Remedy: Apply longest-prefix-match route lookup to the IPv6 destination. Proof: A destination lookup chooses the intended most specific valid route.

Incorrect Answers

A:

Tunneling carries one protocol over an underlay that may not route that payload natively describes a neighboring protocol concern. In this case the controlling fact is iPv6 route selection follows prefix matching and route eligibility, not textual address order. A correct remediation would apply longest-prefix-match route lookup to the IPv6 destination and demonstrate: A destination lookup chooses the intended most specific valid route.

B:

The proposed principle concerns another network fault: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Here, iPv6 route selection follows prefix matching and route eligibility, not textual address order. The most direct correction is to apply longest-prefix-match route lookup to the IPv6 destination, confirmed by a destination lookup chooses the intended most specific valid route.

C:

That result would be useful for a different failure, namely: A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. The current case specifically calls for: Apply longest-prefix-match route lookup to the IPv6 destination. The required observed result is: A destination lookup chooses the intended most specific valid route.

Question 571

A carrier receives the same source MAC from two access ports and sees frequent forwarding-table moves. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Change: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary. Test: Each tested VLAN elects its approved root and loop-free port roles.
  2. Implement: Document VLAN-aware versus flexible tagging and unit classification requirements. Verify: Both test logical units classify tagged traffic into their intended bridge domains.
  3. Control: Investigate MAC movement, loops and correct bridge-domain membership. Accepted result: The MAC table stabilizes on the authorized port after loop or miswire correction.
  4. Action: Validate outer tag encapsulation and EtherType expectations across the handoff. Evidence: A packet capture shows the intended outer and inner VLAN tags end to end.

Explanation

Correct Answer

C:

The selected response implements the principle that mAC learning reflects observed source location and may churn during loops or mobility. The engineer should investigate MAC movement, loops and correct bridge-domain membership. Successful confirmation means: The MAC table stabilizes on the authorized port after loop or miswire correction.

Incorrect Answers

A:

The alternative addresses several VLANs have unexpected root placement under VSTP after port membership changes, not the present root cause. Here the selected correction must reflect mAC learning reflects observed source location and may churn during loops or mobility. Test for: The MAC table stabilizes on the authorized port after loop or miswire correction.

B:

This answer would be more suitable when an Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation, where the corrective action is to document VLAN-aware versus flexible tagging and unit classification requirements. The failure here is different: MAC learning reflects observed source location and may churn during loops or mobility. Required validation: The MAC table stabilizes on the authorized port after loop or miswire correction.

D:

Stacked VLAN services require compatible tagging interpretation at both ends describes a neighboring protocol concern. In this case the controlling fact is mAC learning reflects observed source location and may churn during loops or mobility. A correct remediation would investigate MAC movement, loops and correct bridge-domain membership and demonstrate: The MAC table stabilizes on the authorized port after loop or miswire correction.

Question 572

A switch has a root port and alternate port, but the operator assumes both must forward to use all physical bandwidth. Which underlying Junos networking principle explains the failure?

  1. Root design issue: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching.
  2. The governing rule is: RSTP can converge faster using explicit roles and handshakes where conditions allow.
  3. The key distinction is: Configuration intent must be verified against the actual elected spanning-tree root.
  4. Protocol behavior: A redundant alternate path can remain nonforwarding until a failure changes roles.

Explanation

Correct Answer

D:

Correct diagnosis: A redundant alternate path can remain nonforwarding until a failure changes roles. The appropriate action is: Explain root and alternate roles in a loop-free spanning-tree topology. The follow-up evidence required is: The alternate port transitions appropriately after the root path fails.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. The current case specifically calls for: Explain root and alternate roles in a loop-free spanning-tree topology. The required observed result is: The alternate port transitions appropriately after the root path fails.

B:

This response would target a different source scenario: Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. It cannot establish the current acceptance requirement, which is: The alternate port transitions appropriately after the root path fails. The relevant action is: Explain root and alternate roles in a loop-free spanning-tree topology.

C:

Compare root priority, bridge identifiers and current STP topology status is a relevant step for the separate scenario in which a planned root bridge migration is configured but the operational root remains on the old switch. It does not directly fix this case. Instead explain root and alternate roles in a loop-free spanning-tree topology; verify: The alternate port transitions appropriately after the root path fails.

Question 573

A technician treats an OSPF Link State Request as the same message as a Hello packet. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: The packet trace shows each message at its appropriate adjacency stage.
  2. Verification result: The adjacency advances through database synchronization to Full.
  3. Closeout evidence: Each customer route is visible only in the tables approved by the design.
  4. Acceptance check: A controlled neighbor check reaches Full after configuration correction.

Explanation

Correct Answer

A:

The critical observation is: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Correct it by taking this action: Differentiate neighbor discovery from database synchronization message types. Confirm the outcome with: The packet trace shows each message at its appropriate adjacency stage.

Incorrect Answers

B:

Neighbor discovery can succeed even when database exchange parameters prevent completion describes a neighboring protocol concern. In this case the controlling fact is oSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. A correct remediation would differentiate neighbor discovery from database synchronization message types and demonstrate: The packet trace shows each message at its appropriate adjacency stage.

C:

The proposed principle concerns another network fault: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. Here, oSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. The most direct correction is to differentiate neighbor discovery from database synchronization message types, confirmed by the packet trace shows each message at its appropriate adjacency stage.

D:

That result would be useful for a different failure, namely: A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. The current case specifically calls for: Differentiate neighbor discovery from database synchronization message types. The required observed result is: The packet trace shows each message at its appropriate adjacency stage.

Question 574

An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. What diagnosis and engineering response are most appropriate?

  1. Root issue: External OSPF redistribution must be reviewed for scope and scale. Correction: Restore explicit policy matching and confirm external route advertisements.
  2. Cause: Routing instances isolate routing tables unless explicit import or export mechanisms connect them. Response: Define the intended route-leaking boundary between the customer's instance and the master routing table.
  3. Diagnosis: OSPF identifies speakers by router ID, which must be unique inside a routing domain. Action: Assign distinct stable router IDs and clear stale protocol state using an approved procedure.
  4. Explanation: Neighbor discovery can succeed even when database exchange parameters prevent completion. Repair: Check MTU and interface compatibility and inspect neighbor-state details.

Explanation

Correct Answer

D:

This is the model-intended best choice because neighbor discovery can succeed even when database exchange parameters prevent completion. The targeted correction is to check MTU and interface compatibility and inspect neighbor-state details. Validate it by observing that the adjacency advances through database synchronization to Full.

Incorrect Answers

A:

Restore explicit policy matching and confirm external route advertisements is a relevant step for the separate scenario in which a BGP prefix redistribution into OSPF causes a flood of routes that were not in the approved design. It does not directly fix this case. Instead check MTU and interface compatibility and inspect neighbor-state details; verify: The adjacency advances through database synchronization to Full.

B:

The alternative addresses a provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table, 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 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: Neighbor discovery can succeed even when database exchange parameters prevent completion. Required validation: The adjacency advances through database synchronization to Full.

Question 575

A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. Which underlying Junos networking principle explains the failure?

  1. The key distinction is: Preference edits can change route selection without any interface outage.
  2. Protocol behavior: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links.
  3. Underlying principle: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone.
  4. Root design issue: OSPF route selection follows each router's synchronized topology view.

Explanation

Correct Answer

D:

Underlying cause: OSPF route selection follows each router's synchronized topology view. Corrective action: inspect link-state databases and SPF output on affected routers. Verify the outcome: A shared stable topology produces consistent path computation.

Incorrect Answers

A:

The proposed principle concerns another network fault: Preference edits can change route selection without any interface outage. Here, oSPF route selection follows each router's synchronized topology view. The most direct correction is to inspect link-state databases and SPF output on affected routers, confirmed by a shared stable topology produces consistent path computation.

B:

That result would be useful for a different failure, namely: An engineer expects a designated router to be elected on a point-to-point OSPF circuit. The current case specifically calls for: Inspect link-state databases and SPF output on affected routers. The required observed result is: A shared stable topology produces consistent path computation.

C:

This response would target a different source scenario: OSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path. It cannot establish the current acceptance requirement, which is: A shared stable topology produces consistent path computation. The relevant action is: Inspect link-state databases and SPF output on affected routers.

Question 576

A provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table. Which technical distinction best describes the observed symptom?

  1. The governing rule is: MPLS forwarding typically uses labels to select the next label-switched hop.
  2. The key distinction is: MPLS forwarding relies on label bindings and compatible next-hop state.
  3. Protocol behavior: An LSP cannot follow an unavailable required hop.
  4. Underlying principle: Unresolvable BGP next hops can make received routes unusable.

Explanation

Correct Answer

B:

Correct diagnosis: MPLS forwarding relies on label bindings and compatible next-hop state. The appropriate action is: Distinguish IP RIB entries from label forwarding information and LSP resolution. The follow-up evidence required is: The transit LSR selects an authorized outgoing label and interface.

Incorrect Answers

A:

This answer would be more suitable when an operator expects an MPLS label to represent an entire customer IP packet header, where the corrective action is to distinguish the MPLS shim label stack from the encapsulated payload. The failure here is different: MPLS forwarding relies on label bindings and compatible next-hop state. Required validation: The transit LSR selects an authorized outgoing label and interface.

C:

An LSP cannot follow an unavailable required hop describes a neighboring protocol concern. In this case the controlling fact is mPLS forwarding relies on label bindings and compatible next-hop state. A correct remediation would distinguish IP RIB entries from label forwarding information and LSP resolution and demonstrate: The transit LSR selects an authorized outgoing label and interface.

D:

The proposed principle concerns another network fault: Unresolvable BGP next hops can make received routes unusable. Here, mPLS forwarding relies on label bindings and compatible next-hop state. The most direct correction is to distinguish IP RIB entries from label forwarding information and LSP resolution, confirmed by the transit LSR selects an authorized outgoing label and interface.

Question 577

A multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. Which evidence would justify closing this troubleshooting case?

  1. Verification result: The session reaches Established only with the documented correct peer AS.
  2. Closeout evidence: The TCP session establishes across the intended transport path.
  3. Acceptance check: The backup LSP establishes on a permitted alternate path.
  4. The test confirms that the chosen path matches the configured preference and applicable attributes.

Explanation

Correct Answer

B:

The selected response implements the principle that eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. The engineer should review EBGP multihop transport reachability and session parameters. Successful confirmation means: The TCP session establishes across the intended transport path.

Incorrect Answers

A:

This response would target a different source scenario: A remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation. It cannot establish the current acceptance requirement, which is: The TCP session establishes across the intended transport path. The relevant action is: Review EBGP multihop transport reachability and session parameters.

C:

The alternative addresses an operator configured an explicit RSVP path through a link that is now administratively down, not the present root cause. Here the selected correction must reflect eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Test for: The TCP session establishes across the intended transport path.

D:

This answer would be more suitable when a router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count, where the corrective action is to trace the applicable BGP route-selection steps and local policies. The failure here is different: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Required validation: The TCP session establishes across the intended transport path.

Question 578

An MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. Which post-change observation most strongly confirms the correction?

  1. Expected observation: The missing client receives the correct next-hop-resolvable route.
  2. Verification result: The remote PE service route resolves over the designated LSP.
  3. Closeout evidence: A packet trace verifies the intended stack at the penultimate and egress hops.
  4. Acceptance check: The observed penultimate and egress labels agree with the supported LSP behavior.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Label stack changes can be legitimate parts of LSP forwarding design. Remedy: Verify whether PHP or explicit-null behavior is configured and intended. Proof: The observed penultimate and egress labels agree with the supported LSP behavior.

Incorrect Answers

A:

Route reflection can fail due to session or policy scope even when the route exists centrally describes a neighboring protocol concern. In this case the controlling fact is label stack changes can be legitimate parts of LSP forwarding design. A correct remediation would verify whether PHP or explicit-null behavior is configured and intended and demonstrate: The observed penultimate and egress labels agree with the supported LSP behavior.

B:

The proposed principle concerns another network fault: A labeled transport next hop must be available to carry the overlay service. Here, label stack changes can be legitimate parts of LSP forwarding design. The most direct correction is to verify whether PHP or explicit-null behavior is configured and intended, confirmed by the observed penultimate and egress labels agree with the supported LSP behavior.

C:

That result would be useful for a different failure, namely: A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. The current case specifically calls for: Verify whether PHP or explicit-null behavior is configured and intended. The required observed result is: The observed penultimate and egress labels agree with the supported LSP behavior.

Question 579

A BGP prefix redistribution into OSPF causes a flood of routes that were not in the approved design. Which combined repair and acceptance criterion is strongest?

  1. Control: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. Accepted result: The segment passes route and database tests with the expected neighbor states.
  2. Action: Restore explicit policy matching and confirm external route advertisements. Evidence: An LSA and route inspection finds only the authorized external prefix set.
  3. Repair: Review route preference before considering equivalent forwarding paths. Check: The selected path and its preference match the intended backup policy.
  4. Change: Assign distinct stable router IDs and clear stale protocol state using an approved procedure. Test: Each router is uniquely identified and the link-state database converges.

Explanation

Correct Answer

B:

Underlying cause: External OSPF redistribution must be reviewed for scope and scale. Corrective action: restore explicit policy matching and confirm external route advertisements. Verify the outcome: An LSA and route inspection finds only the authorized external prefix set.

Incorrect Answers

A:

The alternative addresses a broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately, not the present root cause. Here the selected correction must reflect external OSPF redistribution must be reviewed for scope and scale. Test for: An LSA and route inspection finds only the authorized external prefix set.

C:

This option overlooks the decisive condition. Its supporting principle is route preference determines the selected route before any multipath decision, while this scenario depends on external OSPF redistribution must be reviewed for scope and scale. Verify the correction with: An LSA and route inspection finds only the authorized external prefix set.

D:

OSPF identifies speakers by router ID, which must be unique inside a routing domain describes a neighboring protocol concern. In this case the controlling fact is external OSPF redistribution must be reviewed for scope and scale. A correct remediation would restore explicit policy matching and confirm external route advertisements and demonstrate: An LSA and route inspection finds only the authorized external prefix set.

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.

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