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 60

Question 590

An NSR configuration fails commit after an operator adds graceful restart on the same device. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: Conflicting local GR and NSR configuration must be resolved before activation. Remediation: Remove the incompatible local mode and validate the supported HA configuration.
  2. Root issue: DR and BDR elections apply to broadcast or NBMA segments, not ordinary point-to-point links. Correction: Select the correct network-type behavior and inspect the neighbor-state model.
  3. Cause: Forwarding-plane continuity does not prove control-plane routing continuity. Response: Check whether GRES is paired with the intended GR or NSR support and verify protocol state.
  4. Diagnosis: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Action: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.

Explanation

Correct Answer

A:

Correct diagnosis: Conflicting local GR and NSR configuration must be resolved before activation. The appropriate action is: Remove the incompatible local mode and validate the supported HA configuration. The follow-up evidence required is: The corrected candidate commits and the Routing Engine synchronization check passes.

Incorrect Answers

B:

The alternative addresses an engineer expects a designated router to be elected on a point-to-point OSPF circuit, not the present root cause. Here the selected correction must reflect conflicting local GR and NSR configuration must be resolved before activation. Test for: The corrected candidate commits and the Routing Engine synchronization check passes.

C:

This answer would be more suitable when a Routing Engine switchover retains data-plane traffic briefly but causes OSPF adjacencies to restart, where the corrective action is to check whether GRES is paired with the intended GR or NSR support and verify protocol state. The failure here is different: Conflicting local GR and NSR configuration must be resolved before activation. Required validation: The corrected candidate commits and the Routing Engine synchronization check passes.

D:

This option overlooks the decisive condition. Its supporting principle is nonstop bridging protects relevant Layer 2 control-protocol state during switchover, while this scenario depends on conflicting local GR and NSR configuration must be resolved before activation. Verify the correction with: The corrected candidate commits and the Routing Engine synchronization check passes.

Question 591

One branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. Which change best corrects the failure without losing the intended design?

  1. Remediation: Inspect the configuration, active route state and next-hop reachability before changing preference.
  2. Recommended change: Verify whether PHP or explicit-null behavior is configured and intended.
  3. Next step: Compare ingress label imposition with transit LFIB and egress disposition.
  4. Corrective action: Distinguish IP RIB entries from label forwarding information and LSP resolution.

Explanation

Correct Answer

C:

The case turns on the distinction that successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Apply this concrete engineering step: Compare ingress label imposition with transit LFIB and egress disposition. An acceptable verification outcome is: A hop-by-hop labeled test locates and corrects the failing label action.

Incorrect Answers

A:

The proposed principle concerns another network fault: Operational route troubleshooting starts with active state and resolution evidence. Here, successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. The most direct correction is to compare ingress label imposition with transit LFIB and egress disposition, confirmed by a hop-by-hop labeled test locates and corrects the failing label action.

B:

That result would be useful for a different failure, namely: An MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. The current case specifically calls for: Compare ingress label imposition with transit LFIB and egress disposition. The required observed result is: A hop-by-hop labeled test locates and corrects the failing label action.

D:

Distinguish IP RIB entries from label forwarding information and LSP resolution is a relevant step for the separate scenario in which a provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table. It does not directly fix this case. Instead compare ingress label imposition with transit LFIB and egress disposition; verify: A hop-by-hop labeled test locates and corrects the failing label action.

Question 592

Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. Which root-cause explanation and corrective action fit the case?

  1. Diagnosis: RSTP can converge faster using explicit roles and handshakes where conditions allow. Action: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.
  2. Explanation: Loop prevention depends on compatible STP participation across redundant Ethernet links. Repair: Inspect STP state and enable the approved spanning-tree protocol for that bridge domain.
  3. Fault mechanism: Root protection can prevent undesired superior-root claims from changing root placement. Remediation: Review root protection at the provider-facing boundary.
  4. Root issue: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Correction: Evaluate BFD liveness detection with the associated routing protocol.

Explanation

Correct Answer

A:

This is the model-intended best choice because rSTP can converge faster using explicit roles and handshakes where conditions allow. The targeted correction is to compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. Validate it by observing that a link-failure test shows the supported rapid role transition.

Incorrect Answers

B:

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 rSTP can converge faster using explicit roles and handshakes where conditions allow. Verify the correction with: A link-failure test shows the supported rapid role transition.

C:

Root protection can prevent undesired superior-root claims from changing root placement describes a neighboring protocol concern. In this case the controlling fact is rSTP can converge faster using explicit roles and handshakes where conditions allow. A correct remediation would compare the rapid proposal/agreement behavior with traditional timer-dependent transitions and demonstrate: A link-failure test shows the supported rapid role transition.

D:

The proposed principle concerns another network fault: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Here, rSTP can converge faster using explicit roles and handshakes where conditions allow. The most direct correction is to compare the rapid proposal/agreement behavior with traditional timer-dependent transitions, confirmed by a link-failure test shows the supported rapid role transition.

Question 593

An operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. What observable result most directly verifies the intended configuration?

  1. Expected observation: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.
  2. Verification result: A controlled large-payload test succeeds after MTU or MSS adjustment.
  3. Closeout evidence: The remote tunnel endpoint is reachable through the intended underlay.
  4. Acceptance check: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Explanation

Correct Answer

D:

The case turns on the distinction that a tunnel can carry inner packet types over an underlay forwarding only the outer header. Apply this concrete engineering step: Distinguish the inner routed payload from outer unicast encapsulation. An acceptable verification outcome is: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Incorrect Answers

A:

This response would target a different source scenario: IPv6-over-IPv4 tunnel endpoints reach each other using IPv4 but IPv6 payloads fail after a firewall update. It cannot establish the current acceptance requirement, which is: Underlay traces show the outer endpoint traffic without transit processing of inner routes. The relevant action is: Distinguish the inner routed payload from outer unicast encapsulation.

B:

Test effective MTU and path MTU discovery across the encapsulated route is a relevant step for the separate scenario in which small probes pass through GRE but large customer packets are intermittently dropped. It does not directly fix this case. Instead distinguish the inner routed payload from outer unicast encapsulation; verify: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

C:

The alternative addresses a GRE design includes a virtual tunnel interface but omits routable IPv4 underlay access to the remote endpoint, not the present root cause. Here the selected correction must reflect a tunnel can carry inner packet types over an underlay forwarding only the outer header. Test for: Underlay traces show the outer endpoint traffic without transit processing of inner routes.

Question 594

A switch operator treats the highest bridge ID as the guaranteed STP root. What diagnosis and engineering response are most appropriate?

  1. Root issue: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Correction: Trace frame classification and virtual-switch bridge-domain association.
  2. Cause: Traditional spanning-tree root election favors the lowest bridge ID. Response: Review root bridge priority and MAC-based bridge identifier comparison.
  3. Diagnosis: A redundant alternate path can remain nonforwarding until a failure changes roles. Action: Explain root and alternate roles in a loop-free spanning-tree topology.
  4. Explanation: Per-VLAN spanning-tree behavior can differ across VLANs. Repair: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.

Explanation

Correct Answer

B:

This is the model-intended best choice because traditional spanning-tree root election favors the lowest bridge ID. The targeted correction is to review root bridge priority and MAC-based bridge identifier comparison. Validate it by observing that the intended device is root under the tested priorities and tie-breakers.

Incorrect Answers

A:

Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching 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.

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: Review root bridge priority and MAC-based bridge identifier comparison. The required observed result is: The intended device is root under the tested priorities and tie-breakers.

D:

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: The intended device is root under the tested priorities and tie-breakers. The relevant action is: Review root bridge priority and MAC-based bridge identifier comparison.

Question 595

A route leaked to a second routing table unexpectedly carries a next hop that cannot be resolved there. Which cause-and-remedy pairing reflects the observed problem?

  1. 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.
  2. Root issue: Moving route information between tables does not remove the need for a valid forwarding next hop. Correction: Evaluate routing-table relationships and next-hop resolution when using RIB groups.
  3. Cause: A configured static route need not become usable forwarding state when its next hop cannot resolve. Response: Verify recursive next-hop reachability before relying on the static route.
  4. Diagnosis: OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions. Action: Differentiate neighbor discovery from database synchronization message types.

Explanation

Correct Answer

B:

Underlying cause: Moving route information between tables does not remove the need for a valid forwarding next hop. Corrective action: evaluate routing-table relationships and next-hop resolution when using RIB groups. Verify the outcome: The imported route resolves and forwarding behavior matches the intended instance.

Incorrect Answers

A:

The alternative addresses after a maintenance window a configured customer static prefix is missing from active routes despite no syntax errors, not the present root cause. Here the selected correction must reflect moving route information between tables does not remove the need for a valid forwarding next hop. Test for: The imported route resolves and forwarding behavior matches the intended instance.

C:

This option overlooks the decisive condition. Its supporting principle is a configured static route need not become usable forwarding state when its next hop cannot resolve, while this scenario depends on moving route information between tables does not remove the need for a valid forwarding next hop. Verify the correction with: The imported route resolves and forwarding behavior matches the intended instance.

D:

OSPF uses distinct Hello, database description, link state request, update and acknowledgment functions describes a neighboring protocol concern. In this case the controlling fact is moving route information between tables does not remove the need for a valid forwarding next hop. A correct remediation would evaluate routing-table relationships and next-hop resolution when using RIB groups and demonstrate: The imported route resolves and forwarding behavior matches the intended instance.

Question 596

Several VLANs have unexpected root placement under VSTP after port membership changes. Which cause-and-remedy pairing reflects the observed problem?

  1. Explanation: Per-VLAN spanning-tree behavior can differ across VLANs. Repair: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.
  2. Fault mechanism: Traditional spanning-tree root election favors the lowest bridge ID. Remediation: Review root bridge priority and MAC-based bridge identifier comparison.
  3. Root issue: Configuration intent must be verified against the actual elected spanning-tree root. Correction: Compare root priority, bridge identifiers and current STP topology status.
  4. Cause: VLAN reassignment must be verified in actual port classification. Response: Check committed access VLAN settings and operational membership rather than relying on notes.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Per-VLAN spanning-tree behavior can differ across VLANs. Remedy: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary. Proof: Each tested VLAN elects its approved root and loop-free port roles.

Incorrect Answers

B:

This response would target a different source scenario: A switch operator treats the highest bridge ID as the guaranteed STP root. It cannot establish the current acceptance requirement, which is: Each tested VLAN elects its approved root and loop-free port roles. The relevant action is: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.

C:

Compare root priority, bridge identifiers and current STP topology status is a relevant step for the separate scenario in which a planned root bridge migration is configured but the operational root remains on the old switch. It does not directly fix this case. Instead inspect per-VLAN STP instances and configured priorities, not just a global STP summary; verify: Each tested VLAN elects its approved root and loop-free port roles.

D:

The alternative addresses an access switch forwards untagged traffic into VLAN 20 after a port is moved to VLAN 30, not the present root cause. Here the selected correction must reflect per-VLAN spanning-tree behavior can differ across VLANs. Test for: Each tested VLAN elects its approved root and loop-free port roles.

Question 597

Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: Control-plane route visibility and installed forwarding state are distinct evidence.
  2. The governing rule is: OSPF route type and LSA scope depend on where routing information originates.
  3. The key distinction is: Preference edits can change route selection without any interface outage.
  4. Protocol behavior: Route preference determines the selected route before any multipath decision.

Explanation

Correct Answer

D:

The selected response implements the principle that route preference determines the selected route before any multipath decision. The engineer should review route preference before considering equivalent forwarding paths. Successful confirmation means: The selected path and its preference match the intended backup policy.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is control-plane route visibility and installed forwarding state are distinct evidence, while this scenario depends on route preference determines the selected route before any multipath decision. Verify the correction with: The selected path and its preference match the intended backup policy.

B:

OSPF route type and LSA scope depend on where routing information originates describes a neighboring protocol concern. In this case the controlling fact is route preference determines the selected route before any multipath decision. A correct remediation would review route preference before considering equivalent forwarding paths and demonstrate: The selected path and its preference match the intended backup policy.

C:

The proposed principle concerns another network fault: Preference edits can change route selection without any interface outage. Here, route preference determines the selected route before any multipath decision. The most direct correction is to review route preference before considering equivalent forwarding paths, confirmed by the selected path and its preference match the intended backup policy.

Question 598

A router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count. Which statement identifies the key design assumption that failed?

  1. Underlying principle: BGP message types have separate roles in session formation and reachability exchange.
  2. Root design issue: Route reflection can fail due to session or policy scope even when the route exists centrally.
  3. The governing rule is: BGP selection is policy-driven and is not equivalent to IGP least-hop routing.
  4. The key distinction is: Changing router identity may require controlled protocol restart or adjacency reestablishment.

Explanation

Correct Answer

C:

Because bGP selection is policy-driven and is not equivalent to IGP least-hop routing, the best response is to trace the applicable BGP route-selection steps and local policies. A reviewer can close the technical case only after confirming that the chosen path matches the configured preference and applicable attributes.

Incorrect Answers

A:

Distinguish session negotiation from UPDATE message route advertisements is a relevant step for the separate scenario in which a provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. It does not directly fix this case. Instead trace the applicable BGP route-selection steps and local policies; verify: The chosen path matches the configured preference and applicable attributes.

B:

The alternative addresses a route reflector receives a new branch prefix but one iBGP client never learns it, not the present root cause. Here the selected correction must reflect bGP selection is policy-driven and is not equivalent to IGP least-hop routing. Test for: The chosen path matches the configured preference and applicable attributes.

D:

This option overlooks the decisive condition. Its supporting principle is changing router identity may require controlled protocol restart or adjacency reestablishment, while this scenario depends on bGP selection is policy-driven and is not equivalent to IGP least-hop routing. Verify the correction with: The chosen path matches the configured preference and applicable attributes.

Question 599

Two routers advertise identical OSPF router IDs and their link-state information becomes inconsistent. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Control: Check MTU and interface compatibility and inspect neighbor-state details. Accepted result: The adjacency advances through database synchronization to Full.
  2. Action: Rehearse the failure and inspect active next hops and IS-IS route changes. Evidence: The backup next hop resolves and carries test traffic after the primary link fails.
  3. Repair: Assign distinct stable router IDs and clear stale protocol state using an approved procedure. Check: Each router is uniquely identified and the link-state database converges.
  4. Change: Verify compatible network and Hello parameters including mask where applicable. Test: A controlled neighbor check reaches Full after configuration correction.

Explanation

Correct Answer

C:

The case turns on the distinction that oSPF identifies speakers by router ID, which must be unique inside a routing domain. Apply this concrete engineering step: Assign distinct stable router IDs and clear stale protocol state using an approved procedure. An acceptable verification outcome is: Each router is uniquely identified and the link-state database converges.

Incorrect Answers

A:

The proposed principle concerns another network fault: Neighbor discovery can succeed even when database exchange parameters prevent completion. Here, oSPF identifies speakers by router ID, which must be unique inside a routing domain. The most direct correction is to assign distinct stable router IDs and clear stale protocol state using an approved procedure, confirmed by each router is uniquely identified and the link-state database converges.

B:

That result would be useful for a different failure, namely: A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. The current case specifically calls for: Assign distinct stable router IDs and clear stale protocol state using an approved procedure. The required observed result is: Each router is uniquely identified and the link-state database converges.

D:

Verify compatible network and Hello parameters including mask where applicable is a relevant step for the separate scenario in which a router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. It does not directly fix this case. Instead assign distinct stable router IDs and clear stale protocol state using an approved procedure; verify: Each router is uniquely identified and the link-state database converges.

Question 600

A Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: Provider outer VLAN classification must preserve tenant isolation.
  2. Protocol behavior: Provider bridging service tags must be applied and removed at the designed boundaries.
  3. Underlying principle: RSTP can converge faster using explicit roles and handshakes where conditions allow.
  4. Root design issue: A trunk carries only its configured authorized VLANs.

Explanation

Correct Answer

A:

This is the model-intended best choice because provider outer VLAN classification must preserve tenant isolation. The targeted correction is to assign distinct service encapsulation and verify edge translation rules. Validate it by observing that cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is provider bridging service tags must be applied and removed at the designed boundaries, while this scenario depends on provider outer VLAN classification must preserve tenant isolation. Verify the correction with: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

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 provider outer VLAN classification must preserve tenant isolation. A correct remediation would assign distinct service encapsulation and verify edge translation rules and demonstrate: Cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

D:

The proposed principle concerns another network fault: A trunk carries only its configured authorized VLANs. Here, provider outer VLAN classification must preserve tenant isolation. The most direct correction is to assign distinct service encapsulation and verify edge translation rules, confirmed by cross-tenant traffic fails while each tenant's inner VLAN passes end to end.

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