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 57

Question 560

A policy change unexpectedly makes a backup transit provider carry most outbound traffic. Which test result would best confirm a successful fix?

  1. Acceptance check: Traffic uses the primary provider until the documented failover condition occurs.
  2. The test confirms that the TCP session establishes across the intended transport path.
  3. Expected observation: The missing client receives the correct next-hop-resolvable route.
  4. Verification result: The transit LSR selects an authorized outgoing label and interface.

Explanation

Correct Answer

A:

This is the model-intended best choice because routing policy changes can override expected primary and backup peering intent. The targeted correction is to inspect local preference, export/import inheritance and selected BGP path attributes. Validate it by observing that traffic uses the primary provider until the documented failover condition occurs.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy, while this scenario depends on routing policy changes can override expected primary and backup peering intent. Verify the correction with: Traffic uses the primary provider until the documented failover condition occurs.

C:

Route reflection can fail due to session or policy scope even when the route exists centrally describes a neighboring protocol concern. In this case the controlling fact is routing policy changes can override expected primary and backup peering intent. A correct remediation would inspect local preference, export/import inheritance and selected BGP path attributes and demonstrate: Traffic uses the primary provider until the documented failover condition occurs.

D:

The proposed principle concerns another network fault: MPLS forwarding relies on label bindings and compatible next-hop state. Here, routing policy changes can override expected primary and backup peering intent. The most direct correction is to inspect local preference, export/import inheritance and selected BGP path attributes, confirmed by traffic uses the primary provider until the documented failover condition occurs.

Question 561

Two MSTP switches place the same VLAN into different instances due to region configuration drift. Which change best corrects the failure without losing the intended design?

  1. Remediation: Review root bridge priority and MAC-based bridge identifier comparison.
  2. Recommended change: Align region identity, revision and VLAN mapping as required.
  3. Next step: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.
  4. Corrective action: Inspect member states, traffic distribution and configured minimum link expectations.

Explanation

Correct Answer

B:

The selected response implements the principle that mSTP region agreement affects how instances interoperate across links. The engineer should align region identity, revision and VLAN mapping as required. Successful confirmation means: A region status check shows the intended shared instance mapping.

Incorrect Answers

A:

This response would target a different source scenario: A switch operator treats the highest bridge ID as the guaranteed STP root. It cannot establish the current acceptance requirement, which is: A region status check shows the intended shared instance mapping. The relevant action is: Align region identity, revision and VLAN mapping as required.

C:

The alternative addresses several VLANs have unexpected root placement under VSTP after port membership changes, not the present root cause. Here the selected correction must reflect mSTP region agreement affects how instances interoperate across links. Test for: A region status check shows the intended shared instance mapping.

D:

This answer would be more suitable when one LAG member fails silently and the service loses capacity even though the logical interface remains active, where the corrective action is to inspect member states, traffic distribution and configured minimum link expectations. The failure here is different: MSTP region agreement affects how instances interoperate across links. Required validation: A region status check shows the intended shared instance mapping.

Question 562

A GRE design includes a virtual tunnel interface but omits routable IPv4 underlay access to the remote endpoint. Which statement identifies the key design assumption that failed?

  1. Root design issue: GRE encapsulation overhead can expose MTU blackholes for larger payloads.
  2. The governing rule is: MPLS forwarding typically uses labels to select the next label-switched hop.
  3. The key distinction is: Tunnel interfaces depend on a working underlay path between endpoints.
  4. Protocol behavior: A tunnel can carry inner packet types over an underlay forwarding only the outer header.

Explanation

Correct Answer

C:

Correct diagnosis: Tunnel interfaces depend on a working underlay path between endpoints. The appropriate action is: Verify reachability between tunnel source and destination addresses. The follow-up evidence required is: The remote tunnel endpoint is reachable through the intended underlay.

Incorrect Answers

A:

GRE encapsulation overhead can expose MTU blackholes for larger payloads describes a neighboring protocol concern. In this case the controlling fact is tunnel interfaces depend on a working underlay path between endpoints. A correct remediation would verify reachability between tunnel source and destination addresses and demonstrate: The remote tunnel endpoint is reachable through the intended underlay.

B:

The proposed principle concerns another network fault: MPLS forwarding typically uses labels to select the next label-switched hop. Here, tunnel interfaces depend on a working underlay path between endpoints. The most direct correction is to verify reachability between tunnel source and destination addresses, confirmed by the remote tunnel endpoint is reachable through the intended underlay.

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

Question 563

A transport route is reachable through an IP interface but the LSP still fails due to incomplete label distribution. Which change best corrects the failure without losing the intended design?

  1. Corrective action: Evaluate routing-policy local preference before later BGP path-selection attributes.
  2. Apply this control: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  3. Remediation: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints.
  4. Recommended change: Differentiate IP underlay reachability from LDP or RSVP control state.

Explanation

Correct Answer

D:

The critical observation is: MPLS forwarding requires coordinated label signaling and forwarding entries. Correct it by taking this action: Differentiate IP underlay reachability from LDP or RSVP control state. Confirm the outcome with: The label table and LSP state match the intended forwarding path.

Incorrect Answers

A:

The alternative addresses two BGP paths have different local preferences and a technician expects the shorter AS path always to win, not the present root cause. Here the selected correction must reflect mPLS forwarding requires coordinated label signaling and forwarding entries. Test for: The label table and LSP state match the intended forwarding path.

B:

This answer would be more suitable when a penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label, where the corrective action is to recognize penultimate-hop popping as an allowed LSP forwarding behavior. The failure here is different: MPLS forwarding requires coordinated label signaling and forwarding entries. Required validation: The label table and LSP state match the intended forwarding path.

C:

This option overlooks the decisive condition. Its supporting principle is a labeled transport next hop must be available to carry the overlay service, while this scenario depends on mPLS forwarding requires coordinated label signaling and forwarding entries. Verify the correction with: The label table and LSP state match the intended forwarding path.

Question 564

A router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view. What is the most defensible network engineering correction?

  1. Next step: Differentiate multiaccess DIS election from point-to-point adjacency behavior.
  2. Corrective action: Rehearse the failure and inspect active next hops and IS-IS route changes.
  3. Apply this control: Review Level 1 and Level 2 routing roles and their intended boundaries.
  4. Remediation: Inspect local preference, export/import inheritance and selected BGP path attributes.

Explanation

Correct Answer

C:

This is the model-intended best choice because iS-IS routing levels determine topology knowledge and area reachability. The targeted correction is to review Level 1 and Level 2 routing roles and their intended boundaries. Validate it by observing that an eligible Level 2 or L1/L2 path provides the approved interarea destination.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. The current case specifically calls for: Review Level 1 and Level 2 routing roles and their intended boundaries. The required observed result is: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

B:

This response would target a different source scenario: A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. It cannot establish the current acceptance requirement, which is: An eligible Level 2 or L1/L2 path provides the approved interarea destination. The relevant action is: Review Level 1 and Level 2 routing roles and their intended boundaries.

D:

The alternative addresses a policy change unexpectedly makes a backup transit provider carry most outbound traffic, not the present root cause. Here the selected correction must reflect iS-IS routing levels determine topology knowledge and area reachability. Test for: An eligible Level 2 or L1/L2 path provides the approved interarea destination.

Question 565

A router sees multiple labels on a packet but an engineer only examines the innermost label when troubleshooting transit transport. What assessment accurately links the fault to its correction?

  1. Fault mechanism: RSVP-TE path choice can account for configured topology constraints and resources. Remediation: Review explicit-path or constraint-based RSVP traffic-engineering intent.
  2. Root issue: Outer and inner labels can have distinct transport and service roles. Correction: Inspect the full MPLS label stack and outgoing label operation.
  3. Cause: Policy evaluation order can short-circuit later intended acceptance. Response: Evaluate policy terms in effective order and test matching routes.
  4. Diagnosis: A healthy transport LSP does not guarantee a correct overlay label mapping. Action: Inspect outer transport and inner service label handling separately.

Explanation

Correct Answer

B:

The case turns on the distinction that outer and inner labels can have distinct transport and service roles. Apply this concrete engineering step: Inspect the full MPLS label stack and outgoing label operation. An acceptable verification outcome is: A capture identifies the label used at each transit stage.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is rSVP-TE path choice can account for configured topology constraints and resources, while this scenario depends on outer and inner labels can have distinct transport and service roles. Verify the correction with: A capture identifies the label used at each transit stage.

C:

The proposed principle concerns another network fault: Policy evaluation order can short-circuit later intended acceptance. Here, outer and inner labels can have distinct transport and service roles. The most direct correction is to inspect the full MPLS label stack and outgoing label operation, confirmed by a capture identifies the label used at each transit stage.

D:

That result would be useful for a different failure, namely: A customer overlay fails across an MPLS core only for one service label. The current case specifically calls for: Inspect the full MPLS label stack and outgoing label operation. The required observed result is: A capture identifies the label used at each transit stage.

Question 566

A provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. Which corrective action and confirmation pair is most appropriate?

  1. Change: Check client definitions, route-reflector session state and export policy. Test: The missing client receives the correct next-hop-resolvable route.
  2. Implement: Distinguish session negotiation from UPDATE message route advertisements. Verify: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.
  3. Control: Distinguish IP RIB entries from label forwarding information and LSP resolution. Accepted result: The transit LSR selects an authorized outgoing label and interface.
  4. Action: Evaluate routing-policy local preference before later BGP path-selection attributes. Evidence: The intended local preference policy selects the approved egress.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: BGP message types have separate roles in session formation and reachability exchange. Remedy: Distinguish session negotiation from UPDATE message route advertisements. Proof: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Incorrect Answers

A:

Check client definitions, route-reflector session state and export policy is a relevant step for the separate scenario in which a route reflector receives a new branch prefix but one iBGP client never learns it. It does not directly fix this case. Instead distinguish session negotiation from UPDATE message route advertisements; verify: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

C:

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 message types have separate roles in session formation and reachability exchange. Required validation: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

D:

This option overlooks the decisive condition. Its supporting principle is bGP best-path selection considers higher-priority decision attributes before AS-path length, while this scenario depends on bGP message types have separate roles in session formation and reachability exchange. Verify the correction with: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.

Question 567

Several routers report intermittent OSPF neighbor resets on a saturated transit circuit. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: OSPF route type and LSA scope depend on where routing information originates.
  2. The governing rule is: Neighbor discovery can succeed even when database exchange parameters prevent completion.
  3. The key distinction is: Protocol timers need reliable packet delivery and should not mask an unstable link.
  4. Protocol behavior: Control-plane route visibility and installed forwarding state are distinct evidence.

Explanation

Correct Answer

C:

The case turns on the distinction that protocol timers need reliable packet delivery and should not mask an unstable link. Apply this concrete engineering step: Compare Hello/Dead event logs with loss and interface errors before tuning timers. An acceptable verification outcome is: A measured link-quality improvement stabilizes OSPF adjacencies.

Incorrect Answers

A:

The proposed principle concerns another network fault: OSPF route type and LSA scope depend on where routing information originates. Here, protocol timers need reliable packet delivery and should not mask an unstable link. The most direct correction is to compare Hello/Dead event logs with loss and interface errors before tuning timers, confirmed by a measured link-quality improvement stabilizes OSPF adjacencies.

B:

That result would be useful for a different failure, namely: An OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange. The current case specifically calls for: Compare Hello/Dead event logs with loss and interface errors before tuning timers. The required observed result is: A measured link-quality improvement stabilizes OSPF adjacencies.

D:

Compare RIB selection with forwarding-table installation and next-hop resolution is a relevant step for the separate scenario in which a route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. It does not directly fix this case. Instead compare Hello/Dead event logs with loss and interface errors before tuning timers; verify: A measured link-quality improvement stabilizes OSPF adjacencies.

Question 568

IPv6-over-IPv4 tunnel endpoints reach each other using IPv4 but IPv6 payloads fail after a firewall update. What is the most defensible network engineering correction?

  1. Corrective action: Apply longest-prefix-match route lookup to the IPv6 destination.
  2. Apply this control: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.
  3. Remediation: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU.
  4. Recommended change: Differentiate multiaccess DIS election from point-to-point adjacency behavior.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Remedy: Verify tunnel protocol allowance, endpoint encapsulation and effective MTU. Proof: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

Incorrect Answers

A:

This answer would be more suitable when an engineer chooses an IPv6 route based on the printed address alone without comparing prefix length, where the corrective action is to apply longest-prefix-match route lookup to the IPv6 destination. The failure here is different: Underlying endpoint reachability does not guarantee permitted encapsulated payloads. Required validation: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

B:

This option overlooks the decisive condition. Its supporting principle is iPv4 operational success does not prove IPv6 forwarding configuration, while this scenario depends on underlying endpoint reachability does not guarantee permitted encapsulated payloads. Verify the correction with: IPv6 test packets traverse the restored tunnel with appropriate MTU handling.

D:

The proposed principle concerns another network fault: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Here, underlying endpoint reachability does not guarantee permitted encapsulated payloads. The most direct correction is to verify tunnel protocol allowance, endpoint encapsulation and effective MTU, confirmed by iPv6 test packets traverse the restored tunnel with appropriate MTU handling.

Question 569

A provider failover exposes an alternate IS-IS path that had never been tested for next-hop resolution. Which technical distinction best describes the observed symptom?

  1. Protocol behavior: A backup path requires functional forwarding, not merely topology presence.
  2. Underlying principle: Changing router identity may require controlled protocol restart or adjacency reestablishment.
  3. Root design issue: Structured protocol-layer evidence separates link health from routing convergence issues.
  4. The governing rule is: IS-IS advertises extensible routing attributes using TLV-encoded fields.

Explanation

Correct Answer

A:

Underlying cause: A backup path requires functional forwarding, not merely topology presence. Corrective action: rehearse the failure and inspect active next hops and IS-IS route changes. Verify the outcome: The backup next hop resolves and carries test traffic after the primary link fails.

Incorrect Answers

B:

Apply a safe approved OSPF process refresh and verify advertised router identity is a relevant step for the separate scenario in which a technician edits a router ID but tests immediately without accounting for established OSPF process state. It does not directly fix this case. Instead rehearse the failure and inspect active next hops and IS-IS route changes; verify: The backup next hop resolves and carries test traffic after the primary link fails.

C:

The alternative addresses an IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence, not the present root cause. Here the selected correction must reflect a backup path requires functional forwarding, not merely topology presence. Test for: The backup next hop resolves and carries test traffic after the primary link fails.

D:

This answer would be more suitable when an operator calls an IS-IS TLV a transport packet and ignores its role in link-state information, where the corrective action is to identify TLVs as structured information within IS-IS protocol data units. The failure here is different: A backup path requires functional forwarding, not merely topology presence. Required validation: The backup next hop resolves and carries test traffic after the primary link fails.

Question 570

An engineer chooses an IPv6 route based on the printed address alone without comparing prefix length. Which next action best resolves this observed routing or switching failure?

  1. Recommended change: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport.
  2. Next step: Distinguish the inner routed payload from outer unicast encapsulation.
  3. Corrective action: Validate IPv6 addressing, neighbor discovery and inet6 routing separately.
  4. Apply this control: Apply longest-prefix-match route lookup to the IPv6 destination.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: IPv6 route selection follows prefix matching and route eligibility, not textual address order. Remedy: Apply longest-prefix-match route lookup to the IPv6 destination. Proof: A destination lookup chooses the intended most specific valid route.

Incorrect Answers

A:

Tunneling carries one protocol over an underlay that may not route that payload natively describes a neighboring protocol concern. In this case the controlling fact is iPv6 route selection follows prefix matching and route eligibility, not textual address order. A correct remediation would apply longest-prefix-match route lookup to the IPv6 destination and demonstrate: A destination lookup chooses the intended most specific valid route.

B:

The proposed principle concerns another network fault: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Here, iPv6 route selection follows prefix matching and route eligibility, not textual address order. The most direct correction is to apply longest-prefix-match route lookup to the IPv6 destination, confirmed by a destination lookup chooses the intended most specific valid route.

C:

That result would be useful for a different failure, namely: A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. The current case specifically calls for: Apply longest-prefix-match route lookup to the IPv6 destination. The required observed result is: A destination lookup chooses the intended most specific valid route.

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