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 5

Question 40

An engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: BGP MED influence is conditional on the receiving network's path selection rules.
  2. Protocol behavior: A stale label binding cannot compensate for unusable transport forwarding.
  3. Underlying principle: RSVP resource reservation may affect which additional constrained LSPs can be admitted.
  4. Root design issue: A usable IP path need not supply a suitable MPLS LSP or labeled transport path.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Remedy: Distinguish signaling reservations from physical link speed and admission control. Proof: A controlled setup respects the approved link reservation policy.

Incorrect Answers

A:

This answer would be more suitable when an inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies, where the corrective action is to distinguish an advertised inbound hint from neighboring-AS route policy decisions. The failure here is different: RSVP resource reservation may affect which additional constrained LSPs can be admitted. Required validation: A controlled setup respects the approved link reservation policy.

B:

This option overlooks the decisive condition. Its supporting principle is a stale label binding cannot compensate for unusable transport forwarding, while this scenario depends on rSVP resource reservation may affect which additional constrained LSPs can be admitted. Verify the correction with: A controlled setup respects the approved link reservation policy.

D:

The proposed principle concerns another network fault: A usable IP path need not supply a suitable MPLS LSP or labeled transport path. Here, rSVP resource reservation may affect which additional constrained LSPs can be admitted. The most direct correction is to distinguish signaling reservations from physical link speed and admission control, confirmed by a controlled setup respects the approved link reservation policy.

Question 41

A router learns the same prefix from peers in distinct autonomous systems but the engineer compares only BGP hop count. What is the most defensible network engineering correction?

  1. Remediation: Verify IP reachability, routing instance context, TCP transport and session authentication.
  2. Recommended change: Distinguish session negotiation from UPDATE message route advertisements.
  3. Next step: Check the expected DR/BDR versus DROther neighbor-state relationships.
  4. Corrective action: Trace the applicable BGP route-selection steps and local policies.

Explanation

Correct Answer

D:

The case turns on the distinction that bGP selection is policy-driven and is not equivalent to IGP least-hop routing. Apply this concrete engineering step: Trace the applicable BGP route-selection steps and local policies. An acceptable verification outcome is: The chosen path matches the configured preference and applicable attributes.

Incorrect Answers

A:

This response would target a different source scenario: A BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It cannot establish the current acceptance requirement, which is: The chosen path matches the configured preference and applicable attributes. The relevant action is: Trace the applicable BGP route-selection steps and local policies.

B:

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.

C:

The alternative addresses an engineer assumes both routers must reach Full with every speaker on a broadcast network, 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.

Question 42

A route shows as active but the interface destination still drops traffic after an interface move. What implementation step and validation result should be selected?

  1. Repair: Inspect effective group and neighbor export policy evaluation order. Check: A neighbor route view confirms the approved community-tagged routes are sent.
  2. Change: Separate route-selection and lookup-table changes and test each with candidate configuration. Test: The rollback and candidate checks show the exact intended RIB and FIB outcomes.
  3. Implement: Compare installed forwarding entries with interface operational status and adjacency resolution. Verify: A test packet follows the expected active forwarding next hop and interface.
  4. Control: Review route preference before considering equivalent forwarding paths. Accepted result: The selected path and its preference match the intended backup policy.

Explanation

Correct Answer

C:

Correct diagnosis: Forwarding-table and interface evidence localize faults beyond RIB reachability. The appropriate action is: Compare installed forwarding entries with interface operational status and adjacency resolution. The follow-up evidence required is: A test packet follows the expected active forwarding next hop and interface.

Incorrect Answers

A:

Policy inheritance and term action order affect BGP route advertisement describes a neighboring protocol concern. In this case the controlling fact is forwarding-table and interface evidence localize faults beyond RIB reachability. A correct remediation would compare installed forwarding entries with interface operational status and adjacency resolution and demonstrate: A test packet follows the expected active forwarding next hop and interface.

B:

The proposed principle concerns another network fault: Small reversible route-policy changes simplify troubleshooting and rollback. Here, forwarding-table and interface evidence localize faults beyond RIB reachability. The most direct correction is to compare installed forwarding entries with interface operational status and adjacency resolution, confirmed by a test packet follows the expected active forwarding next hop and interface.

D:

This response would target a different source scenario: Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. It cannot establish the current acceptance requirement, which is: A test packet follows the expected active forwarding next hop and interface. The relevant action is: Compare installed forwarding entries with interface operational status and adjacency resolution.

Question 43

Two network services use identical customer VLAN IDs and the team assumes their frames must share one L2 broadcast domain. What is the most defensible network engineering correction?

  1. Corrective action: Separate customer bridge domains and validate virtual-switch membership.
  2. Apply this control: Separate provider service identification from customer VLAN identifiers.
  3. Remediation: Explain root and alternate roles in a loop-free spanning-tree topology.
  4. Recommended change: Distinguish access port traffic from trunk tagging behavior.

Explanation

Correct Answer

B:

Underlying cause: A customer VLAN tag can be scoped by access interface and provider service context. Corrective action: separate provider service identification from customer VLAN identifiers. Verify the outcome: The overlapping customer IDs remain isolated within their designated provider services.

Incorrect Answers

A:

The alternative addresses a customer bridge-domain spans two isolated customers due to reusing a virtual switch without tenant boundaries, not the present root cause. Here the selected correction must reflect a customer VLAN tag can be scoped by access interface and provider service context. Test for: The overlapping customer IDs remain isolated within their designated provider services.

C:

This option overlooks the decisive condition. Its supporting principle is a redundant alternate path can remain nonforwarding until a failure changes roles, 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:

Port mode determines which customer frames are tagged or untagged at the boundary 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 44

An engineer assumes both routers must reach Full with every speaker on a broadcast network. What assessment accurately links the fault to its correction?

  1. Root issue: OSPF DR selection depends on eligible routers and the current election event. Correction: Review router priorities and the nonpreemptive properties of DR elections.
  2. Cause: IS-IS route dissemination follows hierarchical level boundaries. Response: Place the correct L1/L2 boundary and evaluate flooding scope.
  3. Diagnosis: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Action: Compare area, interface mode, timers, authentication and physical status on both endpoints.
  4. Explanation: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. Repair: Check the expected DR/BDR versus DROther neighbor-state relationships.

Explanation

Correct Answer

D:

Correct diagnosis: OSPF broadcast topology reduces unnecessary full adjacency mesh formation. The appropriate action is: Check the expected DR/BDR versus DROther neighbor-state relationships. The follow-up evidence required is: The neighbor states match expected DR roles and routing converges.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A broadcast OSPF segment experiences repeated DR elections after interface priority changes. The current case specifically calls for: Check the expected DR/BDR versus DROther neighbor-state relationships. The required observed result is: The neighbor states match expected DR roles and routing converges.

B:

This response would target a different source scenario: A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. 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 area, interface mode, timers, authentication and physical status on both endpoints is a relevant step for the separate scenario in which a new OSPF uplink remains down at the adjacency stage after a router replacement. 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.

Question 45

A Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected. What observable result most directly verifies the intended configuration?

  1. Acceptance check: A topology test leaves one redundant path nonforwarding and traffic remains reachable.
  2. The test confirms that the intended device is root under the tested priorities and tie-breakers.
  3. Expected observation: A region status check shows the intended shared instance mapping.
  4. Verification result: The active configuration and forwarding table reflect the approved VLAN change.

Explanation

Correct Answer

A:

The critical observation is: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Correct it by taking this action: Enable the appropriate spanning-tree protection and verify the blocked redundant path. Confirm the outcome with: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

Incorrect Answers

B:

Traditional spanning-tree root election favors the lowest bridge ID describes a neighboring protocol concern. In this case the controlling fact is spanning tree prevents forwarding loops by selecting a loop-free active topology. A correct remediation would enable the appropriate spanning-tree protection and verify the blocked redundant path and demonstrate: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

C:

The proposed principle concerns another network fault: MSTP region agreement affects how instances interoperate across links. Here, spanning tree prevents forwarding loops by selecting a loop-free active topology. The most direct correction is to enable the appropriate spanning-tree protection and verify the blocked redundant path, confirmed by a topology test leaves one redundant path nonforwarding and traffic remains reachable.

D:

That result would be useful for a different failure, namely: A virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed. The current case specifically calls for: Enable the appropriate spanning-tree protection and verify the blocked redundant path. The required observed result is: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

Question 46

A router has an IPv6 default route but no usable next-hop reachability on the egress link. What implementation step and validation result should be selected?

  1. Change: Inspect link quality, interface settings and DIS state before forcing election behavior. Test: A stable neighbor and LAN LSP remain after link faults are corrected.
  2. Implement: Inspect IPv6 reachability TLVs, family configuration and active inet6 route state. Verify: The remote PE learns and uses the intended IPv6 prefix.
  3. Control: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. Accepted result: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.
  4. Action: Confirm the IPv6 next-hop adjacency and active routing entry. Evidence: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

Explanation

Correct Answer

D:

This is the model-intended best choice because a configured IPv6 static route still depends on reachable forwarding next hops. The targeted correction is to confirm the IPv6 next-hop adjacency and active routing entry. Validate it by observing that the IPv6 FIB resolves the intended next hop and a test packet crosses the link.

Incorrect Answers

A:

Inspect link quality, interface settings and DIS state before forcing election behavior is a relevant step for the separate scenario in which an IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. It does not directly fix this case. Instead confirm the IPv6 next-hop adjacency and active routing entry; verify: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

B:

The alternative addresses an IS-IS change carries IPv4 traffic but a new IPv6 prefix is missing from a remote PE, not the present root cause. Here the selected correction must reflect a configured IPv6 static route still depends on reachable forwarding next hops. Test for: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

C:

This answer would be more suitable when a service provider tunnels IPv6 over an IPv4 core but expects native IPv6 forwarding at every transit hop, where the corrective action is to model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. The failure here is different: A configured IPv6 static route still depends on reachable forwarding next hops. Required validation: The IPv6 FIB resolves the intended next hop and a test packet crosses the link.

Question 47

Layer 2 forwarding is disrupted during Routing Engine replacement even though high availability was enabled for routing. Which cause-and-remedy pairing reflects the observed problem?

  1. Diagnosis: Failover depends on compatible virtual router configuration and observable primary loss. Action: Check VRRP group, interface, priority, advertisements and tracking conditions.
  2. Explanation: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Repair: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane.
  3. Fault mechanism: OSPF normally prefers the least accumulated metric to a destination. Remediation: Revisit additive path cost and verify SPF outcomes across alternative links.
  4. Root issue: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Correction: Evaluate nonstop bridging together with the supported Routing Engine redundancy design.

Explanation

Correct Answer

B:

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:

The proposed principle concerns another network fault: Failover depends on compatible virtual router configuration and observable primary loss. Here, layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. The most direct correction is to inspect whether nonstop bridging is available and configured for the relevant L2 control plane, confirmed by a controlled switchover retains the expected bridge state and host connectivity.

C:

This response would target a different source scenario: A branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. 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.

D:

Evaluate nonstop bridging together with the supported Routing Engine redundancy design is a relevant step for the separate scenario in which an Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. 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.

Question 48

An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. Which cause-and-remedy pairing reflects the observed problem?

  1. Cause: Compatible IS-IS levels and area information determine available adjacency types. Response: Compare interface level settings and area configuration.
  2. Diagnosis: IS-IS Level 1 adjacency formation depends on common area context. Action: Verify compatible area membership or use the designed Level 2 boundary.
  3. Explanation: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. Repair: Inspect link quality, interface settings and DIS state before forcing election behavior.
  4. Fault mechanism: OSPF DR selection depends on eligible routers and the current election event. Remediation: Review router priorities and the nonpreemptive properties of DR elections.

Explanation

Correct Answer

B:

Correct diagnosis: IS-IS Level 1 adjacency formation depends on common area context. The appropriate action is: Verify compatible area membership or use the designed Level 2 boundary. The follow-up evidence required is: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Incorrect Answers

A:

This answer would be more suitable when an IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment, where the corrective action is to compare interface level settings and area configuration. The failure here is different: IS-IS Level 1 adjacency formation depends on common area context. Required validation: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

C:

Frequent topology churn can stem from physical and configuration issues rather than DIS alone describes a neighboring protocol concern. In this case the controlling fact is iS-IS Level 1 adjacency formation depends on common area context. A correct remediation would verify compatible area membership or use the designed Level 2 boundary and demonstrate: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

D:

The proposed principle concerns another network fault: OSPF DR selection depends on eligible routers and the current election event. Here, iS-IS Level 1 adjacency formation depends on common area context. The most direct correction is to verify compatible area membership or use the designed Level 2 boundary, confirmed by the intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Question 49

An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. Which statement identifies the key design assumption that failed?

  1. Protocol behavior: Communities are policy signaling metadata and not the packet-forwarding next hop themselves.
  2. Underlying principle: Aggressive liveness settings can magnify loss or processing delays.
  3. Root design issue: BGP MED influence is conditional on the receiving network's path selection rules.
  4. The governing rule is: MPLS forwarding relies on label bindings and compatible next-hop state.

Explanation

Correct Answer

C:

The critical observation is: BGP MED influence is conditional on the receiving network's path selection rules. Correct it by taking this action: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. Confirm the outcome with: A controlled route lookup confirms the neighbor's actual selected entry path.

Incorrect Answers

A:

This response would target a different source scenario: An engineer treats a BGP community value as a standalone forwarding next hop. It cannot establish the current acceptance requirement, which is: A controlled route lookup confirms the neighbor's actual selected entry path. The relevant action is: Distinguish an advertised inbound hint from neighboring-AS route policy decisions.

B:

Compare negotiated timers and protocol logs with routing-engine and packet conditions is a relevant step for the separate scenario in which an engineer modifies BGP keepalive or hold timers and the session flaps during CPU pressure. It does not directly fix this case. Instead distinguish an advertised inbound hint from neighboring-AS route policy decisions; verify: A controlled route lookup confirms the neighbor's actual selected entry path.

D:

This answer would be more suitable when a provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table, where the corrective action is to distinguish IP RIB entries from label forwarding information and LSP resolution. The failure here is different: BGP MED influence is conditional on the receiving network's path selection rules. Required validation: A controlled route lookup confirms the neighbor's actual selected entry path.

Question 50

A dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature. Which protocol behavior most directly determines the correct diagnosis?

  1. The key distinction is: OSPF broadcast topology reduces unnecessary full adjacency mesh formation.
  2. Protocol behavior: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity.
  3. Underlying principle: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane.
  4. Root design issue: NSR and graceful restart on the local restarting device are different approaches and can conflict.

Explanation

Correct Answer

C:

Correct diagnosis: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. The appropriate action is: Differentiate forwarding continuity under GRES from routing-protocol state preservation. The follow-up evidence required is: A switchover test assesses both packet forwarding and routing neighbor continuity.

Incorrect Answers

A:

OSPF broadcast topology reduces unnecessary full adjacency mesh formation describes a neighboring protocol concern. In this case the controlling fact is gRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. A correct remediation would differentiate forwarding continuity under GRES from routing-protocol state preservation and demonstrate: A switchover test assesses both packet forwarding and routing neighbor continuity.

B:

The proposed principle concerns another network fault: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Here, gRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane. The most direct correction is to differentiate forwarding continuity under GRES from routing-protocol state preservation, confirmed by a switchover test assesses both packet forwarding and routing neighbor continuity.

D:

This response would target a different source scenario: A provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device. It cannot establish the current acceptance requirement, which is: A switchover test assesses both packet forwarding and routing neighbor continuity. The relevant action is: Differentiate forwarding continuity under GRES from routing-protocol state preservation.

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