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 63

Question 620

An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. Which combined repair and acceptance criterion is strongest?

  1. Repair: Split export policy by authorized customer scope and verify negative advertisements. Check: The unauthorized customer receives no leaked prefixes in a route advertisement check.
  2. Change: Align the area membership and verify OSPF interface settings on both sides. Test: The peers progress to the expected adjacency state and exchange LSAs.
  3. Implement: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. Verify: A controlled route lookup confirms the neighbor's actual selected entry path.
  4. Control: Review BGP next-hop reachability and explicit next-hop handling. Accepted result: The internal peer has a valid route to the BGP next hop and installs the prefix.

Explanation

Correct Answer

C:

This is the model-intended best choice because bGP MED influence is conditional on the receiving network's path selection rules. The targeted correction is to distinguish an advertised inbound hint from neighboring-AS route policy decisions. Validate it by observing that a controlled route lookup confirms the neighbor's actual selected entry path.

Incorrect Answers

A:

That result would be useful for a different failure, namely: One customer’s new prefixes are advertised to a second unrelated customer via a shared export group. The current case specifically calls for: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. The required observed result is: A controlled route lookup confirms the neighbor's actual selected entry path.

B:

This response would target a different source scenario: Two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship. 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.

D:

The alternative addresses a provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP, not the present root cause. Here the selected correction must reflect bGP MED influence is conditional on the receiving network's path selection rules. Test for: A controlled route lookup confirms the neighbor's actual selected entry path.

Question 621

A provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. What remediation is most directly applicable?

  1. Corrective action: Review explicit or constraint-based path selection against current resource availability.
  2. Apply this control: Check SR label advertisements, segment configuration and installed MPLS forwarding.
  3. Remediation: Inspect the full MPLS label stack and outgoing label operation.
  4. Recommended change: Separate route-selection and lookup-table changes and test each with candidate configuration.

Explanation

Correct Answer

B:

The case turns on the distinction that lDP and SR-MPLS may coexist but each needs its own valid label/route state. Apply this concrete engineering step: Check SR label advertisements, segment configuration and installed MPLS forwarding. An acceptable verification outcome is: The intended SR transport path forwards without unintended dependence on the retired LDP path.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is traffic-engineering intent must be reflected in the signaled operational LSP path, while this scenario depends on lDP and SR-MPLS may coexist but each needs its own valid label/route state. Verify the correction with: The intended SR transport path forwards without unintended dependence on the retired LDP path.

C:

The proposed principle concerns another network fault: Outer and inner labels can have distinct transport and service roles. Here, lDP and SR-MPLS may coexist but each needs its own valid label/route state. The most direct correction is to check SR label advertisements, segment configuration and installed MPLS forwarding, confirmed by the intended SR transport path forwards without unintended dependence on the retired LDP path.

D:

That result would be useful for a different failure, namely: A policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit. The current case specifically calls for: Check SR label advertisements, segment configuration and installed MPLS forwarding. The required observed result is: The intended SR transport path forwards without unintended dependence on the retired LDP path.

Question 622

An operator assumes MPLS labels are globally unique across the provider network. Which next action best resolves this observed routing or switching failure?

  1. Next step: Review reservation constraints and available resources rather than resetting all label sessions.
  2. Corrective action: Explain local label significance and neighbor label binding.
  3. Apply this control: Review LDP dependence on reachability and routing of the transport endpoints.
  4. Remediation: Investigate AS-path loop prevention rather than overriding it without risk review.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Labels are generally meaningful within the forwarding context where they are allocated. Remedy: Explain local label significance and neighbor label binding. Proof: A path test records locally valid incoming and outgoing label mappings.

Incorrect Answers

A:

Review reservation constraints and available resources rather than resetting all label sessions is a relevant step for the separate scenario in which an RSVP-signaled LSP enters a failed state after a link bandwidth change. It does not directly fix this case. Instead explain local label significance and neighbor label binding; verify: A path test records locally valid incoming and outgoing label mappings.

C:

This answer would be more suitable when an LDP-signaled LSP fails when the IGP route to the remote loopback disappears, where the corrective action is to review LDP dependence on reachability and routing of the transport endpoints. The failure here is different: Labels are generally meaningful within the forwarding context where they are allocated. Required validation: A path test records locally valid incoming and outgoing label mappings.

D:

This option overlooks the decisive condition. Its supporting principle is bGP AS-path information can prevent routes from looping into an AS, while this scenario depends on labels are generally meaningful within the forwarding context where they are allocated. Verify the correction with: A path test records locally valid incoming and outgoing label mappings.

Question 623

A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Coordinate authentication parameters and test the key change under maintenance controls.
  2. Next step: Verify compatible area membership or use the designed Level 2 boundary.
  3. Corrective action: Compare path metrics and each router's route selection before altering LSP state.
  4. Apply this control: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

Explanation

Correct Answer

D:

Underlying cause: IS-IS packet exchange and transport differ from OSPF over IP. Corrective action: recognize IS-IS as a link-layer routing protocol with its own PDUs. Verify the outcome: A link-level packet trace observes the relevant IS-IS PDUs.

Incorrect Answers

A:

The proposed principle concerns another network fault: Authentication mismatches can reject otherwise valid OSPF protocol packets. Here, iS-IS packet exchange and transport differ from OSPF over IP. The most direct correction is to recognize IS-IS as a link-layer routing protocol with its own PDUs, confirmed by a link-level packet trace observes the relevant IS-IS PDUs.

B:

That result would be useful for a different failure, namely: An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. The current case specifically calls for: Recognize IS-IS as a link-layer routing protocol with its own PDUs. The required observed result is: A link-level packet trace observes the relevant IS-IS PDUs.

C:

This response would target a different source scenario: An IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. It cannot establish the current acceptance requirement, which is: A link-level packet trace observes the relevant IS-IS PDUs. The relevant action is: Recognize IS-IS as a link-layer routing protocol with its own PDUs.

Question 624

A service provider tunnels IPv6 over an IPv4 core but expects native IPv6 forwarding at every transit hop. Which technical explanation and controlled action address the symptom?

  1. Explanation: More-specific routes can override an otherwise healthy IPv6 fallback. Repair: Inspect longest-match results and forwarding routes for the specific destination.
  2. Fault mechanism: Tunneling carries one protocol over an underlay that may not route that payload natively. Remediation: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport.
  3. Root issue: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Correction: Apply longest-prefix-match route lookup to the IPv6 destination.
  4. Cause: A backup path requires functional forwarding, not merely topology presence. Response: Rehearse the failure and inspect active next hops and IS-IS route changes.

Explanation

Correct Answer

B:

Correct diagnosis: Tunneling carries one protocol over an underlay that may not route that payload natively. The appropriate action is: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. The follow-up evidence required is: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

Incorrect Answers

A:

This answer would be more suitable when a new IPv6 static backup route is configured but a more-specific route points into a blackhole, where the corrective action is to inspect longest-match results and forwarding routes for the specific destination. The failure here is different: Tunneling carries one protocol over an underlay that may not route that payload natively. Required validation: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

C:

IPv6 route selection follows prefix matching and route eligibility, not textual address order describes a neighboring protocol concern. In this case the controlling fact is tunneling carries one protocol over an underlay that may not route that payload natively. A correct remediation would model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport and demonstrate: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

D:

The proposed principle concerns another network fault: A backup path requires functional forwarding, not merely topology presence. Here, tunneling carries one protocol over an underlay that may not route that payload natively. The most direct correction is to model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport, confirmed by a tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

Question 625

Two equal-cost next hops exist but a customer assumes every successive packet must alternate between links. What assessment accurately links the fault to its correction?

  1. Diagnosis: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Action: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane.
  2. Explanation: A configured static route need not become usable forwarding state when its next hop cannot resolve. Repair: Verify recursive next-hop reachability before relying on the static route.
  3. Fault mechanism: BGP edge hygiene protects the routing domain from unauthorized reachability. Remediation: Tighten customer import route filtering and test permitted prefix lengths.
  4. Root issue: Instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Correction: Run route and connectivity checks in the explicitly intended routing instance.

Explanation

Correct Answer

A:

Underlying cause: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Corrective action: distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane. Verify the outcome: A controlled flow test verifies the selected load-sharing behavior.

Incorrect Answers

B:

Verify recursive next-hop reachability before relying on the static route is a relevant step for the separate scenario in which a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. It does not directly fix this case. Instead distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane; verify: A controlled flow test verifies the selected load-sharing behavior.

C:

The alternative addresses a customer advertises an unauthorized more-specific and the PE propagates it across the provider core, not the present root cause. Here the selected correction must reflect multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Test for: A controlled flow test verifies the selected load-sharing behavior.

D:

This answer would be more suitable when a provider PE can ping a customer in the master instance but probes in the tenant routing instance fail, where the corrective action is to run route and connectivity checks in the explicitly intended routing instance. The failure here is different: Multiple eligible forwarding next hops do not guarantee per-packet round-robin use. Required validation: A controlled flow test verifies the selected load-sharing behavior.

Question 626

A provider STP domain changes root when a customer sends superior BPDUs from an access port. What is the most defensible network engineering correction?

  1. Corrective action: Align region identity, revision and VLAN mapping as required.
  2. Apply this control: Review root protection at the provider-facing boundary.
  3. Remediation: Validate the usable VLAN-ID range and reserved tag values.
  4. Recommended change: Apply supported root protection at the appropriate customer-facing boundary.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Customer control traffic must not displace the authorized provider root. Remedy: Apply supported root protection at the appropriate customer-facing boundary. Proof: A superior BPDU test preserves the intended root with a logged protective state.

Incorrect Answers

A:

MSTP region agreement affects how instances interoperate across links describes a neighboring protocol concern. In this case the controlling fact is customer control traffic must not displace the authorized provider root. A correct remediation would apply supported root protection at the appropriate customer-facing boundary and demonstrate: A superior BPDU test preserves the intended root with a logged protective state.

B:

The proposed principle concerns another network fault: Root protection can prevent undesired superior-root claims from changing root placement. Here, customer control traffic must not displace the authorized provider root. The most direct correction is to apply supported root protection at the appropriate customer-facing boundary, confirmed by a superior BPDU test preserves the intended root with a logged protective state.

C:

That result would be useful for a different failure, namely: A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. The current case specifically calls for: Apply supported root protection at the appropriate customer-facing boundary. The required observed result is: A superior BPDU test preserves the intended root with a logged protective state.

Question 627

A small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added. What should the operations engineer do first to address the stated fault?

  1. Next step: Inspect link-state databases and SPF output on affected routers.
  2. Corrective action: Evaluate route reflection with defined cluster and client boundaries.
  3. Apply this control: Split export policy by authorized customer scope and verify negative advertisements.
  4. Remediation: Investigate AS-path loop prevention rather than overriding it without risk review.

Explanation

Correct Answer

B:

Underlying cause: iBGP scaling mechanisms reduce the full-mesh session requirement. Corrective action: evaluate route reflection with defined cluster and client boundaries. Verify the outcome: The route-reflector design distributes approved prefixes without unintended loops.

Incorrect Answers

A:

The alternative addresses a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, not the present root cause. Here the selected correction must reflect iBGP scaling mechanisms reduce the full-mesh session requirement. Test for: The route-reflector design distributes approved prefixes without unintended loops.

C:

This option overlooks the decisive condition. Its supporting principle is bGP group-level export policies must preserve customer routing isolation, while this scenario depends on iBGP scaling mechanisms reduce the full-mesh session requirement. Verify the correction with: The route-reflector design distributes approved prefixes without unintended loops.

D:

BGP AS-path information can prevent routes from looping into an AS describes a neighboring protocol concern. In this case the controlling fact is iBGP scaling mechanisms reduce the full-mesh session requirement. A correct remediation would evaluate route reflection with defined cluster and client boundaries and demonstrate: The route-reflector design distributes approved prefixes without unintended loops.

Question 628

A customer edge loses its OSPF neighbor after an authentication key rollover. What action-and-test pairing directly resolves the case?

  1. Implement: Coordinate authentication parameters and test the key change under maintenance controls. Verify: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.
  2. Control: Compare area, interface mode, timers, authentication and physical status on both endpoints. Accepted result: The corrected link reaches stable Full adjacency and exchanges the intended routes.
  3. Action: Define the intended route-leaking boundary between the customer's instance and the master routing table. Evidence: Each customer route is visible only in the tables approved by the design.
  4. Repair: Align the area membership and verify OSPF interface settings on both sides. Check: The peers progress to the expected adjacency state and exchange LSAs.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Authentication mismatches can reject otherwise valid OSPF protocol packets. Remedy: Coordinate authentication parameters and test the key change under maintenance controls. Proof: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Incorrect Answers

B:

This response would target a different source scenario: A new OSPF uplink remains down at the adjacency stage after a router replacement. It cannot establish the current acceptance requirement, which is: Authenticated adjacency returns and no fallback to unauthenticated operation occurs. The relevant action is: Coordinate authentication parameters and test the key change under maintenance controls.

C:

Define the intended route-leaking boundary between the customer's instance and the master routing table is a relevant step for the separate scenario in which a provider creates a customer routing instance but assumes its routes will automatically be present in the master inet.0 table. It does not directly fix this case. Instead coordinate authentication parameters and test the key change under maintenance controls; verify: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

D:

The alternative addresses two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship, not the present root cause. Here the selected correction must reflect authentication mismatches can reject otherwise valid OSPF protocol packets. Test for: Authenticated adjacency returns and no fallback to unauthenticated operation occurs.

Question 629

A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. Which technical distinction best describes the observed symptom?

  1. The governing rule is: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments.
  2. The key distinction is: VRRP provides a master and backup mechanism for a shared virtual default gateway.
  3. Protocol behavior: Forwarding-plane continuity does not prove control-plane routing continuity.
  4. Underlying principle: Spanning tree prevents forwarding loops by selecting a loop-free active topology.

Explanation

Correct Answer

A:

The critical observation is: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Correct it by taking this action: Evaluate BFD liveness detection with the associated routing protocol. Confirm the outcome with: A controlled forwarding failure is detected within the approved target.

Incorrect Answers

B:

VRRP provides a master and backup mechanism for a shared virtual default gateway describes a neighboring protocol concern. In this case the controlling fact is bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. A correct remediation would evaluate BFD liveness detection with the associated routing protocol and demonstrate: A controlled forwarding failure is detected within the approved target.

C:

The proposed principle concerns another network fault: Forwarding-plane continuity does not prove control-plane routing continuity. Here, bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. The most direct correction is to evaluate BFD liveness detection with the associated routing protocol, confirmed by a controlled forwarding failure is detected within the approved target.

D:

That result would be useful for a different failure, namely: A Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected. The current case specifically calls for: Evaluate BFD liveness detection with the associated routing protocol. The required observed result is: A controlled forwarding failure is detected within the approved target.

Question 630

An alternate uplink remains blocked after the primary path fails because expected BPDUs disappear. Which test result would best confirm a successful fix?

  1. Verification result: The corrected topology converges without opening an Ethernet loop.
  2. Closeout evidence: The intended device is root under the tested priorities and tie-breakers.
  3. Acceptance check: A region status check shows the intended shared instance mapping.
  4. The test confirms that separate tagged tests pass in both permitted VLANs.

Explanation

Correct Answer

A:

Correct diagnosis: Loop protection can prevent unsafe forwarding when control-plane information is missing. The appropriate action is: Inspect spanning-tree loop-protection events, root path and link state. The follow-up evidence required is: The corrected topology converges without opening an Ethernet loop.

Incorrect Answers

B:

The alternative addresses a switch operator treats the highest bridge ID as the guaranteed STP root, 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.

C:

This answer would be more suitable when two MSTP switches place the same VLAN into different instances due to region configuration drift, where the corrective action is to align region identity, revision and VLAN mapping as required. The failure here is different: Loop protection can prevent unsafe forwarding when control-plane information is missing. Required validation: The corrected topology converges without opening an Ethernet loop.

D:

This option overlooks the decisive condition. Its supporting principle is mAC table visibility alone does not prove trunk authorization for every VLAN, while this scenario depends on loop protection can prevent unsafe forwarding when control-plane information is missing. Verify the correction with: The corrected topology converges without opening an Ethernet loop.

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