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 53

Question 520

A network design assumes RSVP and LDP use identical path signaling and traffic engineering controls. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: A capture identifies the label used at each transit stage.
  2. The test confirms that the chosen protocol establishes the intended type of LSP.
  3. Expected observation: The backup LSP establishes on a permitted alternate path.
  4. Verification result: A test packet follows the expected active forwarding next hop and interface.

Explanation

Correct Answer

B:

Correct diagnosis: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. The appropriate action is: Separate RSVP-signaled LSP functions from LDP label distribution. The follow-up evidence required is: The chosen protocol establishes the intended type of LSP.

Incorrect Answers

A:

This answer would be more suitable when a router sees multiple labels on a packet but an engineer only examines the innermost label when troubleshooting transit transport, where the corrective action is to inspect the full MPLS label stack and outgoing label operation. The failure here is different: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Required validation: The chosen protocol establishes the intended type of LSP.

C:

An LSP cannot follow an unavailable required hop describes a neighboring protocol concern. In this case the controlling fact is rSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. A correct remediation would separate RSVP-signaled LSP functions from LDP label distribution and demonstrate: The chosen protocol establishes the intended type of LSP.

D:

The proposed principle concerns another network fault: Forwarding-table and interface evidence localize faults beyond RIB reachability. 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.

Question 521

A trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. Which evidence would justify closing this troubleshooting case?

  1. Closeout evidence: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.
  2. Acceptance check: A tagged test frame reaches the approved remote port in the same domain.
  3. The test confirms that a packet capture shows the intended outer and inner VLAN tags end to end.
  4. Expected observation: A link-failure test shows the supported rapid role transition.

Explanation

Correct Answer

A:

Underlying cause: A trunk carries only its configured authorized VLANs. Corrective action: review allowed VLAN membership on both trunk endpoints. Verify the outcome: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Incorrect Answers

B:

Trace frame classification and virtual-switch bridge-domain association is a relevant step for the separate scenario in which a port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. It does not directly fix this case. Instead review allowed VLAN membership on both trunk endpoints; verify: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

C:

The alternative addresses a service provider adds a second VLAN tag to customer frames but the downstream switch treats it as an ordinary single tag, not the present root cause. Here the selected correction must reflect a trunk carries only its configured authorized VLANs. Test for: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

D:

This answer would be more suitable when two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP, where the corrective action is to compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. The failure here is different: A trunk carries only its configured authorized VLANs. Required validation: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.

Question 522

An IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Check MTU and interface compatibility and inspect neighbor-state details. Check: The adjacency advances through database synchronization to Full.
  2. Change: Rehearse the failure and inspect active next hops and IS-IS route changes. Test: The backup next hop resolves and carries test traffic after the primary link fails.
  3. Implement: Verify compatible area membership or use the designed Level 2 boundary. Verify: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.
  4. Control: Inspect link quality, interface settings and DIS state before forcing election behavior. Accepted result: A stable neighbor and LAN LSP remain after link faults are corrected.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. Remedy: Inspect link quality, interface settings and DIS state before forcing election behavior. Proof: A stable neighbor and LAN LSP remain after link faults are corrected.

Incorrect Answers

A:

Neighbor discovery can succeed even when database exchange parameters prevent completion describes a neighboring protocol concern. In this case the controlling fact is frequent topology churn can stem from physical and configuration issues rather than DIS alone. A correct remediation would inspect link quality, interface settings and DIS state before forcing election behavior and demonstrate: A stable neighbor and LAN LSP remain after link faults are corrected.

B:

The proposed principle concerns another network fault: A backup path requires functional forwarding, not merely topology presence. Here, frequent topology churn can stem from physical and configuration issues rather than DIS alone. The most direct correction is to inspect link quality, interface settings and DIS state before forcing election behavior, confirmed by a stable neighbor and LAN LSP remain after link faults are corrected.

C:

That result would be useful for a different failure, namely: An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. The current case specifically calls for: Inspect link quality, interface settings and DIS state before forcing election behavior. The required observed result is: A stable neighbor and LAN LSP remain after link faults are corrected.

Question 523

Two equal-cost next hops exist but a customer assumes every successive packet must alternate between links. What observable result most directly verifies the intended configuration?

  1. Expected observation: The selected path and its preference match the intended backup policy.
  2. Verification result: The static route becomes active after the actual next-hop fault is corrected.
  3. Closeout evidence: A controlled flow test verifies the selected load-sharing behavior.
  4. Acceptance check: A shared stable topology produces consistent path computation.

Explanation

Correct Answer

C:

The selected response implements the principle that multiple eligible forwarding next hops do not guarantee per-packet round-robin use. The engineer should distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane. Successful confirmation means: A controlled flow test verifies the selected load-sharing behavior.

Incorrect Answers

A:

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 multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Test for: A controlled flow test verifies the selected load-sharing behavior.

B:

This answer would be more suitable when after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, where the corrective action is to inspect the configuration, active route state and next-hop reachability before changing preference. The failure here is different: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Required validation: A controlled flow test verifies the selected load-sharing behavior.

D:

OSPF route selection follows each router's synchronized topology view describes a neighboring protocol concern. In this case the controlling fact is multiple eligible forwarding next hops do not guarantee per-packet round-robin use. A correct remediation would distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane and demonstrate: A controlled flow test verifies the selected load-sharing behavior.

Question 524

A small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added. What action-and-test pairing directly resolves the case?

  1. Control: Differentiate community tags from reachability and forwarding attributes. Accepted result: Policy based on the intended community alters admission or preference as designed.
  2. Action: Evaluate route reflection with defined cluster and client boundaries. Evidence: The route-reflector design distributes approved prefixes without unintended loops.
  3. Repair: Verify compatible network and Hello parameters including mask where applicable. Check: A controlled neighbor check reaches Full after configuration correction.
  4. Change: Compare negotiated timers and protocol logs with routing-engine and packet conditions. Test: The restored session remains stable while meeting the approved detection target.

Explanation

Correct Answer

B:

Because iBGP scaling mechanisms reduce the full-mesh session requirement, the best response is to evaluate route reflection with defined cluster and client boundaries. A reviewer can close the technical case only after confirming that the route-reflector design distributes approved prefixes without unintended loops.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An engineer treats a BGP community value as a standalone forwarding next hop. The current case specifically calls for: Evaluate route reflection with defined cluster and client boundaries. The required observed result is: The route-reflector design distributes approved prefixes without unintended loops.

C:

Verify compatible network and Hello parameters including mask where applicable is a relevant step for the separate scenario in which a router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. It does not directly fix this case. Instead evaluate route reflection with defined cluster and client boundaries; verify: The route-reflector design distributes approved prefixes without unintended loops.

D:

The alternative addresses an engineer modifies BGP keepalive or hold timers and the session flaps during CPU pressure, not the present root cause. Here the selected correction must reflect iBGP scaling mechanisms reduce the full-mesh session requirement. Test for: The route-reflector design distributes approved prefixes without unintended loops.

Question 525

A customer overlay fails across an MPLS core only for one service label. What is the primary routing or switching concept illustrated?

  1. The key distinction is: BGP selection is policy-driven and is not equivalent to IGP least-hop routing.
  2. Protocol behavior: LDP signaling depends on the routing and transport state of its endpoints.
  3. Underlying principle: MPLS forwarding typically uses labels to select the next label-switched hop.
  4. Root design issue: A healthy transport LSP does not guarantee a correct overlay label mapping.

Explanation

Correct Answer

D:

The selected response implements the principle that a healthy transport LSP does not guarantee a correct overlay label mapping. The engineer should inspect outer transport and inner service label handling separately. Successful confirmation means: The test service label is retained and accepted at the target PE.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is bGP selection is policy-driven and is not equivalent to IGP least-hop routing, while this scenario depends on a healthy transport LSP does not guarantee a correct overlay label mapping. Verify the correction with: The test service label is retained and accepted at the target PE.

B:

LDP signaling depends on the routing and transport state of its endpoints describes a neighboring protocol concern. In this case the controlling fact is a healthy transport LSP does not guarantee a correct overlay label mapping. A correct remediation would inspect outer transport and inner service label handling separately and demonstrate: The test service label is retained and accepted at the target PE.

C:

The proposed principle concerns another network fault: MPLS forwarding typically uses labels to select the next label-switched hop. Here, a healthy transport LSP does not guarantee a correct overlay label mapping. The most direct correction is to inspect outer transport and inner service label handling separately, confirmed by the test service label is retained and accepted at the target PE.

Question 526

An Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. What operational check demonstrates that the intended outcome occurred?

  1. Closeout evidence: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.
  2. Acceptance check: A capture shows the expected outer service tag between provider edges.
  3. The test confirms that the test frame is accepted only under the approved tagging plan.
  4. Expected observation: The ring converges with no forwarding loop and sustained connectivity.

Explanation

Correct Answer

C:

Because customer-facing encapsulation must match the traffic format at ingress, the best response is to set appropriate port mode and tag handling at the service edge. A reviewer can close the technical case only after confirming that the test frame is accepted only under the approved tagging plan.

Incorrect Answers

A:

Review allowed VLAN membership on both trunk endpoints is a relevant step for the separate scenario in which a trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. It does not directly fix this case. Instead set appropriate port mode and tag handling at the service edge; verify: The test frame is accepted only under the approved tagging plan.

B:

The alternative addresses tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing, not the present root cause. Here the selected correction must reflect customer-facing encapsulation must match the traffic format at ingress. Test for: The test frame is accepted only under the approved tagging plan.

D:

This option overlooks the decisive condition. Its supporting principle is loop prevention depends on compatible STP participation across redundant Ethernet links, while this scenario depends on customer-facing encapsulation must match the traffic format at ingress. Verify the correction with: The test frame is accepted only under the approved tagging plan.

Question 527

An engineer modifies BGP keepalive or hold timers and the session flaps during CPU pressure. Which next action best resolves this observed routing or switching failure?

  1. Apply this control: Check MTU and interface compatibility and inspect neighbor-state details.
  2. Remediation: Compare negotiated timers and protocol logs with routing-engine and packet conditions.
  3. Recommended change: Confirm the configured local and peer AS values with the authoritative design.
  4. Next step: Review EBGP multihop transport reachability and session parameters.

Explanation

Correct Answer

B:

The critical observation is: Aggressive liveness settings can magnify loss or processing delays. Correct it by taking this action: Compare negotiated timers and protocol logs with routing-engine and packet conditions. Confirm the outcome with: The restored session remains stable while meeting the approved detection target.

Incorrect Answers

A:

The proposed principle concerns another network fault: Neighbor discovery can succeed even when database exchange parameters prevent completion. Here, aggressive liveness settings can magnify loss or processing delays. The most direct correction is to compare negotiated timers and protocol logs with routing-engine and packet conditions, confirmed by the restored session remains stable while meeting the approved detection target.

C:

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 restored session remains stable while meeting the approved detection target. The relevant action is: Compare negotiated timers and protocol logs with routing-engine and packet conditions.

D:

Review EBGP multihop transport reachability and session parameters is a relevant step for the separate scenario in which a multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. It does not directly fix this case. Instead compare negotiated timers and protocol logs with routing-engine and packet conditions; verify: The restored session remains stable while meeting the approved detection target.

Question 528

An engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. What is the primary routing or switching concept illustrated?

  1. Underlying principle: A learned LSP does not ensure a destination is selected into the active routing table.
  2. Root design issue: BGP OPEN negotiation includes AS identity that must match peering intent.
  3. The governing rule is: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links.
  4. The key distinction is: IS-IS path selection is based on link-state topology and metrics.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Remedy: Differentiate multiaccess DIS election from point-to-point adjacency behavior. Proof: A point-to-point link reaches the expected adjacency state without DIS election.

Incorrect Answers

A:

This answer would be more suitable when an IS-IS route disappears after a policy update while the LSP database still contains the topology, where the corrective action is to inspect route import policy and forwarding selection separately from LSP presence. The failure here is different: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Required validation: A point-to-point link reaches the expected adjacency state without DIS election.

B:

This option overlooks the decisive condition. Its supporting principle is bGP OPEN negotiation includes AS identity that must match peering intent, while this scenario depends on the IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Verify the correction with: A point-to-point link reaches the expected adjacency state without DIS election.

D:

The proposed principle concerns another network fault: IS-IS path selection is based on link-state topology and metrics. Here, the IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. The most direct correction is to differentiate multiaccess DIS election from point-to-point adjacency behavior, confirmed by a point-to-point link reaches the expected adjacency state without DIS election.

Question 529

A route reflector receives a new branch prefix but one iBGP client never learns it. What implementation step and validation result should be selected?

  1. Control: Evaluate route reflection with defined cluster and client boundaries. Accepted result: The route-reflector design distributes approved prefixes without unintended loops.
  2. Action: Compare ingress label imposition with transit LFIB and egress disposition. Evidence: A hop-by-hop labeled test locates and corrects the failing label action.
  3. Repair: Check client definitions, route-reflector session state and export policy. Check: The missing client receives the correct next-hop-resolvable route.
  4. Change: Verify IP reachability, routing instance context, TCP transport and session authentication. Test: The TCP peering session reaches Established and remains stable.

Explanation

Correct Answer

C:

The critical observation is: Route reflection can fail due to session or policy scope even when the route exists centrally. Correct it by taking this action: Check client definitions, route-reflector session state and export policy. Confirm the outcome with: The missing client receives the correct next-hop-resolvable route.

Incorrect Answers

A:

This response would target a different source scenario: A small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added. It cannot establish the current acceptance requirement, which is: The missing client receives the correct next-hop-resolvable route. The relevant action is: Check client definitions, route-reflector session state and export policy.

B:

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 check client definitions, route-reflector session state and export policy; verify: The missing client receives the correct next-hop-resolvable route.

D:

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

Question 530

An iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone. What remediation is most directly applicable?

  1. Recommended change: Distinguish internal LSAs from externally originated route information.
  2. Next step: Trace the applicable BGP route-selection steps and local policies.
  3. Corrective action: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior.
  4. Apply this control: Confirm the configured local and peer AS values with the authoritative design.

Explanation

Correct Answer

C:

Correct diagnosis: Unresolvable BGP next hops can make received routes unusable. The appropriate action is: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior. The follow-up evidence required is: The internal router resolves the next hop and installs the intended route.

Incorrect Answers

A:

OSPF route type and LSA scope depend on where routing information originates describes a neighboring protocol concern. In this case the controlling fact is unresolvable BGP next hops can make received routes unusable. A correct remediation would restore appropriate IGP next-hop reachability or approved next-hop-self behavior and demonstrate: The internal router resolves the next hop and installs the intended route.

B:

The proposed principle concerns another network fault: BGP selection is policy-driven and is not equivalent to IGP least-hop routing. 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.

D:

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

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