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 73

Question 720

A provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy. What diagnosis and engineering response are most appropriate?

  1. Root issue: Routing policy controls which external reachability is injected into OSPF. Correction: Constrain redistribution and test route policy acceptance for the intended prefixes.
  2. Cause: Failover paths are governed by their actual configured metrics. Response: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.
  3. Diagnosis: Multi-area OSPF design requires attention to backbone connectivity. Action: Review hierarchical OSPF backbone attachment and area border placement.
  4. Explanation: The designated system serves LAN pseudonode advertisement and election semantics. Repair: Review current DIS election rules for the network and protocol instance.

Explanation

Correct Answer

A:

This is the model-intended best choice because routing policy controls which external reachability is injected into OSPF. The targeted correction is to constrain redistribution and test route policy acceptance for the intended prefixes. Validate it by observing that only approved external prefixes appear in the OSPF domain.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is failover paths are governed by their actual configured metrics, while this scenario depends on routing policy controls which external reachability is injected into OSPF. Verify the correction with: Only approved external prefixes appear in the OSPF domain.

C:

Multi-area OSPF design requires attention to backbone connectivity describes a neighboring protocol concern. In this case the controlling fact is routing policy controls which external reachability is injected into OSPF. A correct remediation would constrain redistribution and test route policy acceptance for the intended prefixes and demonstrate: Only approved external prefixes appear in the OSPF domain.

D:

The proposed principle concerns another network fault: The designated system serves LAN pseudonode advertisement and election semantics. Here, routing policy controls which external reachability is injected into OSPF. The most direct correction is to constrain redistribution and test route policy acceptance for the intended prefixes, confirmed by only approved external prefixes appear in the OSPF domain.

Question 721

A RIB group leak forwards a VPN service toward the wrong next hop after a route update. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Check import destinations, next-hop resolution and effective routes in every receiving table.
  2. Next step: Add a precise prefix and instance match, then inspect effective imports.
  3. Corrective action: Review hierarchical OSPF backbone attachment and area border placement.
  4. Apply this control: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.

Explanation

Correct Answer

A:

Underlying cause: Imported routes must be validated in the destination lookup context. Corrective action: check import destinations, next-hop resolution and effective routes in every receiving table. Verify the outcome: The receiving instance shows the correct route and installed next hop after correction.

Incorrect Answers

B:

Add a precise prefix and instance match, then inspect effective imports is a relevant step for the separate scenario in which a route import policy accepts more-specific destinations that should remain isolated inside a wholesale tenant. It does not directly fix this case. Instead check import destinations, next-hop resolution and effective routes in every receiving table; verify: The receiving instance shows the correct route and installed next hop after correction.

C:

The alternative addresses a router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0, not the present root cause. Here the selected correction must reflect imported routes must be validated in the destination lookup context. Test for: The receiving instance shows the correct route and installed next hop after correction.

D:

This answer would be more suitable when a summary route is advertised even though the operator expects every more-specific customer route to remain reachable, where the corrective action is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes. The failure here is different: Imported routes must be validated in the destination lookup context. Required validation: The receiving instance shows the correct route and installed next hop after correction.

Question 722

A provider switch receives an unknown destination MAC and a new engineer expects it to unicast to a random uplink. What action-and-test pairing directly resolves the case?

  1. Change: Evaluate MSTP instances and explicit VLAN-to-instance mapping. Test: Each VLAN maps to its intended instance and designated root.
  2. Implement: Review MAC learning and unknown-unicast handling within the correct bridge domain. Verify: A frame trace shows only expected domain members receive the unknown destination.
  3. Control: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. Accepted result: Separate tagged tests pass in both permitted VLANs.
  4. Action: Document VLAN-aware versus flexible tagging and unit classification requirements. Evidence: Both test logical units classify tagged traffic into their intended bridge domains.

Explanation

Correct Answer

B:

This is the model-intended best choice because bridges learn source MAC locations and flood unknown destinations within a permitted domain. The targeted correction is to review MAC learning and unknown-unicast handling within the correct bridge domain. Validate it by observing that a frame trace shows only expected domain members receive the unknown destination.

Incorrect Answers

A:

MSTP can group VLANs into multiple spanning-tree instances under shared region parameters describes a neighboring protocol concern. In this case the controlling fact is bridges learn source MAC locations and flood unknown destinations within a permitted domain. A correct remediation would review MAC learning and unknown-unicast handling within the correct bridge domain and demonstrate: A frame trace shows only expected domain members receive the unknown destination.

C:

That result would be useful for a different failure, namely: After a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink. The current case specifically calls for: Review MAC learning and unknown-unicast handling within the correct bridge domain. The required observed result is: A frame trace shows only expected domain members receive the unknown destination.

D:

This response would target a different source scenario: An Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation. It cannot establish the current acceptance requirement, which is: A frame trace shows only expected domain members receive the unknown destination. The relevant action is: Review MAC learning and unknown-unicast handling within the correct bridge domain.

Question 723

A loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. What is the most defensible network engineering correction?

  1. Apply this control: Restore the required transport route and inspect label-signaling and next-hop state.
  2. Remediation: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.
  3. Recommended change: Distinguish the MPLS shim label stack from the encapsulated payload.
  4. Next step: Inspect label-switched next-hop resolution separately from generic IP reachability.

Explanation

Correct Answer

D:

The critical observation is: A usable IP path need not supply a suitable MPLS LSP or labeled transport path. Correct it by taking this action: Inspect label-switched next-hop resolution separately from generic IP reachability. Confirm the outcome with: The labeled service route resolves after the intended LSP is restored.

Incorrect Answers

A:

The alternative addresses a route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes, not the present root cause. Here the selected correction must reflect a usable IP path need not supply a suitable MPLS LSP or labeled transport path. Test for: The labeled service route resolves after the intended LSP is restored.

B:

This answer would be more suitable when a dual-stack peer is Established but the IPv6 customer route is absent, where the corrective action is to inspect inet6 family negotiation, filters and IPv6 next-hop validity. The failure here is different: A usable IP path need not supply a suitable MPLS LSP or labeled transport path. Required validation: The labeled service route resolves after the intended LSP is restored.

C:

This option overlooks the decisive condition. Its supporting principle is mPLS forwarding typically uses labels to select the next label-switched hop, while this scenario depends on a usable IP path need not supply a suitable MPLS LSP or labeled transport path. Verify the correction with: The labeled service route resolves after the intended LSP is restored.

Question 724

A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: An authorized switchover maintains bridge control state and service reachability.
  2. Verification result: The active configuration and forwarding table reflect the approved VLAN change.
  3. Closeout evidence: The service uses a valid supported customer VLAN ID.
  4. Acceptance check: A test host reaches its gateway and an authorized remote subnet through IRB.

Explanation

Correct Answer

C:

This is the model-intended best choice because 802.1Q VLAN identifiers have reserved values and platform constraints. The targeted correction is to validate the usable VLAN-ID range and reserved tag values. Validate it by observing that the service uses a valid supported customer VLAN ID.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. The current case specifically calls for: Validate the usable VLAN-ID range and reserved tag values. The required observed result is: The service uses a valid supported customer VLAN ID.

B:

This response would target a different source scenario: A virtual switch forwarding issue persists because customer VLAN configuration was changed but never committed. It cannot establish the current acceptance requirement, which is: The service uses a valid supported customer VLAN ID. The relevant action is: Validate the usable VLAN-ID range and reserved tag values.

D:

The alternative addresses a VLAN provides local host connectivity but hosts cannot reach a different IP subnet through the bridge domain, not the present root cause. Here the selected correction must reflect 802.1Q VLAN identifiers have reserved values and platform constraints. Test for: The service uses a valid supported customer VLAN ID.

Question 725

An IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node. What implementation step and validation result should be selected?

  1. Control: Rehearse the failure and inspect active next hops and IS-IS route changes. Accepted result: The backup next hop resolves and carries test traffic after the primary link fails.
  2. Action: Distinguish IS-IS adjacency from address-family reachability advertisements. Evidence: The expected IPv6 prefix appears after family and policy review.
  3. Repair: Review current DIS election rules for the network and protocol instance. Check: The LAN's DIS and pseudonode LSP match the documented protocol state.
  4. Change: Separate session liveness from prefix acceptance and RIB installation. Test: Both neighbor state and selected prefix route evidence are verified independently.

Explanation

Correct Answer

C:

Underlying cause: The designated system serves LAN pseudonode advertisement and election semantics. Corrective action: review current DIS election rules for the network and protocol instance. Verify the outcome: The LAN's DIS and pseudonode LSP match the documented protocol state.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is a backup path requires functional forwarding, not merely topology presence, while this scenario depends on the designated system serves LAN pseudonode advertisement and election semantics. Verify the correction with: The LAN's DIS and pseudonode LSP match the documented protocol state.

B:

An adjacency can be operational while a specific family or prefix is not advertised describes a neighboring protocol concern. In this case the controlling fact is the designated system serves LAN pseudonode advertisement and election semantics. A correct remediation would review current DIS election rules for the network and protocol instance and demonstrate: The LAN's DIS and pseudonode LSP match the documented protocol state.

D:

That result would be useful for a different failure, namely: An eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed. The current case specifically calls for: Review current DIS election rules for the network and protocol instance. The required observed result is: The LAN's DIS and pseudonode LSP match the documented protocol state.

Question 726

A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. What action-and-test pairing directly resolves the case?

  1. Implement: Verify IP reachability, routing instance context, TCP transport and session authentication. Verify: The TCP peering session reaches Established and remains stable.
  2. Control: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes. Accepted result: The summary is advertised only under the approved component-route conditions.
  3. Action: Document the discard behavior and determine whether the aggregate should remain advertised. Evidence: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.
  4. Repair: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples. Check: Only the subscriber's approved traffic enters the alternate routing instance.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: Aggregation can hide individual component failures if advertisement policy is not controlled. Remedy: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes. Proof: The summary is advertised only under the approved component-route conditions.

Incorrect Answers

A:

Verify IP reachability, routing instance context, TCP transport and session authentication is a relevant step for the separate scenario in which a BGP peer is stuck in Active after a maintenance window even though the remote address is configured. It does not directly fix this case. Instead distinguish aggregate reachability from specific-route forwarding and test loss of component routes; verify: The summary is advertised only under the approved component-route conditions.

C:

This answer would be more suitable when a static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear, where the corrective action is to document the discard behavior and determine whether the aggregate should remain advertised. The failure here is different: Aggregation can hide individual component failures if advertisement policy is not controlled. Required validation: The summary is advertised only under the approved component-route conditions.

D:

This option overlooks the decisive condition. Its supporting principle is overlapping address classification makes precise route-filter and policy terms essential, while this scenario depends on aggregation can hide individual component failures if advertisement policy is not controlled. Verify the correction with: The summary is advertised only under the approved component-route conditions.

Question 727

A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. What diagnosis and engineering response are most appropriate?

  1. Explanation: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Repair: Review filter-based forwarding classification and the intended next-table selection.
  2. Fault mechanism: An upstream LSR can remove a label before the egress in an appropriate PHP design. Remediation: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  3. Root issue: RSVP-TE can signal explicit or constrained paths while ordinary LDP follows routing reachability. Correction: Separate RSVP-signaled LSP functions from LDP label distribution.
  4. Cause: A healthy transport LSP does not guarantee a correct overlay label mapping. Response: Inspect outer transport and inner service label handling separately.

Explanation

Correct Answer

B:

The critical observation is: An upstream LSR can remove a label before the egress in an appropriate PHP design. Correct it by taking this action: Recognize penultimate-hop popping as an allowed LSP forwarding behavior. Confirm the outcome with: A packet trace verifies the intended stack at the penultimate and egress hops.

Incorrect Answers

A:

The proposed principle concerns another network fault: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Here, an upstream LSR can remove a label before the egress in an appropriate PHP design. The most direct correction is to recognize penultimate-hop popping as an allowed LSP forwarding behavior, confirmed by a packet trace verifies the intended stack at the penultimate and egress hops.

C:

This response would target a different source scenario: A network design assumes RSVP and LDP use identical path signaling and traffic engineering controls. It cannot establish the current acceptance requirement, which is: A packet trace verifies the intended stack at the penultimate and egress hops. The relevant action is: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.

D:

Inspect outer transport and inner service label handling separately is a relevant step for the separate scenario in which a customer overlay fails across an MPLS core only for one service label. It does not directly fix this case. Instead recognize penultimate-hop popping as an allowed LSP forwarding behavior; verify: A packet trace verifies the intended stack at the penultimate and egress hops.

Question 728

A new IPv6 static backup route is configured but a more-specific route points into a blackhole. What diagnosis and engineering response are most appropriate?

  1. Diagnosis: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Action: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.
  2. Explanation: More-specific routes can override an otherwise healthy IPv6 fallback. Repair: Inspect longest-match results and forwarding routes for the specific destination.
  3. Fault mechanism: Policy placement determines which prefixes influence a routing table or advertisement. Remediation: Apply and verify supported route policy at the intended routing import or export boundary.
  4. Root issue: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Correction: Review the IPv6 OSPFv3 address-family and interface adjacency model.

Explanation

Correct Answer

B:

Correct diagnosis: More-specific routes can override an otherwise healthy IPv6 fallback. The appropriate action is: Inspect longest-match results and forwarding routes for the specific destination. The follow-up evidence required is: The intended most-specific route changes to a valid next hop during failover.

Incorrect Answers

A:

This answer would be more suitable when an IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution, where the corrective action is to verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path. The failure here is different: More-specific routes can override an otherwise healthy IPv6 fallback. Required validation: The intended most-specific route changes to a valid next hop during failover.

C:

Policy placement determines which prefixes influence a routing table or advertisement describes a neighboring protocol concern. In this case the controlling fact is more-specific routes can override an otherwise healthy IPv6 fallback. A correct remediation would inspect longest-match results and forwarding routes for the specific destination and demonstrate: The intended most-specific route changes to a valid next hop during failover.

D:

The proposed principle concerns another network fault: OSPFv3 has protocol-specific requirements for neighbor exchange and IPv6 routing. Here, more-specific routes can override an otherwise healthy IPv6 fallback. The most direct correction is to inspect longest-match results and forwarding routes for the specific destination, confirmed by the intended most-specific route changes to a valid next hop during failover.

Question 729

A GRE design includes a virtual tunnel interface but omits routable IPv4 underlay access to the remote endpoint. Which post-change observation most strongly confirms the correction?

  1. Expected observation: A large packet test respects the effective tunnel MTU without unwanted loss.
  2. Verification result: The tunnel endpoints pass test traffic after source correction.
  3. Closeout evidence: A packet decode identifies label fields separately from the carried IP packet.
  4. Acceptance check: The remote tunnel endpoint is reachable through the intended underlay.

Explanation

Correct Answer

D:

The case turns on the distinction that tunnel interfaces depend on a working underlay path between endpoints. Apply this concrete engineering step: Verify reachability between tunnel source and destination addresses. An acceptable verification outcome is: The remote tunnel endpoint is reachable through the intended underlay.

Incorrect Answers

A:

This response would target a different source scenario: An engineer expects a GRE tunnel to preserve the same maximum payload size as a native Ethernet path. It cannot establish the current acceptance requirement, which is: The remote tunnel endpoint is reachable through the intended underlay. The relevant action is: Verify reachability between tunnel source and destination addresses.

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 verify reachability between tunnel source and destination addresses; verify: The remote tunnel endpoint is reachable through the intended underlay.

C:

The alternative addresses an operator expects an MPLS label to represent an entire customer IP packet header, not the present root cause. Here the selected correction must reflect tunnel interfaces depend on a working underlay path between endpoints. Test for: The remote tunnel endpoint is reachable through the intended underlay.

Question 730

One branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core. What implementation step and validation result should be selected?

  1. Control: Compare ingress label imposition with transit LFIB and egress disposition. Accepted result: A hop-by-hop labeled test locates and corrects the failing label action.
  2. Action: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints. Evidence: The remote PE service route resolves over the designated LSP.
  3. Repair: Review route-reflector client and cluster design, including loop-prevention attributes. Check: A test prefix reaches permitted clients without cycling through reflector clusters.
  4. Change: Inspect label-switched next-hop resolution separately from generic IP reachability. Test: The labeled service route resolves after the intended LSP is restored.

Explanation

Correct Answer

A:

Because successful ordinary IP forwarding does not isolate MPLS packet forwarding faults, the best response is to compare ingress label imposition with transit LFIB and egress disposition. A reviewer can close the technical case only after confirming that a hop-by-hop labeled test locates and corrects the failing label action.

Incorrect Answers

B:

The proposed principle concerns another network fault: A labeled transport next hop must be available to carry the overlay service. 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.

C:

That result would be useful for a different failure, namely: A route reflector advertises routes to the wrong clients after a change in group membership. 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:

This response would target a different source scenario: A loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. It cannot establish the current acceptance requirement, which is: A hop-by-hop labeled test locates and corrects the failing label action. The relevant action is: Compare ingress label imposition with transit LFIB and egress disposition.

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