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 38

Question 370

A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. What assessment accurately links the fault to its correction?

  1. Explanation: Aggregation can hide individual component failures if advertisement policy is not controlled. Repair: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.
  2. Fault mechanism: Operational route troubleshooting starts with active state and resolution evidence. Remediation: Inspect the configuration, active route state and next-hop reachability before changing preference.
  3. Root issue: OSPF route selection follows each router's synchronized topology view. Correction: Inspect link-state databases and SPF output on affected routers.
  4. Cause: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. Response: Restrict routing-policy matches and validate the import and export boundary.

Explanation

Correct Answer

A:

Because aggregation can hide individual component failures if advertisement policy is not controlled, the best response is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes. A reviewer can close the technical case only after confirming that the summary is advertised only under the approved component-route conditions.

Incorrect Answers

B:

The proposed principle concerns another network fault: Operational route troubleshooting starts with active state and resolution evidence. Here, aggregation can hide individual component failures if advertisement policy is not controlled. The most direct correction is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes, confirmed by the summary is advertised only under the approved component-route conditions.

C:

That result would be useful for a different failure, namely: A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. The current case specifically calls for: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes. The required observed result is: The summary is advertised only under the approved component-route conditions.

D:

This response would target a different source scenario: A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. It cannot establish the current acceptance requirement, which is: The summary is advertised only under the approved component-route conditions. The relevant action is: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.

Question 371

An operator assumes OSPFv3 must form using the same interface and address settings as OSPFv2. Which combined repair and acceptance criterion is strongest?

  1. Repair: Inspect longest-match results and forwarding routes for the specific destination. Check: The intended most-specific route changes to a valid next hop during failover.
  2. Change: Review the IPv6 OSPFv3 address-family and interface adjacency model. Test: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.
  3. Implement: Apply and verify supported route policy at the intended routing import or export boundary. Verify: The allowed prefixes are present and denied test prefixes are absent.
  4. Control: Review IPv6 path MTU discovery and endpoint fragmentation requirements. Accepted result: The sender adapts to a validated path MTU and payload delivery succeeds.

Explanation

Correct Answer

B:

Underlying cause: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Corrective action: review the IPv6 OSPFv3 address-family and interface adjacency model. Verify the outcome: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

Incorrect Answers

A:

The alternative addresses a new IPv6 static backup route is configured but a more-specific route points into a blackhole, not the present root cause. Here the selected correction must reflect oSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Test for: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

C:

This option overlooks the decisive condition. Its supporting principle is policy placement determines which prefixes influence a routing table or advertisement, while this scenario depends on oSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Verify the correction with: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

D:

Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets describes a neighboring protocol concern. In this case the controlling fact is oSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. A correct remediation would review the IPv6 OSPFv3 address-family and interface adjacency model and demonstrate: The peers exchange the expected IPv6 routes using a valid OSPFv3 adjacency.

Question 372

Tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing. What observable result most directly verifies the intended configuration?

  1. Expected observation: The service uses a valid supported customer VLAN ID.
  2. Verification result: A capture shows the expected outer service tag between provider edges.
  3. Closeout evidence: The corrected topology converges without opening an Ethernet loop.
  4. Acceptance check: A test host ARPs or discovers its gateway and routes to the intended subnet.

Explanation

Correct Answer

B:

Because provider bridging service tags must be applied and removed at the designed boundaries, the best response is to check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. A reviewer can close the technical case only after confirming that a capture shows the expected outer service tag between provider edges.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. The current case specifically calls for: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. The required observed result is: A capture shows the expected outer service tag between provider edges.

C:

Inspect spanning-tree loop-protection events, root path and link state is a relevant step for the separate scenario in which an alternate uplink remains blocked after the primary path fails because expected BPDUs disappear. It does not directly fix this case. Instead check Q-in-Q input/output encapsulation and rewrite behavior at the handoff; verify: A capture shows the expected outer service tag between provider edges.

D:

The alternative addresses a router-on-a-stick replacement with IRB stops reachability between a bridge domain and an L3 subnet, not the present root cause. Here the selected correction must reflect provider bridging service tags must be applied and removed at the designed boundaries. Test for: A capture shows the expected outer service tag between provider edges.

Question 373

An operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Control: Distinguish the inner routed payload from outer unicast encapsulation. Accepted result: Underlay traces show the outer endpoint traffic without transit processing of inner routes.
  2. Action: Verify instance ownership and route policy at both tunnel endpoints. Evidence: Traffic uses the tunnel in the intended customer routing instance only.
  3. Repair: Account for outer IP and GRE header overhead in the MTU design. Check: A large packet test respects the effective tunnel MTU without unwanted loss.
  4. Change: Collect hop-local LFIB, label forwarding and interface counters along the LSP. Test: The corrected transit hop forwards the expected incoming label to its planned outgoing label.

Explanation

Correct Answer

A:

The critical observation is: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Correct it by taking this action: Distinguish the inner routed payload from outer unicast encapsulation. Confirm the outcome with: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Incorrect Answers

B:

Tunneling transport and customer route isolation are separate configurations describes a neighboring protocol concern. In this case the controlling fact is a tunnel can carry inner packet types over an underlay forwarding only the outer header. A correct remediation would distinguish the inner routed payload from outer unicast encapsulation and demonstrate: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

C:

The proposed principle concerns another network fault: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Here, a tunnel can carry inner packet types over an underlay forwarding only the outer header. The most direct correction is to distinguish the inner routed payload from outer unicast encapsulation, confirmed by underlay traces show the outer endpoint traffic without transit processing of inner routes.

D:

That result would be useful for a different failure, namely: A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. The current case specifically calls for: Distinguish the inner routed payload from outer unicast encapsulation. The required observed result is: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Question 374

A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. Which corrective action and confirmation pair is most appropriate?

  1. Implement: Collect protocol adjacency, LSP and routing-table outputs for the affected route. Verify: The report explains the fault from interface through neighbor to selected route.
  2. Control: Compare Hello/Dead event logs with loss and interface errors before tuning timers. Accepted result: A measured link-quality improvement stabilizes OSPF adjacencies.
  3. Action: Review current DIS election rules for the network and protocol instance. Evidence: The LAN's DIS and pseudonode LSP match the documented protocol state.
  4. Repair: Review Level 1 and Level 2 routing roles and their intended boundaries. Check: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

Explanation

Correct Answer

D:

This is the model-intended best choice because iS-IS routing levels determine topology knowledge and area reachability. The targeted correction is to review Level 1 and Level 2 routing roles and their intended boundaries. Validate it by observing that an eligible Level 2 or L1/L2 path provides the approved interarea destination.

Incorrect Answers

A:

Collect protocol adjacency, LSP and routing-table outputs for the affected route is a relevant step for the separate scenario in which an IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. It does not directly fix this case. Instead review Level 1 and Level 2 routing roles and their intended boundaries; verify: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

B:

The alternative addresses several routers report intermittent OSPF neighbor resets on a saturated transit circuit, not the present root cause. Here the selected correction must reflect iS-IS routing levels determine topology knowledge and area reachability. Test for: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

C:

This answer would be more suitable when an IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node, where the corrective action is to review current DIS election rules for the network and protocol instance. The failure here is different: IS-IS routing levels determine topology knowledge and area reachability. Required validation: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

Question 375

A customer bridge-domain spans two isolated customers due to reusing a virtual switch without tenant boundaries. What operational check demonstrates that the intended outcome occurred?

  1. Closeout evidence: Both local and remote MACs learn in the intended bridge domain and hosts communicate.
  2. Acceptance check: A cross-customer unknown-unicast probe remains isolated from the other tenant.
  3. The test confirms that each tested VLAN elects its approved root and loop-free port roles.
  4. Expected observation: The MAC table stabilizes on the authorized port after loop or miswire correction.

Explanation

Correct Answer

B:

The critical observation is: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Correct it by taking this action: Separate customer bridge domains and validate virtual-switch membership. Confirm the outcome with: A cross-customer unknown-unicast probe remains isolated from the other tenant.

Incorrect Answers

A:

The proposed principle concerns another network fault: A working IRB gateway does not validate all L2 paths and trunk members. Here, layer 2 isolation depends on bridge-domain and logical switch boundaries. The most direct correction is to separate customer bridge domains and validate virtual-switch membership, confirmed by a cross-customer unknown-unicast probe remains isolated from the other tenant.

C:

This response would target a different source scenario: Several VLANs have unexpected root placement under VSTP after port membership changes. It cannot establish the current acceptance requirement, which is: A cross-customer unknown-unicast probe remains isolated from the other tenant. The relevant action is: Separate customer bridge domains and validate virtual-switch membership.

D:

Investigate MAC movement, loops and correct bridge-domain membership is a relevant step for the separate scenario in which a carrier receives the same source MAC from two access ports and sees frequent forwarding-table moves. It does not directly fix this case. Instead separate customer bridge domains and validate virtual-switch membership; verify: A cross-customer unknown-unicast probe remains isolated from the other tenant.

Question 376

An engineer uses loop protection as if it served the same purpose as BPDU protection on every port. Which combined repair and acceptance criterion is strongest?

  1. Repair: Match loop, BPDU and root protection to their different fault conditions. Check: Separate fault injections trigger the intended protection per port role.
  2. Change: Inspect spanning-tree loop-protection events, root path and link state. Test: The corrected topology converges without opening an Ethernet loop.
  3. Implement: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. Verify: A link-failure test shows the supported rapid role transition.
  4. Control: Distinguish member-link redundancy from a single physical failure domain. Accepted result: A member link failure leaves traffic flowing through a remaining usable member.

Explanation

Correct Answer

A:

This is the model-intended best choice because spanning-tree security mechanisms protect distinct topology and control-plane risks. The targeted correction is to match loop, BPDU and root protection to their different fault conditions. Validate it by observing that separate fault injections trigger the intended protection per port role.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is loop protection can prevent unsafe forwarding when control-plane information is missing, while this scenario depends on spanning-tree security mechanisms protect distinct topology and control-plane risks. Verify the correction with: Separate fault injections trigger the intended protection per port role.

C:

RSTP can converge faster using explicit roles and handshakes where conditions allow describes a neighboring protocol concern. In this case the controlling fact is spanning-tree security mechanisms protect distinct topology and control-plane risks. A correct remediation would match loop, BPDU and root protection to their different fault conditions and demonstrate: Separate fault injections trigger the intended protection per port role.

D:

The proposed principle concerns another network fault: Link aggregation improves availability only when member links and topology provide meaningful redundancy. Here, spanning-tree security mechanisms protect distinct topology and control-plane risks. The most direct correction is to match loop, BPDU and root protection to their different fault conditions, confirmed by separate fault injections trigger the intended protection per port role.

Question 377

A dual-stack peer is Established but the IPv6 customer route is absent. What is the most defensible network engineering correction?

  1. Corrective action: Inspect the incoming label, outgoing label and interface on each affected LSR.
  2. Apply this control: Restore standard AS-path checks and review any justified exception with design authority.
  3. Remediation: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.
  4. Recommended change: Map inbound and outbound policy points and confirm the intended communities.

Explanation

Correct Answer

C:

The critical observation is: IPv4 BGP session liveness does not prove IPv6 family route exchange. Correct it by taking this action: Inspect inet6 family negotiation, filters and IPv6 next-hop validity. Confirm the outcome with: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

Incorrect Answers

A:

This response would target a different source scenario: An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. It cannot establish the current acceptance requirement, which is: The expected IPv6 NLRI is received and becomes an eligible IPv6 route. The relevant action is: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.

B:

Restore standard AS-path checks and review any justified exception with design authority is a relevant step for the separate scenario in which a provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. It does not directly fix this case. Instead inspect inet6 family negotiation, filters and IPv6 next-hop validity; verify: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

D:

This answer would be more suitable when a service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group, where the corrective action is to map inbound and outbound policy points and confirm the intended communities. The failure here is different: IPv4 BGP session liveness does not prove IPv6 family route exchange. Required validation: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

Question 378

A VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain. Which corrective action and confirmation pair is most appropriate?

  1. Control: Distinguish member-link redundancy from a single physical failure domain. Accepted result: A member link failure leaves traffic flowing through a remaining usable member.
  2. Action: Deploy or validate an integrated routing and bridging L3 interface and gateway. Evidence: A test host reaches its gateway and an authorized remote subnet through IRB.
  3. Repair: Validate outer tag encapsulation and EtherType expectations across the handoff. Check: A packet capture shows the intended outer and inner VLAN tags end to end.
  4. Change: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. Test: A capture shows the expected outer service tag between provider edges.

Explanation

Correct Answer

B:

This is the model-intended best choice because layer 2 bridging does not by itself provide IP intersubnet routing. The targeted correction is to deploy or validate an integrated routing and bridging L3 interface and gateway. Validate it by observing that a test host reaches its gateway and an authorized remote subnet through IRB.

Incorrect Answers

A:

Link aggregation improves availability only when member links and topology provide meaningful redundancy describes a neighboring protocol concern. In this case the controlling fact is layer 2 bridging does not by itself provide IP intersubnet routing. A correct remediation would deploy or validate an integrated routing and bridging L3 interface and gateway and demonstrate: A test host reaches its gateway and an authorized remote subnet through IRB.

C:

That result would be useful for a different failure, namely: A service provider adds a second VLAN tag to customer frames but the downstream switch treats it as an ordinary single tag. The current case specifically calls for: Deploy or validate an integrated routing and bridging L3 interface and gateway. The required observed result is: A test host reaches its gateway and an authorized remote subnet through IRB.

D:

This response would target a different source scenario: Tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing. It cannot establish the current acceptance requirement, which is: A test host reaches its gateway and an authorized remote subnet through IRB. The relevant action is: Deploy or validate an integrated routing and bridging L3 interface and gateway.

Question 379

A route reflector advertises routes to the wrong clients after a change in group membership. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: An Established BGP session can exist with zero accepted routes or unusable next hops.
  2. Protocol behavior: OSPF broadcast topology reduces unnecessary full adjacency mesh formation.
  3. Underlying principle: Route reflection relies on correct client boundaries and originator or cluster tracking.
  4. Root design issue: Policy inheritance and term action order affect BGP route advertisement.

Explanation

Correct Answer

C:

The selected response implements the principle that route reflection relies on correct client boundaries and originator or cluster tracking. The engineer should review route-reflector client and cluster design, including loop-prevention attributes. Successful confirmation means: A test prefix reaches permitted clients without cycling through reflector clusters.

Incorrect Answers

A:

The alternative addresses an eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed, not the present root cause. Here the selected correction must reflect route reflection relies on correct client boundaries and originator or cluster tracking. Test for: A test prefix reaches permitted clients without cycling through reflector clusters.

B:

This answer would be more suitable when an engineer assumes both routers must reach Full with every speaker on a broadcast network, where the corrective action is to check the expected DR/BDR versus DROther neighbor-state relationships. The failure here is different: Route reflection relies on correct client boundaries and originator or cluster tracking. Required validation: A test prefix reaches permitted clients without cycling through reflector clusters.

D:

Policy inheritance and term action order affect BGP route advertisement describes a neighboring protocol concern. In this case the controlling fact is route reflection relies on correct client boundaries and originator or cluster tracking. A correct remediation would review route-reflector client and cluster design, including loop-prevention attributes and demonstrate: A test prefix reaches permitted clients without cycling through reflector clusters.

Question 380

An engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. What is the most defensible network engineering correction?

  1. Remediation: Verify compatible area membership or use the designed Level 2 boundary.
  2. Recommended change: Compare NET area addresses and intended L1 or L2 adjacency mode.
  3. Next step: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.
  4. Corrective action: Apply and verify supported route policy at the intended routing import or export boundary.

Explanation

Correct Answer

D:

Correct diagnosis: Policy placement determines which prefixes influence a routing table or advertisement. The appropriate action is: Apply and verify supported route policy at the intended routing import or export boundary. The follow-up evidence required is: The allowed prefixes are present and denied test prefixes are absent.

Incorrect Answers

A:

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: Apply and verify supported route policy at the intended routing import or export boundary. The required observed result is: The allowed prefixes are present and denied test prefixes are absent.

B:

This response would target a different source scenario: Two routers exchange IS-IS Hellos but one rejects the neighbor during area validation. It cannot establish the current acceptance requirement, which is: The allowed prefixes are present and denied test prefixes are absent. The relevant action is: Apply and verify supported route policy at the intended routing import or export boundary.

C:

Check DR and BDR roles and expected 2-Way peers before changing a healthy segment is a relevant step for the separate scenario in which a broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. It does not directly fix this case. Instead apply and verify supported route policy at the intended routing import or export boundary; verify: The allowed prefixes are present and denied test prefixes are absent.

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