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 69

Question 680

An OSPF route appears longer than expected after failover because a backup link's cost was never verified. What is the primary routing or switching concept illustrated?

  1. Root design issue: OSPF route selection follows each router's synchronized topology view.
  2. The governing rule is: Area mismatch can affect Level 1 adjacency even when packets are received.
  3. The key distinction is: Failover paths are governed by their actual configured metrics.
  4. Protocol behavior: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Failover paths are governed by their actual configured metrics. Remedy: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. Proof: When the primary fails the documented backup path is selected without loops.

Incorrect Answers

A:

This answer would be more suitable when a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, where the corrective action is to inspect link-state databases and SPF output on affected routers. The failure here is different: Failover paths are governed by their actual configured metrics. Required validation: When the primary fails the documented backup path is selected without loops.

B:

This option overlooks the decisive condition. Its supporting principle is area mismatch can affect Level 1 adjacency even when packets are received, while this scenario depends on failover paths are governed by their actual configured metrics. Verify the correction with: When the primary fails the documented backup path is selected without loops.

D:

The proposed principle concerns another network fault: OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone. Here, failover paths are governed by their actual configured metrics. The most direct correction is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs, confirmed by when the primary fails the documented backup path is selected without loops.

Question 681

An engineer expects a GRE tunnel to preserve the same maximum payload size as a native Ethernet path. What implementation step and validation result should be selected?

  1. Action: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing. Evidence: Each service test packet reaches its assigned tunnel context.
  2. Repair: Verify configured tunnel source and destination and their active underlay routing. Check: The tunnel endpoints pass test traffic after source correction.
  3. Change: Account for outer IP and GRE header overhead in the MTU design. Test: A large packet test respects the effective tunnel MTU without unwanted loss.
  4. Implement: Enable and verify the intended IPv6 address-family reachability advertisements. Verify: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

Explanation

Correct Answer

C:

The critical observation is: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Correct it by taking this action: Account for outer IP and GRE header overhead in the MTU design. Confirm the outcome with: A large packet test respects the effective tunnel MTU without unwanted loss.

Incorrect Answers

A:

This response would target a different source scenario: Two GRE tunnels share source and destination addresses while the design assumes ordinary routing will distinguish the services automatically. It cannot establish the current acceptance requirement, which is: A large packet test respects the effective tunnel MTU without unwanted loss. The relevant action is: Account for outer IP and GRE header overhead in the MTU design.

B:

Verify configured tunnel source and destination and their active underlay routing is a relevant step for the separate scenario in which a GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. It does not directly fix this case. Instead account for outer IP and GRE header overhead in the MTU design; verify: A large packet test respects the effective tunnel MTU without unwanted loss.

D:

This answer would be more suitable when an IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled, where the corrective action is to enable and verify the intended IPv6 address-family reachability advertisements. The failure here is different: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Required validation: A large packet test respects the effective tunnel MTU without unwanted loss.

Question 682

A VRRP backup router does not take over when the primary gateway interface is disabled. Which technical distinction best describes the observed symptom?

  1. Protocol behavior: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity.
  2. Underlying principle: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches.
  3. Root design issue: Failover depends on compatible virtual router configuration and observable primary loss.
  4. The governing rule is: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments.

Explanation

Correct Answer

C:

Correct diagnosis: Failover depends on compatible virtual router configuration and observable primary loss. The appropriate action is: Check VRRP group, interface, priority, advertisements and tracking conditions. The follow-up evidence required is: The backup assumes master role and clients retain access to the virtual gateway.

Incorrect Answers

A:

Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity describes a neighboring protocol concern. In this case the controlling fact is failover depends on compatible virtual router configuration and observable primary loss. A correct remediation would check VRRP group, interface, priority, advertisements and tracking conditions and demonstrate: The backup assumes master role and clients retain access to the virtual gateway.

B:

The proposed principle concerns another network fault: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Here, failover depends on compatible virtual router configuration and observable primary loss. The most direct correction is to check VRRP group, interface, priority, advertisements and tracking conditions, confirmed by the backup assumes master role and clients retain access to the virtual gateway.

D:

This response would target a different source scenario: A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. It cannot establish the current acceptance requirement, which is: The backup assumes master role and clients retain access to the virtual gateway. The relevant action is: Check VRRP group, interface, priority, advertisements and tracking conditions.

Question 683

An engineer sees that RSVP signaling succeeded and assumes all reserved bandwidth remains available for other tunnels. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: A controlled setup respects the approved link reservation policy.
  2. The test confirms that an operational path check excludes the unapproved transit link.
  3. Expected observation: The rollback and candidate checks show the exact intended RIB and FIB outcomes.
  4. Verification result: A capture identifies the label used at each transit stage.

Explanation

Correct Answer

A:

The case turns on the distinction that rSVP resource reservation may affect which additional constrained LSPs can be admitted. Apply this concrete engineering step: Distinguish signaling reservations from physical link speed and admission control. An acceptable verification outcome is: A controlled setup respects the approved link reservation policy.

Incorrect Answers

B:

This answer would be more suitable when an RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change, where the corrective action is to review explicit or constraint-based path selection against current resource availability. 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.

C:

This option overlooks the decisive condition. Its supporting principle is small reversible route-policy changes simplify troubleshooting and rollback, 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:

Outer and inner labels can have distinct transport and service roles describes a neighboring protocol concern. In this case the controlling fact is rSVP resource reservation may affect which additional constrained LSPs can be admitted. A correct remediation would distinguish signaling reservations from physical link speed and admission control and demonstrate: A controlled setup respects the approved link reservation policy.

Question 684

A Layer 2 ring floods broadcast frames repeatedly after an extra cable is connected. Which underlying Junos networking principle explains the failure?

  1. The governing rule is: Root protection can prevent undesired superior-root claims from changing root placement.
  2. The key distinction is: Spanning tree prevents forwarding loops by selecting a loop-free active topology.
  3. Protocol behavior: Layer 2 bridging does not by itself provide IP intersubnet routing.
  4. Underlying principle: STP instability can be secondary to physical link churn.

Explanation

Correct Answer

B:

Because spanning tree prevents forwarding loops by selecting a loop-free active topology, the best response is to enable the appropriate spanning-tree protection and verify the blocked redundant path. A reviewer can close the technical case only after confirming that a topology test leaves one redundant path nonforwarding and traffic remains reachable.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A carrier attachment must not allow a customer switch to become the provider's root bridge. 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.

C:

Deploy or validate an integrated routing and bridging L3 interface and gateway is a relevant step for the separate scenario in which a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain. It does not directly fix this case. Instead enable the appropriate spanning-tree protection and verify the blocked redundant path; verify: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

D:

The alternative addresses an RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement, not the present root cause. Here the selected correction must reflect spanning tree prevents forwarding loops by selecting a loop-free active topology. Test for: A topology test leaves one redundant path nonforwarding and traffic remains reachable.

Question 685

A carrier receives the same source MAC from two access ports and sees frequent forwarding-table moves. What is the most defensible network engineering correction?

  1. Apply this control: Investigate MAC movement, loops and correct bridge-domain membership.
  2. Remediation: Trace trunk authorization, bridge-domain membership and MAC learning across the path.
  3. Recommended change: Review root protection at the provider-facing boundary.
  4. Next step: Review MAC learning and unknown-unicast handling within the correct bridge domain.

Explanation

Correct Answer

A:

The critical observation is: MAC learning reflects observed source location and may churn during loops or mobility. Correct it by taking this action: Investigate MAC movement, loops and correct bridge-domain membership. Confirm the outcome with: The MAC table stabilizes on the authorized port after loop or miswire correction.

Incorrect Answers

B:

A working IRB gateway does not validate all L2 paths and trunk members describes a neighboring protocol concern. In this case the controlling fact is mAC learning reflects observed source location and may churn during loops or mobility. A correct remediation would investigate MAC movement, loops and correct bridge-domain membership and demonstrate: The MAC table stabilizes on the authorized port after loop or miswire correction.

C:

The proposed principle concerns another network fault: Root protection can prevent undesired superior-root claims from changing root placement. Here, mAC learning reflects observed source location and may churn during loops or mobility. The most direct correction is to investigate MAC movement, loops and correct bridge-domain membership, confirmed by the MAC table stabilizes on the authorized port after loop or miswire correction.

D:

That result would be useful for a different failure, namely: A provider switch receives an unknown destination MAC and a new engineer expects it to unicast to a random uplink. The current case specifically calls for: Investigate MAC movement, loops and correct bridge-domain membership. The required observed result is: The MAC table stabilizes on the authorized port after loop or miswire correction.

Question 686

A BGP export policy matches a community but no routes leave the peer after a group-level policy reorder. What assessment accurately links the fault to its correction?

  1. Cause: OSPF route type and LSA scope depend on where routing information originates. Response: Distinguish internal LSAs from externally originated route information.
  2. Diagnosis: iBGP scaling mechanisms reduce the full-mesh session requirement. Action: Evaluate route reflection with defined cluster and client boundaries.
  3. Explanation: Policy inheritance and term action order affect BGP route advertisement. Repair: Inspect effective group and neighbor export policy evaluation order.
  4. Fault mechanism: Aggressive liveness settings can magnify loss or processing delays. Remediation: Compare negotiated timers and protocol logs with routing-engine and packet conditions.

Explanation

Correct Answer

C:

Because policy inheritance and term action order affect BGP route advertisement, the best response is to inspect effective group and neighbor export policy evaluation order. A reviewer can close the technical case only after confirming that a neighbor route view confirms the approved community-tagged routes are sent.

Incorrect Answers

A:

Distinguish internal LSAs from externally originated route information is a relevant step for the separate scenario in which a link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. It does not directly fix this case. Instead inspect effective group and neighbor export policy evaluation order; verify: A neighbor route view confirms the approved community-tagged routes are sent.

B:

The alternative addresses a small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added, not the present root cause. Here the selected correction must reflect policy inheritance and term action order affect BGP route advertisement. Test for: A neighbor route view confirms the approved community-tagged routes are sent.

D:

This option overlooks the decisive condition. Its supporting principle is aggressive liveness settings can magnify loss or processing delays, while this scenario depends on policy inheritance and term action order affect BGP route advertisement. Verify the correction with: A neighbor route view confirms the approved community-tagged routes are sent.

Question 687

An LDP-signaled LSP fails when the IGP route to the remote loopback disappears. What assessment accurately links the fault to its correction?

  1. Root issue: Labels are generally meaningful within the forwarding context where they are allocated. Correction: Explain local label significance and neighbor label binding.
  2. Cause: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Response: Review EBGP multihop transport reachability and session parameters.
  3. Diagnosis: End-to-end signaling state alone cannot pinpoint a data-plane label failure. Action: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  4. Explanation: LDP label bindings are useful only with a functional path to the FEC next hop. Repair: Review LDP dependence on reachability and routing of the transport endpoints.

Explanation

Correct Answer

D:

Underlying cause: LDP label bindings are useful only with a functional path to the FEC next hop. Corrective action: review LDP dependence on reachability and routing of the transport endpoints. Verify the outcome: The restored IGP path permits LDP forwarding to the remote endpoint.

Incorrect Answers

A:

The proposed principle concerns another network fault: Labels are generally meaningful within the forwarding context where they are allocated. Here, lDP label bindings are useful only with a functional path to the FEC next hop. The most direct correction is to review LDP dependence on reachability and routing of the transport endpoints, confirmed by the restored IGP path permits LDP forwarding to the remote endpoint.

B:

That result would be useful for a different failure, namely: A multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. The current case specifically calls for: Review LDP dependence on reachability and routing of the transport endpoints. The required observed result is: The restored IGP path permits LDP forwarding to the remote endpoint.

C:

This response would target a different source scenario: A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. It cannot establish the current acceptance requirement, which is: The restored IGP path permits LDP forwarding to the remote endpoint. The relevant action is: Review LDP dependence on reachability and routing of the transport endpoints.

Question 688

A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. What assessment accurately links the fault to its correction?

  1. Fault mechanism: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Remediation: Review segment identifiers and forwarding under SR-MPLS.
  2. Root issue: LDP label bindings are useful only with a functional path to the FEC next hop. Correction: Review LDP dependence on reachability and routing of the transport endpoints.
  3. Cause: Route preference determines the selected route before any multipath decision. Response: Review route preference before considering equivalent forwarding paths.
  4. Diagnosis: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Action: Review reservation constraints and available resources rather than resetting all label sessions.

Explanation

Correct Answer

A:

This is the model-intended best choice because sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. The targeted correction is to review segment identifiers and forwarding under SR-MPLS. Validate it by observing that a test packet follows its segment list through installed SR forwarding.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is lDP label bindings are useful only with a functional path to the FEC next hop, while this scenario depends on sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Verify the correction with: A test packet follows its segment list through installed SR forwarding.

C:

Route preference determines the selected route before any multipath decision describes a neighboring protocol concern. In this case the controlling fact is sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. A correct remediation would review segment identifiers and forwarding under SR-MPLS and demonstrate: A test packet follows its segment list through installed SR forwarding.

D:

The proposed principle concerns another network fault: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Here, sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. The most direct correction is to review segment identifiers and forwarding under SR-MPLS, confirmed by a test packet follows its segment list through installed SR forwarding.

Question 689

Small probes pass through GRE but large customer packets are intermittently dropped. Which corrective action and confirmation pair is most appropriate?

  1. Change: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing. Test: Each service test packet reaches its assigned tunnel context.
  2. Implement: Verify configured tunnel source and destination and their active underlay routing. Verify: The tunnel endpoints pass test traffic after source correction.
  3. Control: Test effective MTU and path MTU discovery across the encapsulated route. Accepted result: A controlled large-payload test succeeds after MTU or MSS adjustment.
  4. Action: Review LDP dependence on reachability and routing of the transport endpoints. Evidence: The restored IGP path permits LDP forwarding to the remote endpoint.

Explanation

Correct Answer

C:

The critical observation is: GRE encapsulation overhead can expose MTU blackholes for larger payloads. Correct it by taking this action: Test effective MTU and path MTU discovery across the encapsulated route. Confirm the outcome with: A controlled large-payload test succeeds after MTU or MSS adjustment.

Incorrect Answers

A:

This response would target a different source scenario: Two GRE tunnels share source and destination addresses while the design assumes ordinary routing will distinguish the services automatically. It cannot establish the current acceptance requirement, which is: A controlled large-payload test succeeds after MTU or MSS adjustment. The relevant action is: Test effective MTU and path MTU discovery across the encapsulated route.

B:

Verify configured tunnel source and destination and their active underlay routing is a relevant step for the separate scenario in which a GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. It does not directly fix this case. Instead test effective MTU and path MTU discovery across the encapsulated route; verify: A controlled large-payload test succeeds after MTU or MSS adjustment.

D:

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: GRE encapsulation overhead can expose MTU blackholes for larger payloads. Required validation: A controlled large-payload test succeeds after MTU or MSS adjustment.

Question 690

Two GRE tunnels share source and destination addresses while the design assumes ordinary routing will distinguish the services automatically. Which cause-and-remedy pairing reflects the observed problem?

  1. Diagnosis: Tunnel endpoint parameters must correspond to actual reachable interfaces. Action: Verify configured tunnel source and destination and their active underlay routing.
  2. Explanation: Tunneling carries one protocol over an underlay that may not route that payload natively. Repair: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport.
  3. Fault mechanism: Tunnel identification and routing-instance separation must be explicit in overlapping designs. Remediation: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing.
  4. Root issue: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Correction: Distinguish the inner routed payload from outer unicast encapsulation.

Explanation

Correct Answer

C:

Correct diagnosis: Tunnel identification and routing-instance separation must be explicit in overlapping designs. The appropriate action is: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing. The follow-up evidence required is: Each service test packet reaches its assigned tunnel context.

Incorrect Answers

A:

Tunnel endpoint parameters must correspond to actual reachable interfaces describes a neighboring protocol concern. In this case the controlling fact is tunnel identification and routing-instance separation must be explicit in overlapping designs. A correct remediation would review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing and demonstrate: Each service test packet reaches its assigned tunnel context.

B:

The proposed principle concerns another network fault: Tunneling carries one protocol over an underlay that may not route that payload natively. Here, tunnel identification and routing-instance separation must be explicit in overlapping designs. The most direct correction is to review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing, confirmed by each service test packet reaches its assigned tunnel context.

D:

This response would target a different source scenario: An operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. It cannot establish the current acceptance requirement, which is: Each service test packet reaches its assigned tunnel context. The relevant action is: Review tunnel identifiers, endpoint uniqueness and supported platform demultiplexing.

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