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 74

Question 730

One branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. What implementation step and validation result should be selected?

  1. Control: Compare ingress label imposition with transit LFIB and egress disposition. Accepted result: A hop-by-hop labeled test locates and corrects the failing label action.
  2. Action: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints. Evidence: The remote PE service route resolves over the designated LSP.
  3. Repair: Review route-reflector client and cluster design, including loop-prevention attributes. Check: A test prefix reaches permitted clients without cycling through reflector clusters.
  4. Change: Inspect label-switched next-hop resolution separately from generic IP reachability. Test: The labeled service route resolves after the intended LSP is restored.

Explanation

Correct Answer

A:

Because successful ordinary IP forwarding does not isolate MPLS packet forwarding faults, the best response is to compare ingress label imposition with transit LFIB and egress disposition. A reviewer can close the technical case only after confirming that a hop-by-hop labeled test locates and corrects the failing label action.

Incorrect Answers

B:

The proposed principle concerns another network fault: A labeled transport next hop must be available to carry the overlay service. Here, successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. The most direct correction is to compare ingress label imposition with transit LFIB and egress disposition, confirmed by a hop-by-hop labeled test locates and corrects the failing label action.

C:

That result would be useful for a different failure, namely: A route reflector advertises routes to the wrong clients after a change in group membership. The current case specifically calls for: Compare ingress label imposition with transit LFIB and egress disposition. The required observed result is: A hop-by-hop labeled test locates and corrects the failing label action.

D:

This response would target a different source scenario: A loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. It cannot establish the current acceptance requirement, which is: A hop-by-hop labeled test locates and corrects the failing label action. The relevant action is: Compare ingress label imposition with transit LFIB and egress disposition.

Question 731

An eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.
  2. Next step: Separate session liveness from prefix acceptance and RIB installation.
  3. Corrective action: Separate RSVP-signaled LSP functions from LDP label distribution.
  4. Apply this control: Review route-reflector client and cluster design, including loop-prevention attributes.

Explanation

Correct Answer

B:

Underlying cause: An Established BGP session can exist with zero accepted routes or unusable next hops. Corrective action: separate session liveness from prefix acceptance and RIB installation. Verify the outcome: Both neighbor state and selected prefix route evidence are verified independently.

Incorrect Answers

A:

The alternative addresses an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, not the present root cause. Here the selected correction must reflect an Established BGP session can exist with zero accepted routes or unusable next hops. Test for: Both neighbor state and selected prefix route evidence are verified independently.

C:

This option overlooks the decisive condition. Its supporting principle is rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability, while this scenario depends on an Established BGP session can exist with zero accepted routes or unusable next hops. Verify the correction with: Both neighbor state and selected prefix route evidence are verified independently.

D:

Route reflection relies on correct client boundaries and originator or cluster tracking describes a neighboring protocol concern. In this case the controlling fact is an Established BGP session can exist with zero accepted routes or unusable next hops. A correct remediation would separate session liveness from prefix acceptance and RIB installation and demonstrate: Both neighbor state and selected prefix route evidence are verified independently.

Question 732

A broadcast OSPF segment experiences repeated DR elections after interface priority changes. Which next action best resolves this observed routing or switching failure?

  1. Remediation: Review router priorities and the nonpreemptive properties of DR elections.
  2. Recommended change: Apply and verify supported route policy at the intended routing import or export boundary.
  3. Next step: Differentiate neighbor discovery from database synchronization message types.
  4. Corrective action: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: OSPF DR selection depends on eligible routers and the current election event. Remedy: Review router priorities and the nonpreemptive properties of DR elections. Proof: The elected DR and BDR align with the tested election conditions.

Incorrect Answers

B:

This response would target a different source scenario: An engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. It cannot establish the current acceptance requirement, which is: The elected DR and BDR align with the tested election conditions. The relevant action is: Review router priorities and the nonpreemptive properties of DR elections.

C:

Differentiate neighbor discovery from database synchronization message types is a relevant step for the separate scenario in which a technician treats an OSPF Link State Request as the same message as a Hello packet. It does not directly fix this case. Instead review router priorities and the nonpreemptive properties of DR elections; verify: The elected DR and BDR align with the tested election conditions.

D:

The alternative addresses an OSPF route appears longer than expected after failover because a backup link's cost was never verified, not the present root cause. Here the selected correction must reflect oSPF DR selection depends on eligible routers and the current election event. Test for: The elected DR and BDR align with the tested election conditions.

Question 733

After a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink. Which technical distinction best describes the observed symptom?

  1. Root design issue: Configuration intent must be verified against the actual elected spanning-tree root.
  2. The governing rule is: Untagged frame classification is local to the receiving interface.
  3. The key distinction is: MAC table visibility alone does not prove trunk authorization for every VLAN.
  4. Protocol behavior: Junos candidate configuration changes are not active until committed.

Explanation

Correct Answer

C:

Underlying cause: MAC table visibility alone does not prove trunk authorization for every VLAN. Corrective action: inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. Verify the outcome: Separate tagged tests pass in both permitted VLANs.

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 mAC table visibility alone does not prove trunk authorization for every VLAN. Verify the correction with: Separate tagged tests pass in both permitted VLANs.

B:

Untagged frame classification is local to the receiving interface describes a neighboring protocol concern. In this case the controlling fact is mAC table visibility alone does not prove trunk authorization for every VLAN. A correct remediation would inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning and demonstrate: Separate tagged tests pass in both permitted VLANs.

D:

That result would be useful for a different failure, namely: A virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed. The current case specifically calls for: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. The required observed result is: Separate tagged tests pass in both permitted VLANs.

Question 734

A Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected. What is the most defensible network engineering correction?

  1. Corrective action: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.
  2. Apply this control: Match loop, BPDU and root protection to their different fault conditions.
  3. Remediation: Enable the appropriate spanning-tree protection and verify the blocked redundant path.
  4. Recommended change: Verify VLAN or bridge-domain membership and its L3 IRB binding.

Explanation

Correct Answer

C:

Because spanning tree prevents forwarding loops by selecting a loop-free active topology, the best response is to enable the appropriate spanning-tree protection and verify the blocked redundant path. A reviewer can close the technical case only after confirming that a topology test leaves one redundant path nonforwarding and traffic remains reachable.

Incorrect Answers

A:

Inspect per-VLAN STP instances and configured priorities, not just a global STP summary is a relevant step for the separate scenario in which several VLANs have unexpected root placement under VSTP after port membership changes. It does not directly fix this case. Instead enable the appropriate spanning-tree protection and verify the blocked redundant path; verify: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

B:

The alternative addresses an engineer uses loop protection as if it served the same purpose as BPDU protection on every port, not the present root cause. Here the selected correction must reflect spanning tree prevents forwarding loops by selecting a loop-free active topology. Test for: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

D:

This option overlooks the decisive condition. Its supporting principle is integrated routing bridges a defined L2 domain into an L3 interface when correctly associated, while this scenario depends on spanning tree prevents forwarding loops by selecting a loop-free active topology. Verify the correction with: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

Question 735

An iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone. What action-and-test pairing directly resolves the case?

  1. Control: Confirm the configured local and peer AS values with the authoritative design. Accepted result: The session reaches Established only with the documented correct peer AS.
  2. Action: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior. Evidence: The internal router resolves the next hop and installs the intended route.
  3. Repair: Review hierarchical OSPF backbone attachment and area border placement. Check: The planned ABR topology provides verified interarea reachability.
  4. Change: Investigate AS-path loop prevention rather than overriding it without risk review. Test: The route is accepted only after the AS-path design is corrected.

Explanation

Correct Answer

B:

The critical observation is: Unresolvable BGP next hops can make received routes unusable. Correct it by taking this action: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior. Confirm the outcome with: The internal router resolves the next hop and installs the intended route.

Incorrect Answers

A:

The proposed principle concerns another network fault: BGP OPEN negotiation includes AS identity that must match peering intent. Here, unresolvable BGP next hops can make received routes unusable. The most direct correction is to restore appropriate IGP next-hop reachability or approved next-hop-self behavior, confirmed by the internal router resolves the next hop and installs the intended route.

C:

This response would target a different source scenario: A router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. It cannot establish the current acceptance requirement, which is: The internal router resolves the next hop and installs the intended route. The relevant action is: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.

D:

Investigate AS-path loop prevention rather than overriding it without risk review is a relevant step for the separate scenario in which a provider advertises a customer prefix with its own AS number already present in the return AS path. It does not directly fix this case. Instead restore appropriate IGP next-hop reachability or approved next-hop-self behavior; verify: The internal router resolves the next hop and installs the intended route.

Question 736

An operator expects an MPLS label to represent an entire customer IP packet header. Which combined repair and acceptance criterion is strongest?

  1. Implement: Verify IP reachability, routing instance context, TCP transport and session authentication. Verify: The TCP peering session reaches Established and remains stable.
  2. Control: Compare label bindings with the active IGP next hop and installed forwarding entries. Accepted result: The selected LDP label uses a live next-hop interface after convergence.
  3. Action: Distinguish the MPLS shim label stack from the encapsulated payload. Evidence: A packet decode identifies label fields separately from the carried IP packet.
  4. Repair: Separate RSVP-signaled LSP functions from LDP label distribution. Check: The chosen protocol establishes the intended type of LSP.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: MPLS forwarding typically uses labels to select the next label-switched hop. Remedy: Distinguish the MPLS shim label stack from the encapsulated payload. Proof: A packet decode identifies label fields separately from the carried IP packet.

Incorrect Answers

A:

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: MPLS forwarding typically uses labels to select the next label-switched hop. Required validation: A packet decode identifies label fields separately from the carried IP packet.

B:

This option overlooks the decisive condition. Its supporting principle is a stale label binding cannot compensate for unusable transport forwarding, 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.

D:

The proposed principle concerns another network fault: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. 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.

Question 737

An LDP binding exists for a remote destination but the forwarding interface points to a failed next hop. Which cause-and-remedy pairing reflects the observed problem?

  1. Explanation: A stale label binding cannot compensate for unusable transport forwarding. Repair: Compare label bindings with the active IGP next hop and installed forwarding entries.
  2. Fault mechanism: Unresolvable BGP next hops can make received routes unusable. Remediation: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.
  3. Root issue: A labeled transport next hop must be available to carry the overlay service. Correction: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.
  4. Cause: Different segment types express different routing or link steering semantics. Response: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions.

Explanation

Correct Answer

A:

Underlying cause: A stale label binding cannot compensate for unusable transport forwarding. Corrective action: compare label bindings with the active IGP next hop and installed forwarding entries. Verify the outcome: The selected LDP label uses a live next-hop interface after convergence.

Incorrect Answers

B:

Restore appropriate IGP next-hop reachability or approved next-hop-self behavior is a relevant step for the separate scenario in which an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone. It does not directly fix this case. Instead compare label bindings with the active IGP next hop and installed forwarding entries; verify: The selected LDP label uses a live next-hop interface after convergence.

C:

The alternative addresses a route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path, not the present root cause. Here the selected correction must reflect a stale label binding cannot compensate for unusable transport forwarding. Test for: The selected LDP label uses a live next-hop interface after convergence.

D:

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: A stale label binding cannot compensate for unusable transport forwarding. Required validation: The selected LDP label uses a live next-hop interface after convergence.

Question 738

An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. What should the operations engineer do first to address the stated fault?

  1. Apply this control: Revisit additive path cost and verify SPF outcomes across alternative links.
  2. Remediation: Remove the incompatible local mode and validate the supported HA configuration.
  3. Recommended change: Evaluate BFD liveness detection with the associated routing protocol.
  4. Next step: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Remedy: Evaluate nonstop bridging together with the supported Routing Engine redundancy design. Proof: An authorized switchover maintains bridge control state and service reachability.

Incorrect Answers

A:

OSPF normally prefers the least accumulated metric to a destination describes a neighboring protocol concern. In this case the controlling fact is nonstop bridging protects relevant Layer 2 control-protocol state during switchover. A correct remediation would evaluate nonstop bridging together with the supported Routing Engine redundancy design and demonstrate: An authorized switchover maintains bridge control state and service reachability.

B:

The proposed principle concerns another network fault: Conflicting local GR and NSR configuration must be resolved before activation. Here, nonstop bridging protects relevant Layer 2 control-protocol state during switchover. The most direct correction is to evaluate nonstop bridging together with the supported Routing Engine redundancy design, confirmed by an authorized switchover maintains bridge control state and service reachability.

C:

That result would be useful for a different failure, namely: A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. The current case specifically calls for: Evaluate nonstop bridging together with the supported Routing Engine redundancy design. The required observed result is: An authorized switchover maintains bridge control state and service reachability.

Question 739

A segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. What is the most defensible network engineering correction?

  1. Corrective action: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.
  2. Apply this control: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  3. Remediation: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions.
  4. Recommended change: Map inbound and outbound policy points and confirm the intended communities.

Explanation

Correct Answer

C:

The selected response implements the principle that different segment types express different routing or link steering semantics. The engineer should distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. Successful confirmation means: A segment trace follows the desired prefix or explicit adjacency.

Incorrect Answers

A:

The alternative addresses a route to a service PE resolves in inet.0 but cannot resolve to the expected MPLS transport path, not the present root cause. Here the selected correction must reflect different segment types express different routing or link steering semantics. Test for: A segment trace follows the desired prefix or explicit adjacency.

B:

This answer would be more suitable when a penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label, where the corrective action is to recognize penultimate-hop popping as an allowed LSP forwarding behavior. The failure here is different: Different segment types express different routing or link steering semantics. Required validation: A segment trace follows the desired prefix or explicit adjacency.

D:

BGP group inheritance and policy direction govern which advertisements are modified describes a neighboring protocol concern. In this case the controlling fact is different segment types express different routing or link steering semantics. A correct remediation would distinguish prefix-based segment reachability from adjacency-specific forwarding instructions and demonstrate: A segment trace follows the desired prefix or explicit adjacency.

Question 740

A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. What remediation is most directly applicable?

  1. Next step: Review martian-address treatment and justify any carefully scoped exception.
  2. Corrective action: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples.
  3. Apply this control: Restore the intended route preferences and check selected forwarding next hops.
  4. Remediation: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

Explanation

Correct Answer

B:

Because overlapping address classification makes precise route-filter and policy terms essential, the best response is to tighten the filter match and verify the next-table lookup with explicit positive and negative examples. A reviewer can close the technical case only after confirming that only the subscriber's approved traffic enters the alternate routing instance.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. The current case specifically calls for: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples. The required observed result is: Only the subscriber's approved traffic enters the alternate routing instance.

C:

Restore the intended route preferences and check selected forwarding next hops is a relevant step for the separate scenario in which a backup path becomes primary after a preference edit even though the design called for failover only. It does not directly fix this case. Instead tighten the filter match and verify the next-table lookup with explicit positive and negative examples; verify: Only the subscriber's approved traffic enters the alternate routing instance.

D:

The alternative addresses an OSPF route appears longer than expected after failover because a backup link's cost was never verified, not the present root cause. Here the selected correction must reflect overlapping address classification makes precise route-filter and policy terms essential. Test for: Only the subscriber's approved traffic enters the alternate routing instance.

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