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 2

Question 10

A provider STP domain changes root when a customer sends superior BPDUs from an access port. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Traditional spanning-tree root election favors the lowest bridge ID.
  2. Protocol behavior: A trunk carries only its configured authorized VLANs.
  3. Underlying principle: Loop prevention depends on compatible STP participation across redundant Ethernet links.
  4. Root design issue: Customer control traffic must not displace the authorized provider root.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Customer control traffic must not displace the authorized provider root. Remedy: Apply supported root protection at the appropriate customer-facing boundary. Proof: A superior BPDU test preserves the intended root with a logged protective state.

Incorrect Answers

A:

Traditional spanning-tree root election favors the lowest bridge ID describes a neighboring protocol concern. In this case the controlling fact is customer control traffic must not displace the authorized provider root. A correct remediation would apply supported root protection at the appropriate customer-facing boundary and demonstrate: A superior BPDU test preserves the intended root with a logged protective state.

B:

The proposed principle concerns another network fault: A trunk carries only its configured authorized VLANs. Here, customer control traffic must not displace the authorized provider root. The most direct correction is to apply supported root protection at the appropriate customer-facing boundary, confirmed by a superior BPDU test preserves the intended root with a logged protective state.

C:

That result would be useful for a different failure, namely: A new redundant uplink produces a broadcast storm on an access VLAN. The current case specifically calls for: Apply supported root protection at the appropriate customer-facing boundary. The required observed result is: A superior BPDU test preserves the intended root with a logged protective state.

Question 11

A switch operator treats the highest bridge ID as the guaranteed STP root. 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: The intended device is root under the tested priorities and tie-breakers.
  3. The test confirms that the ring converges with no forwarding loop and sustained connectivity.
  4. Expected observation: The alternate port transitions appropriately after the root path fails.

Explanation

Correct Answer

B:

Underlying cause: Traditional spanning-tree root election favors the lowest bridge ID. Corrective action: review root bridge priority and MAC-based bridge identifier comparison. Verify the outcome: The intended device is root under the tested priorities and tie-breakers.

Incorrect Answers

A:

The alternative addresses a trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch, not the present root cause. Here the selected correction must reflect traditional spanning-tree root election favors the lowest bridge ID. Test for: The intended device is root under the tested priorities and tie-breakers.

C:

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 traditional spanning-tree root election favors the lowest bridge ID. Verify the correction with: The intended device is root under the tested priorities and tie-breakers.

D:

A redundant alternate path can remain nonforwarding until a failure changes roles describes a neighboring protocol concern. In this case the controlling fact is traditional spanning-tree root election favors the lowest bridge ID. A correct remediation would review root bridge priority and MAC-based bridge identifier comparison and demonstrate: The intended device is root under the tested priorities and tie-breakers.

Question 12

A small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added. Which evidence would justify closing this troubleshooting case?

  1. Verification result: The route-reflector design distributes approved prefixes without unintended loops.
  2. Closeout evidence: Policy based on the intended community alters admission or preference as designed.
  3. Acceptance check: The point-to-point adjacency forms without an unnecessary DR election.
  4. The test confirms that the unauthorized customer receives no leaked prefixes in a route advertisement check.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: iBGP scaling mechanisms reduce the full-mesh session requirement. Remedy: Evaluate route reflection with defined cluster and client boundaries. Proof: The route-reflector design distributes approved prefixes without unintended loops.

Incorrect Answers

B:

This response would target a different source scenario: An engineer treats a BGP community value as a standalone forwarding next hop. It cannot establish the current acceptance requirement, which is: The route-reflector design distributes approved prefixes without unintended loops. The relevant action is: Evaluate route reflection with defined cluster and client boundaries.

C:

Select the correct network-type behavior and inspect the neighbor-state model is a relevant step for the separate scenario in which an engineer expects a designated router to be elected on a point-to-point OSPF circuit. 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 one customer’s new prefixes are advertised to a second unrelated customer via a shared export group, 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 13

A GRE design includes a virtual tunnel interface but omits routable IPv4 underlay access to the remote endpoint. Which combined repair and acceptance criterion is strongest?

  1. Action: Treat tunnel decapsulation as a routing and security boundary. Evidence: Only authorized customer prefixes enter or leave the decapsulated routing context.
  2. Repair: Verify reachability between tunnel source and destination addresses. Check: The remote tunnel endpoint is reachable through the intended underlay.
  3. Change: Review reservation constraints and available resources rather than resetting all label sessions. Test: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  4. Implement: Test effective MTU and path MTU discovery across the encapsulated route. Verify: A controlled large-payload test succeeds after MTU or MSS adjustment.

Explanation

Correct Answer

B:

The case turns on the distinction that tunnel interfaces depend on a working underlay path between endpoints. Apply this concrete engineering step: Verify reachability between tunnel source and destination addresses. An acceptable verification outcome is: The remote tunnel endpoint is reachable through the intended underlay.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is encapsulation does not replace explicit customer route filtering and access policy, while this scenario depends on tunnel interfaces depend on a working underlay path between endpoints. Verify the correction with: The remote tunnel endpoint is reachable through the intended underlay.

C:

The proposed principle concerns another network fault: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Here, tunnel interfaces depend on a working underlay path between endpoints. The most direct correction is to verify reachability between tunnel source and destination addresses, confirmed by the remote tunnel endpoint is reachable through the intended underlay.

D:

That result would be useful for a different failure, namely: Small probes pass through GRE but large customer packets are intermittently dropped. The current case specifically calls for: Verify reachability between tunnel source and destination addresses. The required observed result is: The remote tunnel endpoint is reachable through the intended underlay.

Question 14

A provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table. Which post-change observation most strongly confirms the correction?

  1. The test confirms that the labeled service route resolves after the intended LSP is restored.
  2. Expected observation: The receiving instance shows the correct route and installed next hop after correction.
  3. Verification result: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  4. Closeout evidence: The transit LSR selects an authorized outgoing label and interface.

Explanation

Correct Answer

D:

This is the model-intended best choice because mPLS forwarding relies on label bindings and compatible next-hop state. The targeted correction is to distinguish IP RIB entries from label forwarding information and LSP resolution. Validate it by observing that the transit LSR selects an authorized outgoing label and interface.

Incorrect Answers

A:

Inspect label-switched next-hop resolution separately from generic IP reachability is a relevant step for the separate scenario in which a loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. It does not directly fix this case. Instead distinguish IP RIB entries from label forwarding information and LSP resolution; verify: The transit LSR selects an authorized outgoing label and interface.

B:

The alternative addresses a RIB group leak forwards a VPN service toward the wrong next hop after a route update, not the present root cause. Here the selected correction must reflect mPLS forwarding relies on label bindings and compatible next-hop state. Test for: The transit LSR selects an authorized outgoing label and interface.

C:

This answer would be more suitable when an RSVP-signaled LSP enters a failed state after a link bandwidth change, where the corrective action is to review reservation constraints and available resources rather than resetting all label sessions. 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.

Question 15

An Ethernet provider transit receives an untagged subscriber frame on a service meant for tagged traffic. Which cause-and-remedy pairing reflects the observed problem?

  1. Fault mechanism: A customer VLAN tag can be scoped by access interface and provider service context. Remediation: Separate provider service identification from customer VLAN identifiers.
  2. Root issue: Customer-facing encapsulation must match the traffic format at ingress. Correction: Set appropriate port mode and tag handling at the service edge.
  3. Cause: Port mode determines which customer frames are tagged or untagged at the boundary. Response: Distinguish access port traffic from trunk tagging behavior.
  4. Diagnosis: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Action: Differentiate forwarding continuity under GRES from routing-protocol state preservation.

Explanation

Correct Answer

B:

The critical observation is: Customer-facing encapsulation must match the traffic format at ingress. Correct it by taking this action: Set appropriate port mode and tag handling at the service edge. Confirm the outcome with: The test frame is accepted only under the approved tagging plan.

Incorrect Answers

A:

The proposed principle concerns another network fault: A customer VLAN tag can be scoped by access interface and provider service context. Here, customer-facing encapsulation must match the traffic format at ingress. The most direct correction is to set appropriate port mode and tag handling at the service edge, confirmed by the test frame is accepted only under the approved tagging plan.

C:

This response would target a different source scenario: An access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame. It cannot establish the current acceptance requirement, which is: The test frame is accepted only under the approved tagging plan. The relevant action is: Set appropriate port mode and tag handling at the service edge.

D:

Differentiate forwarding continuity under GRES from routing-protocol state preservation is a relevant step for the separate scenario in which a dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature. 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.

Question 16

A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. Which corrective action and confirmation pair is most appropriate?

  1. Change: Recognize penultimate-hop popping as an allowed LSP forwarding behavior. Test: A packet trace verifies the intended stack at the penultimate and egress hops.
  2. Implement: Review segment identifiers and forwarding under SR-MPLS. Verify: A test packet follows its segment list through installed SR forwarding.
  3. Control: Inspect the incoming label, outgoing label and interface on each affected LSR. Accepted result: The repaired hop has the expected swap operation and carries a test packet.
  4. Action: Compare installed forwarding entries with interface operational status and adjacency resolution. Evidence: A test packet follows the expected active forwarding next hop and interface.

Explanation

Correct Answer

A:

This is the model-intended best choice because an upstream LSR can remove a label before the egress in an appropriate PHP design. The targeted correction is to recognize penultimate-hop popping as an allowed LSP forwarding behavior. Validate it by observing that a packet trace verifies the intended stack at the penultimate and egress hops.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit, while this scenario depends on an upstream LSR can remove a label before the egress in an appropriate PHP design. Verify the correction with: A packet trace verifies the intended stack at the penultimate and egress hops.

C:

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 upstream LSR can remove a label before the egress in an appropriate PHP design. A correct remediation would recognize penultimate-hop popping as an allowed LSP forwarding behavior and demonstrate: A packet trace verifies the intended stack at the penultimate and egress hops.

D:

The proposed principle concerns another network fault: Forwarding-table and interface evidence localize faults beyond RIB reachability. Here, an upstream LSR can remove a label before the egress in an appropriate PHP design. The most direct correction is to recognize penultimate-hop popping as an allowed LSP forwarding behavior, confirmed by a packet trace verifies the intended stack at the penultimate and egress hops.

Question 17

An operator plans provider bridging but assumes the customer's C-tag is removed from every frame. What diagnosis and engineering response are most appropriate?

  1. Diagnosis: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Action: Separate customer bridge domains and validate virtual-switch membership.
  2. Explanation: Customer-facing encapsulation must match the traffic format at ingress. Repair: Set appropriate port mode and tag handling at the service edge.
  3. Fault mechanism: Customer control traffic must not displace the authorized provider root. Remediation: Apply supported root protection at the appropriate customer-facing boundary.
  4. Root issue: Provider bridging can carry customer VLAN tags inside a provider service tag. Correction: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design.

Explanation

Correct Answer

D:

The case turns on the distinction that provider bridging can carry customer VLAN tags inside a provider service tag. Apply this concrete engineering step: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. An acceptable verification outcome is: An ingress-to-egress capture confirms the intended stacked tagging.

Incorrect Answers

A:

This response would target a different source scenario: A customer bridge-domain spans two isolated customers due to reusing a virtual switch without tenant boundaries. It cannot establish the current acceptance requirement, which is: An ingress-to-egress capture confirms the intended stacked tagging. The relevant action is: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design.

B:

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 clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design; verify: An ingress-to-egress capture confirms the intended stacked tagging.

C:

The alternative addresses a provider STP domain changes root when a customer sends superior BPDUs from an access port, not the present root cause. Here the selected correction must reflect provider bridging can carry customer VLAN tags inside a provider service tag. Test for: An ingress-to-egress capture confirms the intended stacked tagging.

Question 18

A VRRP backup router does not take over when the primary gateway interface is disabled. What implementation step and validation result should be selected?

  1. Action: Differentiate forwarding continuity under GRES from routing-protocol state preservation. Evidence: A switchover test assesses both packet forwarding and routing neighbor continuity.
  2. Repair: Review session type, supported distributed behavior and switchover-appropriate intervals. Check: A tested switchover maintains the required liveness behavior without false failure.
  3. Change: Explain root and alternate roles in a loop-free spanning-tree topology. Test: The alternate port transitions appropriately after the root path fails.
  4. Implement: Check VRRP group, interface, priority, advertisements and tracking conditions. Verify: The backup assumes master role and clients retain access to the virtual gateway.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Failover depends on compatible virtual router configuration and observable primary loss. Remedy: Check VRRP group, interface, priority, advertisements and tracking conditions. Proof: The backup assumes master role and clients retain access to the virtual gateway.

Incorrect Answers

A:

GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane describes a neighboring protocol concern. In this case the controlling fact is failover depends on compatible virtual router configuration and observable primary loss. A correct remediation would check VRRP group, interface, priority, advertisements and tracking conditions and demonstrate: The backup assumes master role and clients retain access to the virtual gateway.

B:

The proposed principle concerns another network fault: BFD HA behavior depends on platform processing placement and timer tolerances. Here, failover depends on compatible virtual router configuration and observable primary loss. The most direct correction is to check VRRP group, interface, priority, advertisements and tracking conditions, confirmed by the backup assumes master role and clients retain access to the virtual gateway.

C:

That result would be useful for a different failure, namely: A switch has a root port and alternate port, but the operator assumes both must forward to use all physical bandwidth. The current case specifically calls for: Check VRRP group, interface, priority, advertisements and tracking conditions. The required observed result is: The backup assumes master role and clients retain access to the virtual gateway.

Question 19

A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. Which technical distinction best describes the observed symptom?

  1. Protocol behavior: BGP group-level export policies must preserve customer routing isolation.
  2. Underlying principle: BGP route acceptance must be constrained rather than inferred from neighbor identity.
  3. Root design issue: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links.
  4. The governing rule is: iBGP scaling mechanisms reduce the full-mesh session requirement.

Explanation

Correct Answer

B:

Underlying cause: BGP route acceptance must be constrained rather than inferred from neighbor identity. Corrective action: create explicit import policy and prefix limits aligned to customer contracts. Verify the outcome: Only approved customer prefixes enter the provider's active routing table.

Incorrect Answers

A:

The alternative addresses one customer’s new prefixes are advertised to a second unrelated customer via a shared export group, not the present root cause. Here the selected correction must reflect bGP route acceptance must be constrained rather than inferred from neighbor identity. Test for: Only approved customer prefixes enter the provider's active routing table.

C:

This option overlooks the decisive condition. Its supporting principle is dR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links, while this scenario depends on bGP route acceptance must be constrained rather than inferred from neighbor identity. Verify the correction with: Only approved customer prefixes enter the provider's active routing table.

D:

iBGP scaling mechanisms reduce the full-mesh session requirement describes a neighboring protocol concern. In this case the controlling fact is bGP route acceptance must be constrained rather than inferred from neighbor identity. A correct remediation would create explicit import policy and prefix limits aligned to customer contracts and demonstrate: Only approved customer prefixes enter the provider's active routing table.

Question 20

An iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Neighbor state must be traced through transport before modifying route policy.
  2. Protocol behavior: Unresolvable BGP next hops can make received routes unusable.
  3. Underlying principle: A usable IP path need not supply a suitable MPLS LSP or labeled transport path.
  4. Root design issue: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy.

Explanation

Correct Answer

B:

Because unresolvable BGP next hops can make received routes unusable, the best response is to restore appropriate IGP next-hop reachability or approved next-hop-self behavior. A reviewer can close the technical case only after confirming that the internal router resolves the next hop and installs the intended route.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A BGP peer is stuck in Active after a maintenance window even though the remote address is configured. The current case specifically calls for: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior. The required observed result is: The internal router resolves the next hop and installs the intended route.

C:

Inspect label-switched next-hop resolution separately from generic IP reachability is a relevant step for the separate scenario in which a loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. 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.

D:

The alternative addresses a multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop, not the present root cause. Here the selected correction must reflect unresolvable BGP next hops can make received routes unusable. Test for: The internal router resolves the next hop and installs the intended route.

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