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 15

Question 140

A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. Which next action best resolves this observed routing or switching failure?

  1. Apply this control: Add a precise prefix and instance match, then inspect effective imports.
  2. Remediation: Restrict routing-policy matches and validate the import and export boundary.
  3. Recommended change: Distinguish internal LSAs from externally originated route information.
  4. Next step: Verify recursive next-hop reachability before relying on the static route.

Explanation

Correct Answer

B:

Because route redistribution must be intentionally scoped to prevent cross-tenant leakage, the best response is to restrict routing-policy matches and validate the import and export boundary. A reviewer can close the technical case only after confirming that a negative test proves the unrelated customer prefix is absent from the target table.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. The current case specifically calls for: Restrict routing-policy matches and validate the import and export boundary. The required observed result is: A negative test proves the unrelated customer prefix is absent from the target table.

C:

Distinguish internal LSAs from externally originated route information is a relevant step for the separate scenario in which a link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. It does not directly fix this case. Instead restrict routing-policy matches and validate the import and export boundary; verify: A negative test proves the unrelated customer prefix is absent from the target table.

D:

The alternative addresses a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, not the present root cause. Here the selected correction must reflect route redistribution must be intentionally scoped to prevent cross-tenant leakage. Test for: A negative test proves the unrelated customer prefix is absent from the target table.

Question 141

An IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled. What remediation is most directly applicable?

  1. Corrective action: Enable and verify the intended IPv6 address-family reachability advertisements.
  2. Apply this control: Review the IPv6 OSPFv3 address-family and interface adjacency model.
  3. Remediation: Identify TLVs as structured information within IS-IS protocol data units.
  4. Recommended change: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance.

Explanation

Correct Answer

A:

The critical observation is: IS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Correct it by taking this action: Enable and verify the intended IPv6 address-family reachability advertisements. Confirm the outcome with: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

Incorrect Answers

B:

OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing describes a neighboring protocol concern. In this case the controlling fact is iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. A correct remediation would enable and verify the intended IPv6 address-family reachability advertisements and demonstrate: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

C:

The proposed principle concerns another network fault: IS-IS advertises extensible routing attributes using TLV-encoded fields. Here, iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. The most direct correction is to enable and verify the intended IPv6 address-family reachability advertisements, confirmed by iPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

D:

That result would be useful for a different failure, namely: After enabling OSPFv3 a provider sees IPv6 neighbors but no remote IPv6 customer prefixes. The current case specifically calls for: Enable and verify the intended IPv6 address-family reachability advertisements. The required observed result is: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

Question 142

A GRE tunnel is reachable from one routing instance but the remote customer route leaks into a different instance. What remediation is most directly applicable?

  1. Next step: Restore underlay endpoint reachability and then validate the inner tunnel route.
  2. Corrective action: Verify instance ownership and route policy at both tunnel endpoints.
  3. Apply this control: Distinguish tunneling encapsulation from confidentiality protection.
  4. Remediation: Restore the required transport route and inspect label-signaling and next-hop state.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Tunneling transport and customer route isolation are separate configurations. Remedy: Verify instance ownership and route policy at both tunnel endpoints. Proof: Traffic uses the tunnel in the intended customer routing instance only.

Incorrect Answers

A:

Restore underlay endpoint reachability and then validate the inner tunnel route is a relevant step for the separate scenario in which a GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws. It does not directly fix this case. Instead verify instance ownership and route policy at both tunnel endpoints; verify: Traffic uses the tunnel in the intended customer routing instance only.

C:

This answer would be more suitable when a network operator assumes a GRE tunnel encrypts customer packets merely because they are encapsulated, where the corrective action is to distinguish tunneling encapsulation from confidentiality protection. The failure here is different: Tunneling transport and customer route isolation are separate configurations. Required validation: Traffic uses the tunnel in the intended customer routing instance only.

D:

This option overlooks the decisive condition. Its supporting principle is mPLS relies on selected underlay transport reachability and policy eligibility, while this scenario depends on tunneling transport and customer route isolation are separate configurations. Verify the correction with: Traffic uses the tunnel in the intended customer routing instance only.

Question 143

A service provider adds a second VLAN tag to customer frames but the downstream switch treats it as an ordinary single tag. What assessment accurately links the fault to its correction?

  1. Fault mechanism: A redundant alternate path can remain nonforwarding until a failure changes roles. Remediation: Explain root and alternate roles in a loop-free spanning-tree topology.
  2. Root issue: A trunk carries only its configured authorized VLANs. Correction: Review allowed VLAN membership on both trunk endpoints.
  3. Cause: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Response: Separate customer bridge domains and validate virtual-switch membership.
  4. Diagnosis: Stacked VLAN services require compatible tagging interpretation at both ends. Action: Validate outer tag encapsulation and EtherType expectations across the handoff.

Explanation

Correct Answer

D:

Underlying cause: Stacked VLAN services require compatible tagging interpretation at both ends. Corrective action: validate outer tag encapsulation and EtherType expectations across the handoff. Verify the outcome: A packet capture shows the intended outer and inner VLAN tags end to end.

Incorrect Answers

A:

The proposed principle concerns another network fault: A redundant alternate path can remain nonforwarding until a failure changes roles. Here, stacked VLAN services require compatible tagging interpretation at both ends. The most direct correction is to validate outer tag encapsulation and EtherType expectations across the handoff, confirmed by a packet capture shows the intended outer and inner VLAN tags end to end.

B:

That result would be useful for a different failure, namely: A trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. The current case specifically calls for: Validate outer tag encapsulation and EtherType expectations across the handoff. The required observed result is: A packet capture shows the intended outer and inner VLAN tags end to end.

C:

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: A packet capture shows the intended outer and inner VLAN tags end to end. The relevant action is: Validate outer tag encapsulation and EtherType expectations across the handoff.

Question 144

Two MSTP switches place the same VLAN into different instances due to region configuration drift. What diagnosis and engineering response are most appropriate?

  1. Explanation: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Repair: Differentiate forwarding continuity under GRES from routing-protocol state preservation.
  2. Fault mechanism: MSTP region agreement affects how instances interoperate across links. Remediation: Align region identity, revision and VLAN mapping as required.
  3. Root issue: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Correction: Evaluate MSTP instances and explicit VLAN-to-instance mapping.
  4. Cause: Loop prevention depends on compatible STP participation across redundant Ethernet links. Response: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain.

Explanation

Correct Answer

B:

Correct diagnosis: MSTP region agreement affects how instances interoperate across links. The appropriate action is: Align region identity, revision and VLAN mapping as required. The follow-up evidence required is: A region status check shows the intended shared instance mapping.

Incorrect Answers

A:

This answer would be more suitable when a dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature, where the corrective action is to differentiate forwarding continuity under GRES from routing-protocol state preservation. The failure here is different: MSTP region agreement affects how instances interoperate across links. Required validation: A region status check shows the intended shared instance mapping.

C:

MSTP can group VLANs into multiple spanning-tree instances under shared region parameters describes a neighboring protocol concern. In this case the controlling fact is mSTP region agreement affects how instances interoperate across links. A correct remediation would align region identity, revision and VLAN mapping as required and demonstrate: A region status check shows the intended shared instance mapping.

D:

The proposed principle concerns another network fault: Loop prevention depends on compatible STP participation across redundant Ethernet links. Here, mSTP region agreement affects how instances interoperate across links. The most direct correction is to align region identity, revision and VLAN mapping as required, confirmed by a region status check shows the intended shared instance mapping.

Question 145

Layer 2 forwarding is disrupted during Routing Engine replacement even though high availability was enabled for routing. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Review session type, supported distributed behavior and switchover-appropriate intervals. Check: A tested switchover maintains the required liveness behavior without false failure.
  2. Change: Evaluate BFD liveness detection with the associated routing protocol. Test: A controlled forwarding failure is detected within the approved target.
  3. Implement: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane. Verify: A controlled switchover retains the expected bridge state and host connectivity.
  4. Control: Evaluate MSTP instances and explicit VLAN-to-instance mapping. Accepted result: Each VLAN maps to its intended instance and designated root.

Explanation

Correct Answer

C:

The critical observation is: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Correct it by taking this action: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane. Confirm the outcome with: A controlled switchover retains the expected bridge state and host connectivity.

Incorrect Answers

A:

This response would target a different source scenario: A BFD session flaps during Routing Engine switchover after aggressive timer tuning. It cannot establish the current acceptance requirement, which is: A controlled switchover retains the expected bridge state and host connectivity. The relevant action is: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane.

B:

Evaluate BFD liveness detection with the associated routing protocol is a relevant step for the separate scenario in which a routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. It does not directly fix this case. Instead inspect whether nonstop bridging is available and configured for the relevant L2 control plane; verify: A controlled switchover retains the expected bridge state and host connectivity.

D:

This answer would be more suitable when a data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review, where the corrective action is to evaluate MSTP instances and explicit VLAN-to-instance mapping. The failure here is different: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Required validation: A controlled switchover retains the expected bridge state and host connectivity.

Question 146

A route reflector receives a new branch prefix but one iBGP client never learns it. Which post-change observation most strongly confirms the correction?

  1. Expected observation: The session reaches Established only with the documented correct peer AS.
  2. Verification result: Only approved customer prefixes enter the provider's active routing table.
  3. Closeout evidence: The label table and LSP state match the intended forwarding path.
  4. Acceptance check: The missing client receives the correct next-hop-resolvable route.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Route reflection can fail due to session or policy scope even when the route exists centrally. Remedy: Check client definitions, route-reflector session state and export policy. Proof: The missing client receives the correct next-hop-resolvable route.

Incorrect Answers

A:

BGP OPEN negotiation includes AS identity that must match peering intent describes a neighboring protocol concern. In this case the controlling fact is route reflection can fail due to session or policy scope even when the route exists centrally. A correct remediation would check client definitions, route-reflector session state and export policy and demonstrate: The missing client receives the correct next-hop-resolvable route.

B:

The proposed principle concerns another network fault: BGP route acceptance must be constrained rather than inferred from neighbor identity. Here, route reflection can fail due to session or policy scope even when the route exists centrally. The most direct correction is to check client definitions, route-reflector session state and export policy, confirmed by the missing client receives the correct next-hop-resolvable route.

C:

That result would be useful for a different failure, namely: A transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. The current case specifically calls for: Check client definitions, route-reflector session state and export policy. The required observed result is: The missing client receives the correct next-hop-resolvable route.

Question 147

A customer bridge-domain spans two isolated customers due to reusing a virtual switch without tenant boundaries. Which root-cause explanation and corrective action fit the case?

  1. Root issue: Integrated routing bridges a defined L2 domain into an L3 interface when correctly associated. Correction: Verify VLAN or bridge-domain membership and its L3 IRB binding.
  2. Cause: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. Response: Differentiate forwarding continuity under GRES from routing-protocol state preservation.
  3. Diagnosis: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Action: Separate customer bridge domains and validate virtual-switch membership.
  4. Explanation: Layer 2 forwarding loops cannot be reliably corrected through unrelated IP routing alone. Repair: Trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses.

Explanation

Correct Answer

C:

The selected response implements the principle that layer 2 isolation depends on bridge-domain and logical switch boundaries. The engineer should separate customer bridge domains and validate virtual-switch membership. Successful confirmation means: A cross-customer unknown-unicast probe remains isolated from the other tenant.

Incorrect Answers

A:

The alternative addresses an IRB interface is present but an operator assumes it creates a bridge domain automatically, not the present root cause. Here the selected correction must reflect layer 2 isolation depends on bridge-domain and logical switch boundaries. Test for: A cross-customer unknown-unicast probe remains isolated from the other tenant.

B:

This answer would be more suitable when a dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature, where the corrective action is to differentiate forwarding continuity under GRES from routing-protocol state preservation. The failure here is different: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Required validation: A cross-customer unknown-unicast probe remains isolated from the other tenant.

D:

Layer 2 forwarding loops cannot be reliably corrected through unrelated IP routing alone describes a neighboring protocol concern. In this case the controlling fact is layer 2 isolation depends on bridge-domain and logical switch boundaries. A correct remediation would separate customer bridge domains and validate virtual-switch membership and demonstrate: A cross-customer unknown-unicast probe remains isolated from the other tenant.

Question 148

A provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. What action-and-test pairing directly resolves the case?

  1. Implement: Distinguish session negotiation from UPDATE message route advertisements. Verify: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.
  2. Control: Check client definitions, route-reflector session state and export policy. Accepted result: The missing client receives the correct next-hop-resolvable route.
  3. Action: Restore standard AS-path checks and review any justified exception with design authority. Evidence: An unwanted looped route is rejected in a lab before production change.
  4. Repair: Differentiate IP underlay reachability from LDP or RSVP control state. Check: The label table and LSP state match the intended forwarding path.

Explanation

Correct Answer

C:

This is the model-intended best choice because disabling loop prevention can introduce persistent interdomain routing loops. The targeted correction is to restore standard AS-path checks and review any justified exception with design authority. Validate it by observing that an unwanted looped route is rejected in a lab before production change.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. The current case specifically calls for: Restore standard AS-path checks and review any justified exception with design authority. The required observed result is: An unwanted looped route is rejected in a lab before production change.

B:

This response would target a different source scenario: A route reflector receives a new branch prefix but one iBGP client never learns it. It cannot establish the current acceptance requirement, which is: An unwanted looped route is rejected in a lab before production change. The relevant action is: Restore standard AS-path checks and review any justified exception with design authority.

D:

The alternative addresses a transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution, not the present root cause. Here the selected correction must reflect disabling loop prevention can introduce persistent interdomain routing loops. Test for: An unwanted looped route is rejected in a lab before production change.

Question 149

A MAC table is empty after a restart and an operator manually inserts dozens of addresses before sending test traffic. Which next action best resolves this observed routing or switching failure?

  1. Remediation: Generate controlled frames and observe normal learning on the correct bridge domain.
  2. Recommended change: Review allowed VLAN membership on both trunk endpoints.
  3. Next step: Evaluate BFD liveness detection with the associated routing protocol.
  4. Corrective action: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff.

Explanation

Correct Answer

A:

The critical observation is: Dynamic MAC tables are populated by observed frames and need not be prefilled. Correct it by taking this action: Generate controlled frames and observe normal learning on the correct bridge domain. Confirm the outcome with: A source MAC appears on the expected port after a test frame.

Incorrect Answers

B:

A trunk carries only its configured authorized VLANs describes a neighboring protocol concern. In this case the controlling fact is dynamic MAC tables are populated by observed frames and need not be prefilled. A correct remediation would generate controlled frames and observe normal learning on the correct bridge domain and demonstrate: A source MAC appears on the expected port after a test frame.

C:

The proposed principle concerns another network fault: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Here, dynamic MAC tables are populated by observed frames and need not be prefilled. The most direct correction is to generate controlled frames and observe normal learning on the correct bridge domain, confirmed by a source MAC appears on the expected port after a test frame.

D:

That result would be useful for a different failure, namely: Tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing. The current case specifically calls for: Generate controlled frames and observe normal learning on the correct bridge domain. The required observed result is: A source MAC appears on the expected port after a test frame.

Question 150

An access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Review allowed VLAN membership on both trunk endpoints. Check: Both permitted VLAN test flows cross while an explicitly denied VLAN stays blocked.
  2. Change: Distinguish access port traffic from trunk tagging behavior. Test: An end-host packet enters the correct VLAN without requiring endpoint tagging.
  3. Implement: Evaluate BFD liveness detection with the associated routing protocol. Verify: A controlled forwarding failure is detected within the approved target.
  4. Control: Document VLAN-aware versus flexible tagging and unit classification requirements. Accepted result: Both test logical units classify tagged traffic into their intended bridge domains.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Port mode determines which customer frames are tagged or untagged at the boundary. Remedy: Distinguish access port traffic from trunk tagging behavior. Proof: An end-host packet enters the correct VLAN without requiring endpoint tagging.

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 distinguish access port traffic from trunk tagging behavior; verify: An end-host packet enters the correct VLAN without requiring endpoint tagging.

C:

This answer would be more suitable when a routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up, where the corrective action is to evaluate BFD liveness detection with the associated routing protocol. The failure here is different: Port mode determines which customer frames are tagged or untagged at the boundary. Required validation: An end-host packet enters the correct VLAN without requiring endpoint tagging.

D:

This option overlooks the decisive condition. Its supporting principle is logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model, while this scenario depends on port mode determines which customer frames are tagged or untagged at the boundary. Verify the correction with: An end-host packet enters the correct VLAN without requiring endpoint tagging.

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