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 32

Question 310

A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. Which technical distinction best describes the observed symptom?

  1. The governing rule is: Policy inheritance and term action order affect BGP route advertisement.
  2. The key distinction is: Summary advertisements require validation against their underlying active route policy.
  3. Protocol behavior: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues.
  4. Underlying principle: Aggregation can hide individual component failures if advertisement policy is not controlled.

Explanation

Correct Answer

C:

Because instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues, the best response is to run route and connectivity checks in the explicitly intended routing instance. A reviewer can close the technical case only after confirming that the tenant-specific lookup resolves and the same source-based test reaches its destination.

Incorrect Answers

A:

Inspect effective group and neighbor export policy evaluation order is a relevant step for the separate scenario in which a BGP export policy matches a community but no routes leave the peer after a group-level policy reorder. It does not directly fix this case. Instead run route and connectivity checks in the explicitly intended routing instance; verify: The tenant-specific lookup resolves and the same source-based test reaches its destination.

B:

The alternative addresses an aggregated customer advertisement persists while all contributing specifics have withdrawn, not the present root cause. Here the selected correction must reflect instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Test for: The tenant-specific lookup resolves and the same source-based test reaches its destination.

D:

This option overlooks the decisive condition. Its supporting principle is aggregation can hide individual component failures if advertisement policy is not controlled, while this scenario depends on instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Verify the correction with: The tenant-specific lookup resolves and the same source-based test reaches its destination.

Question 311

A provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Repair: Distinguish IP RIB entries from label forwarding information and LSP resolution. Check: The transit LSR selects an authorized outgoing label and interface.
  2. Change: Update the engineered path constraints and verify candidate topology availability. Test: The backup LSP establishes on a permitted alternate path.
  3. Implement: Distinguish the MPLS shim label stack from the encapsulated payload. Verify: A packet decode identifies label fields separately from the carried IP packet.
  4. Control: Compare MED use with actual prior BGP decision attributes and neighbor policy. Accepted result: A captured received-path comparison explains which attribute selected the route.

Explanation

Correct Answer

A:

The selected response implements the principle that mPLS forwarding relies on label bindings and compatible next-hop state. The engineer should distinguish IP RIB entries from label forwarding information and LSP resolution. Successful confirmation means: The transit LSR selects an authorized outgoing label and interface.

Incorrect Answers

B:

That result would be useful for a different failure, namely: An operator configured an explicit RSVP path through a link that is now administratively down. The current case specifically calls for: Distinguish IP RIB entries from label forwarding information and LSP resolution. The required observed result is: The transit LSR selects an authorized outgoing label and interface.

C:

This response would target a different source scenario: An operator expects an MPLS label to represent an entire customer IP packet header. It cannot establish the current acceptance requirement, which is: The transit LSR selects an authorized outgoing label and interface. The relevant action is: Distinguish IP RIB entries from label forwarding information and LSP resolution.

D:

Compare MED use with actual prior BGP decision attributes and neighbor policy is a relevant step for the separate scenario in which an operator changes MED and sees no route change because the target AS prioritizes other attributes. 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.

Question 312

A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. What observable result most directly verifies the intended configuration?

  1. Expected observation: The unauthorized more-specific is rejected while approved aggregates remain.
  2. Verification result: A hop-by-hop labeled test locates and corrects the failing label action.
  3. Closeout evidence: The intended local preference policy selects the approved egress.
  4. Acceptance check: The internal peer has a valid route to the BGP next hop and installs the prefix.

Explanation

Correct Answer

D:

Because iBGP can preserve externally learned next-hop information that internal speakers must resolve, the best response is to review BGP next-hop reachability and explicit next-hop handling. A reviewer can close the technical case only after confirming that the internal peer has a valid route to the BGP next hop and installs the prefix.

Incorrect Answers

A:

This answer would be more suitable when a customer advertises an unauthorized more-specific and the PE propagates it across the provider core, where the corrective action is to tighten customer import route filtering and test permitted prefix lengths. The failure here is different: iBGP can preserve externally learned next-hop information that internal speakers must resolve. Required validation: The internal peer has a valid route to the BGP next hop and installs the prefix.

B:

This option overlooks the decisive condition. Its supporting principle is successful ordinary IP forwarding does not isolate MPLS packet forwarding faults, while this scenario depends on iBGP can preserve externally learned next-hop information that internal speakers must resolve. Verify the correction with: The internal peer has a valid route to the BGP next hop and installs the prefix.

C:

BGP best-path selection considers higher-priority decision attributes before AS-path length describes a neighboring protocol concern. In this case the controlling fact is iBGP can preserve externally learned next-hop information that internal speakers must resolve. A correct remediation would review BGP next-hop reachability and explicit next-hop handling and demonstrate: The internal peer has a valid route to the BGP next hop and installs the prefix.

Question 313

An alternate uplink remains blocked after the primary path fails because expected BPDUs disappear. Which change best corrects the failure without losing the intended design?

  1. Next step: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.
  2. Corrective action: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.
  3. Apply this control: Distinguish member-link redundancy from a single physical failure domain.
  4. Remediation: Inspect spanning-tree loop-protection events, root path and link state.

Explanation

Correct Answer

D:

The case turns on the distinction that loop protection can prevent unsafe forwarding when control-plane information is missing. Apply this concrete engineering step: Inspect spanning-tree loop-protection events, root path and link state. An acceptable verification outcome is: The corrected topology converges without opening an Ethernet loop.

Incorrect Answers

A:

This response would target a different source scenario: Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. It cannot establish the current acceptance requirement, which is: The corrected topology converges without opening an Ethernet loop. The relevant action is: Inspect spanning-tree loop-protection events, root path and link state.

B:

Inspect per-VLAN STP instances and configured priorities, not just a global STP summary is a relevant step for the separate scenario in which several VLANs have unexpected root placement under VSTP after port membership changes. It does not directly fix this case. Instead inspect spanning-tree loop-protection events, root path and link state; verify: The corrected topology converges without opening an Ethernet loop.

C:

The alternative addresses a failover plan relies on one physical interface carrying several links and calls it a redundant LAG, not the present root cause. Here the selected correction must reflect loop protection can prevent unsafe forwarding when control-plane information is missing. Test for: The corrected topology converges without opening an Ethernet loop.

Question 314

A link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. Which corrective action and confirmation pair is most appropriate?

  1. Implement: Check MTU and interface compatibility and inspect neighbor-state details. Verify: The adjacency advances through database synchronization to Full.
  2. Control: Check the expected DR/BDR versus DROther neighbor-state relationships. Accepted result: The neighbor states match expected DR roles and routing converges.
  3. Action: Verify route contribution and the conditions for route generation. Evidence: The generated prefix appears only when the required contributing route is active.
  4. Repair: Distinguish internal LSAs from externally originated route information. Check: The expected redistributed prefix appears with the right OSPF route type.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: OSPF route type and LSA scope depend on where routing information originates. Remedy: Distinguish internal LSAs from externally originated route information. Proof: The expected redistributed prefix appears with the right OSPF route type.

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 oSPF route type and LSA scope depend on where routing information originates. A correct remediation would distinguish internal LSAs from externally originated route information and demonstrate: The expected redistributed prefix appears with the right OSPF route type.

B:

The proposed principle concerns another network fault: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. Here, oSPF route type and LSA scope depend on where routing information originates. The most direct correction is to distinguish internal LSAs from externally originated route information, confirmed by the expected redistributed prefix appears with the right OSPF route type.

C:

That result would be useful for a different failure, namely: A generated route is configured but its expected contributing route is absent from the routing table. The current case specifically calls for: Distinguish internal LSAs from externally originated route information. The required observed result is: The expected redistributed prefix appears with the right OSPF route type.

Question 315

Two network services use identical customer VLAN IDs and the team assumes their frames must share one L2 broadcast domain. Which statement identifies the key design assumption that failed?

  1. The governing rule is: A customer VLAN tag can be scoped by access interface and provider service context.
  2. The key distinction is: Provider bridging can carry customer VLAN tags inside a provider service tag.
  3. Protocol behavior: Customer-facing encapsulation must match the traffic format at ingress.
  4. Underlying principle: Link aggregation improves availability only when member links and topology provide meaningful redundancy.

Explanation

Correct Answer

A:

The case turns on the distinction that a customer VLAN tag can be scoped by access interface and provider service context. Apply this concrete engineering step: Separate provider service identification from customer VLAN identifiers. An acceptable verification outcome is: The overlapping customer IDs remain isolated within their designated provider services.

Incorrect Answers

B:

This answer would be more suitable when an operator plans provider bridging but assumes the customer's C-tag is removed from every frame, where the corrective action is to clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. The failure here is different: A customer VLAN tag can be scoped by access interface and provider service context. Required validation: The overlapping customer IDs remain isolated within their designated provider services.

C:

This option overlooks the decisive condition. Its supporting principle is customer-facing encapsulation must match the traffic format at ingress, while this scenario depends on a customer VLAN tag can be scoped by access interface and provider service context. Verify the correction with: The overlapping customer IDs remain isolated within their designated provider services.

D:

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 a customer VLAN tag can be scoped by access interface and provider service context. A correct remediation would separate provider service identification from customer VLAN identifiers and demonstrate: The overlapping customer IDs remain isolated within their designated provider services.

Question 316

An engineer assumes both routers must reach Full with every speaker on a broadcast network. Which test result would best confirm a successful fix?

  1. Verification result: The neighbor states match expected DR roles and routing converges.
  2. Closeout evidence: The allowed prefixes are present and denied test prefixes are absent.
  3. Acceptance check: A measured link-quality improvement stabilizes OSPF adjacencies.
  4. The test confirms that only approved external prefixes appear in the OSPF domain.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. Remedy: Check the expected DR/BDR versus DROther neighbor-state relationships. Proof: The neighbor states match expected DR roles and routing converges.

Incorrect Answers

B:

This response would target a different source scenario: An engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context. It cannot establish the current acceptance requirement, which is: The neighbor states match expected DR roles and routing converges. The relevant action is: Check the expected DR/BDR versus DROther neighbor-state relationships.

C:

Compare Hello/Dead event logs with loss and interface errors before tuning timers is a relevant step for the separate scenario in which several routers report intermittent OSPF neighbor resets on a saturated transit circuit. It does not directly fix this case. Instead check the expected DR/BDR versus DROther neighbor-state relationships; verify: The neighbor states match expected DR roles and routing converges.

D:

The alternative addresses a provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy, not the present root cause. Here the selected correction must reflect oSPF broadcast topology reduces unnecessary full adjacency mesh formation. Test for: The neighbor states match expected DR roles and routing converges.

Question 317

A technician edits a router ID but tests immediately without accounting for established OSPF process state. Which combined repair and acceptance criterion is strongest?

  1. Action: Apply a safe approved OSPF process refresh and verify advertised router identity. Evidence: All neighbors record the new unique ID and routing stability is restored.
  2. Repair: Check the expected DR/BDR versus DROther neighbor-state relationships. Check: The neighbor states match expected DR roles and routing converges.
  3. Change: Compare RIB selection with forwarding-table installation and next-hop resolution. Test: The forwarding entry uses the correct next hop for the active route.
  4. Implement: Review the passive-interface configuration and required active neighbor links. Verify: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Explanation

Correct Answer

A:

The critical observation is: Changing router identity may require controlled protocol restart or adjacency reestablishment. Correct it by taking this action: Apply a safe approved OSPF process refresh and verify advertised router identity. Confirm the outcome with: All neighbors record the new unique ID and routing stability is restored.

Incorrect Answers

B:

OSPF broadcast topology reduces unnecessary full adjacency mesh formation describes a neighboring protocol concern. In this case the controlling fact is changing router identity may require controlled protocol restart or adjacency reestablishment. A correct remediation would apply a safe approved OSPF process refresh and verify advertised router identity and demonstrate: All neighbors record the new unique ID and routing stability is restored.

C:

The proposed principle concerns another network fault: Control-plane route visibility and installed forwarding state are distinct evidence. Here, changing router identity may require controlled protocol restart or adjacency reestablishment. The most direct correction is to apply a safe approved OSPF process refresh and verify advertised router identity, confirmed by all neighbors record the new unique ID and routing stability is restored.

D:

That result would be useful for a different failure, namely: An OSPF interface is accidentally set passive on a provider edge and its neighbor never appears. The current case specifically calls for: Apply a safe approved OSPF process refresh and verify advertised router identity. The required observed result is: All neighbors record the new unique ID and routing stability is restored.

Question 318

An OSPF packet capture shows Link State Updates but the route remains hidden from the active table. What operational check demonstrates that the intended outcome occurred?

  1. The test confirms that only approved external prefixes appear in the OSPF domain.
  2. Expected observation: The adjacency advances through database synchronization to Full.
  3. Verification result: The routing table exposes the selection reason and the intended route is installed.
  4. Closeout evidence: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Explanation

Correct Answer

C:

Because receiving topology data does not guarantee a route becomes active and installed, the best response is to compare received LSAs with route selection, area eligibility and next-hop resolution. A reviewer can close the technical case only after confirming that the routing table exposes the selection reason and the intended route is installed.

Incorrect Answers

A:

Constrain redistribution and test route policy acceptance for the intended prefixes is a relevant step for the separate scenario in which a provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy. It does not directly fix this case. Instead compare received LSAs with route selection, area eligibility and next-hop resolution; verify: The routing table exposes the selection reason and the intended route is installed.

B:

The alternative addresses an OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange, not the present root cause. Here the selected correction must reflect receiving topology data does not guarantee a route becomes active and installed. Test for: The routing table exposes the selection reason and the intended route is installed.

D:

This option overlooks the decisive condition. Its supporting principle is iS-IS Level 1 adjacency formation depends on common area context, while this scenario depends on receiving topology data does not guarantee a route becomes active and installed. Verify the correction with: The routing table exposes the selection reason and the intended route is installed.

Question 319

A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. Which cause-and-remedy pairing reflects the observed problem?

  1. Fault mechanism: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Remediation: Separate customer bridge domains and validate virtual-switch membership.
  2. Root issue: Loop protection can prevent unsafe forwarding when control-plane information is missing. Correction: Inspect spanning-tree loop-protection events, root path and link state.
  3. Cause: RSTP can converge faster using explicit roles and handshakes where conditions allow. Response: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.
  4. Diagnosis: Protective edge-port shutdown is evidence of BPDU policy enforcement. Action: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.

Explanation

Correct Answer

D:

Underlying cause: Protective edge-port shutdown is evidence of BPDU policy enforcement. Corrective action: verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. Verify the outcome: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Incorrect Answers

A:

The proposed principle concerns another network fault: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Here, protective edge-port shutdown is evidence of BPDU policy enforcement. The most direct correction is to verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards, confirmed by the approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

B:

That result would be useful for a different failure, namely: An alternate uplink remains blocked after the primary path fails because expected BPDUs disappear. The current case specifically calls for: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. The required observed result is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

C:

This response would target a different source scenario: Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. It cannot establish the current acceptance requirement, which is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled. The relevant action is: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.

Question 320

A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. What is the most defensible network engineering correction?

  1. Remediation: Validate forwarding load-sharing configuration and run representative multi-flow traffic.
  2. Recommended change: Constrain redistribution and test route policy acceptance for the intended prefixes.
  3. Next step: Review filter-based forwarding classification and the intended next-table selection.
  4. Corrective action: Compare RIB selection with forwarding-table installation and next-hop resolution.

Explanation

Correct Answer

D:

Because control-plane route visibility and installed forwarding state are distinct evidence, the best response is to compare RIB selection with forwarding-table installation and next-hop resolution. A reviewer can close the technical case only after confirming that the forwarding entry uses the correct next hop for the active route.

Incorrect Answers

A:

This answer would be more suitable when an equal-cost path test sends nearly all flows across one member while both links remain operational, where the corrective action is to validate forwarding load-sharing configuration and run representative multi-flow traffic. The failure here is different: Control-plane route visibility and installed forwarding state are distinct evidence. Required validation: The forwarding entry uses the correct next hop for the active route.

B:

This option overlooks the decisive condition. Its supporting principle is routing policy controls which external reachability is injected into OSPF, while this scenario depends on control-plane route visibility and installed forwarding state are distinct evidence. Verify the correction with: The forwarding entry uses the correct next hop for the active route.

C:

Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table describes a neighboring protocol concern. In this case the controlling fact is control-plane route visibility and installed forwarding state are distinct evidence. A correct remediation would compare RIB selection with forwarding-table installation and next-hop resolution and demonstrate: The forwarding entry uses the correct next hop for the active route.

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