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 70

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.

Question 691

After a trunk change a MAC address is visible but only one of two VLANs can traverse the uplink. What action-and-test pairing directly resolves the case?

  1. Action: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. Evidence: Separate tagged tests pass in both permitted VLANs.
  2. Repair: Apply suitable BPDU protection according to edge-port policy. Check: A controlled BPDU causes the expected protected-port response.
  3. Change: Compare candidate and committed configurations and confirm actual bridge membership. Test: The active configuration and forwarding table reflect the approved VLAN change.
  4. Implement: Investigate MAC movement, loops and correct bridge-domain membership. Verify: The MAC table stabilizes on the authorized port after loop or miswire correction.

Explanation

Correct Answer

A:

The case turns on the distinction that mAC table visibility alone does not prove trunk authorization for every VLAN. Apply this concrete engineering step: Inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning. An acceptable verification outcome is: Separate tagged tests pass in both permitted VLANs.

Incorrect Answers

B:

This answer would be more suitable when an edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch, where the corrective action is to apply suitable BPDU protection according to edge-port policy. The failure here is different: MAC table visibility alone does not prove trunk authorization for every VLAN. Required validation: Separate tagged tests pass in both permitted VLANs.

C:

This option overlooks the decisive condition. Its supporting principle is junos candidate configuration changes are not active until committed, while this scenario depends on mAC table visibility alone does not prove trunk authorization for every VLAN. Verify the correction with: Separate tagged tests pass in both permitted VLANs.

D:

MAC learning reflects observed source location and may churn during loops or mobility describes a neighboring protocol concern. In this case the controlling fact is mAC table visibility alone does not prove trunk authorization for every VLAN. A correct remediation would inspect VLAN membership and tagging on both ends and verify per-VLAN MAC learning and demonstrate: Separate tagged tests pass in both permitted VLANs.

Question 692

A route shows as active but the interface destination still drops traffic after an interface move. Which cause-and-remedy pairing reflects the observed problem?

  1. Root issue: A configured static route need not become usable forwarding state when its next hop cannot resolve. Correction: Verify recursive next-hop reachability before relying on the static route.
  2. Cause: Forwarding-table and interface evidence localize faults beyond RIB reachability. Response: Compare installed forwarding entries with interface operational status and adjacency resolution.
  3. Diagnosis: Neighbor state must be traced through transport before modifying route policy. Action: Verify IP reachability, routing instance context, TCP transport and session authentication.
  4. Explanation: Imported routes must be validated in the destination lookup context. Repair: Check import destinations, next-hop resolution and effective routes in every receiving table.

Explanation

Correct Answer

B:

Because forwarding-table and interface evidence localize faults beyond RIB reachability, the best response is to compare installed forwarding entries with interface operational status and adjacency resolution. A reviewer can close the technical case only after confirming that a test packet follows the expected active forwarding next hop and interface.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. The current case specifically calls for: Compare installed forwarding entries with interface operational status and adjacency resolution. The required observed result is: A test packet follows the expected active forwarding next hop and interface.

C:

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 compare installed forwarding entries with interface operational status and adjacency resolution; verify: A test packet follows the expected active forwarding next hop and interface.

D:

The alternative addresses a RIB group leak forwards a VPN service toward the wrong next hop after a route update, not the present root cause. Here the selected correction must reflect forwarding-table and interface evidence localize faults beyond RIB reachability. Test for: A test packet follows the expected active forwarding next hop and interface.

Question 693

An RSVP-signaled LSP enters a failed state after a link bandwidth change. What diagnosis and engineering response are most appropriate?

  1. Fault mechanism: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Remediation: Review reservation constraints and available resources rather than resetting all label sessions.
  2. Root issue: Routing policy acceptance must reflect explicitly permitted destinations. Correction: Add a precise prefix and instance match, then inspect effective imports.
  3. Cause: Outer and inner labels can have distinct transport and service roles. Response: Inspect the full MPLS label stack and outgoing label operation.
  4. 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.

Explanation

Correct Answer

A:

The critical observation is: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Correct it by taking this action: Review reservation constraints and available resources rather than resetting all label sessions. Confirm the outcome with: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

Incorrect Answers

B:

Routing policy acceptance must reflect explicitly permitted destinations describes a neighboring protocol concern. In this case the controlling fact is rSVP LSP setup can fail resource or path constraints even with valid IP reachability. A correct remediation would review reservation constraints and available resources rather than resetting all label sessions and demonstrate: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

C:

The proposed principle concerns another network fault: Outer and inner labels can have distinct transport and service roles. Here, rSVP LSP setup can fail resource or path constraints even with valid IP reachability. The most direct correction is to review reservation constraints and available resources rather than resetting all label sessions, confirmed by a compatible bandwidth or path choice allows the target RSVP LSP to establish.

D:

That result would be useful for a different failure, namely: A maintenance change affects MPLS forwarding on just one core hop and the team only checks RSVP session status at ingress. The current case specifically calls for: Review reservation constraints and available resources rather than resetting all label sessions. The required observed result is: A compatible bandwidth or path choice allows the target RSVP LSP to establish.

Question 694

A multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. What action-and-test pairing directly resolves the case?

  1. Change: Check SR label advertisements, segment configuration and installed MPLS forwarding. Test: The intended SR transport path forwards without unintended dependence on the retired LDP path.
  2. Implement: Review EBGP multihop transport reachability and session parameters. Verify: The TCP session establishes across the intended transport path.
  3. Control: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. Accepted result: A controlled route lookup confirms the neighbor's actual selected entry path.
  4. Action: Compare MED use with actual prior BGP decision attributes and neighbor policy. Evidence: A captured received-path comparison explains which attribute selected the route.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Remedy: Review EBGP multihop transport reachability and session parameters. Proof: The TCP session establishes across the intended transport path.

Incorrect Answers

A:

Check SR label advertisements, segment configuration and installed MPLS forwarding is a relevant step for the separate scenario in which a provider migrates one path from LDP to SR-MPLS but does not verify the segment-routing forwarding state. It does not directly fix this case. Instead review EBGP multihop transport reachability and session parameters; verify: The TCP session establishes across the intended transport path.

C:

This answer would be more suitable when an inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies, where the corrective action is to distinguish an advertised inbound hint from neighboring-AS route policy decisions. The failure here is different: EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Required validation: The TCP session establishes across the intended transport path.

D:

This option overlooks the decisive condition. Its supporting principle is mED is not guaranteed to override local policy or earlier attributes, while this scenario depends on eBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy. Verify the correction with: The TCP session establishes across the intended transport path.

Question 695

An IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship. Which post-change observation most strongly confirms the correction?

  1. Verification result: Each direction's active route matches the documented costs and design.
  2. Closeout evidence: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.
  3. Acceptance check: A link-level packet trace observes the relevant IS-IS PDUs.
  4. The test confirms that the corrected link reaches stable Full adjacency and exchanges the intended routes.

Explanation

Correct Answer

B:

The critical observation is: IS-IS Level 1 adjacency formation depends on common area context. Correct it by taking this action: Verify compatible area membership or use the designed Level 2 boundary. Confirm the outcome with: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Incorrect Answers

A:

The proposed principle concerns another network fault: Common topology information can still produce direction-dependent shortest paths. Here, iS-IS Level 1 adjacency formation depends on common area context. The most direct correction is to verify compatible area membership or use the designed Level 2 boundary, confirmed by the intended Level 1 or Level 2 adjacency forms with the expected topology scope.

C:

This response would target a different source scenario: A technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. It cannot establish the current acceptance requirement, which is: The intended Level 1 or Level 2 adjacency forms with the expected topology scope. The relevant action is: Verify compatible area membership or use the designed Level 2 boundary.

D:

Compare area, interface mode, timers, authentication and physical status on both endpoints is a relevant step for the separate scenario in which a new OSPF uplink remains down at the adjacency stage after a router replacement. It does not directly fix this case. Instead verify compatible area membership or use the designed Level 2 boundary; verify: The intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Question 696

Two routers exchange IS-IS Hellos but one rejects the neighbor during area validation. Which technical distinction best describes the observed symptom?

  1. Underlying principle: An operational interface is not evidence of matching IS-IS protocol configuration.
  2. Root design issue: IS-IS advertises extensible routing attributes using TLV-encoded fields.
  3. The governing rule is: OSPF route type and LSA scope depend on where routing information originates.
  4. The key distinction is: Area mismatch can affect Level 1 adjacency even when packets are received.

Explanation

Correct Answer

D:

Because area mismatch can affect Level 1 adjacency even when packets are received, the best response is to compare NET area addresses and intended L1 or L2 adjacency mode. A reviewer can close the technical case only after confirming that a protocol check shows the authorized level and matching adjacency.

Incorrect Answers

A:

This answer would be more suitable when a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up, where the corrective action is to inspect IS-IS interface enablement, levels, area identifiers and link type. The failure here is different: Area mismatch can affect Level 1 adjacency even when packets are received. Required validation: A protocol check shows the authorized level and matching adjacency.

B:

This option overlooks the decisive condition. Its supporting principle is iS-IS advertises extensible routing attributes using TLV-encoded fields, while this scenario depends on area mismatch can affect Level 1 adjacency even when packets are received. Verify the correction with: A protocol check shows the authorized level and matching adjacency.

C:

OSPF route type and LSA scope depend on where routing information originates describes a neighboring protocol concern. In this case the controlling fact is area mismatch can affect Level 1 adjacency even when packets are received. A correct remediation would compare NET area addresses and intended L1 or L2 adjacency mode and demonstrate: A protocol check shows the authorized level and matching adjacency.

Question 697

An aggregated customer advertisement persists while all contributing specifics have withdrawn. Which evidence would justify closing this troubleshooting case?

  1. The test confirms that the tenant-specific lookup resolves and the same source-based test reaches its destination.
  2. Expected observation: The rejected address remains excluded or a documented narrowly scoped exception is applied.
  3. Verification result: A loss-of-last-contributor test causes the intended summary behavior.
  4. Closeout evidence: An authenticated TCP session stays Established after the rule correction.

Explanation

Correct Answer

C:

The critical observation is: Summary advertisements require validation against their underlying active route policy. Correct it by taking this action: Audit aggregate or generated-route contributors and policy conditions. Confirm the outcome with: A loss-of-last-contributor test causes the intended summary behavior.

Incorrect Answers

A:

This response would target a different source scenario: A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. It cannot establish the current acceptance requirement, which is: A loss-of-last-contributor test causes the intended summary behavior. The relevant action is: Audit aggregate or generated-route contributors and policy conditions.

B:

Review martian-address treatment and justify any carefully scoped exception is a relevant step for the separate scenario in which an operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. It does not directly fix this case. Instead audit aggregate or generated-route contributors and policy conditions; verify: A loss-of-last-contributor test causes the intended summary behavior.

D:

This answer would be more suitable when an EBGP peer drops repeatedly after a firewall change despite clean interface counters, where the corrective action is to inspect TCP reachability, permitted port 179, and authentication on the transport path. The failure here is different: Summary advertisements require validation against their underlying active route policy. Required validation: A loss-of-last-contributor test causes the intended summary behavior.

Question 698

A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. Which corrective action and confirmation pair is most appropriate?

  1. Implement: Split export policy by authorized customer scope and verify negative advertisements. Verify: The unauthorized customer receives no leaked prefixes in a route advertisement check.
  2. Control: Restore the required transport route and inspect label-signaling and next-hop state. Accepted result: The transport endpoint again resolves and a labeled probe succeeds.
  3. Action: Review reservation constraints and available resources rather than resetting all label sessions. Evidence: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  4. Repair: Explain local label significance and neighbor label binding. Check: A path test records locally valid incoming and outgoing label mappings.

Explanation

Correct Answer

B:

This is the model-intended best choice because mPLS relies on selected underlay transport reachability and policy eligibility. The targeted correction is to restore the required transport route and inspect label-signaling and next-hop state. Validate it by observing that the transport endpoint again resolves and a labeled probe succeeds.

Incorrect Answers

A:

BGP group-level export policies must preserve customer routing isolation describes a neighboring protocol concern. In this case the controlling fact is mPLS relies on selected underlay transport reachability and policy eligibility. A correct remediation would restore the required transport route and inspect label-signaling and next-hop state and demonstrate: The transport endpoint again resolves and a labeled probe succeeds.

C:

That result would be useful for a different failure, namely: An RSVP-signaled LSP enters a failed state after a link bandwidth change. The current case specifically calls for: Restore the required transport route and inspect label-signaling and next-hop state. The required observed result is: The transport endpoint again resolves and a labeled probe succeeds.

D:

This response would target a different source scenario: An operator assumes MPLS labels are globally unique across the provider network. It cannot establish the current acceptance requirement, which is: The transport endpoint again resolves and a labeled probe succeeds. The relevant action is: Restore the required transport route and inspect label-signaling and next-hop state.

Question 699

A transit operator changes IS-IS metrics on one interface and later discovers a traffic-engineering imbalance. Which next action best resolves this observed routing or switching failure?

  1. Remediation: Compare area, interface mode, timers, authentication and physical status on both endpoints.
  2. Recommended change: Verify compatible area membership or use the designed Level 2 boundary.
  3. Next step: Measure end-to-end route choices and review configured interface metrics.
  4. Corrective action: Compare NET area addresses and intended L1 or L2 adjacency mode.

Explanation

Correct Answer

C:

The selected response implements the principle that iS-IS shortest-path output depends on effective metrics across the route. The engineer should measure end-to-end route choices and review configured interface metrics. Successful confirmation means: Traffic and route lookup follow the documented optimized path.

Incorrect Answers

A:

The alternative addresses a new OSPF uplink remains down at the adjacency stage after a router replacement, not the present root cause. Here the selected correction must reflect iS-IS shortest-path output depends on effective metrics across the route. Test for: Traffic and route lookup follow the documented optimized path.

B:

This answer would be more suitable when an IS-IS adjacency between two provider routers fails because their NET addresses encode incompatible area identifiers for a Level 1 relationship, where the corrective action is to verify compatible area membership or use the designed Level 2 boundary. The failure here is different: IS-IS shortest-path output depends on effective metrics across the route. Required validation: Traffic and route lookup follow the documented optimized path.

D:

Area mismatch can affect Level 1 adjacency even when packets are received describes a neighboring protocol concern. In this case the controlling fact is iS-IS shortest-path output depends on effective metrics across the route. A correct remediation would measure end-to-end route choices and review configured interface metrics and demonstrate: Traffic and route lookup follow the documented optimized path.

Question 700

A provider PE can ping a customer in the master instance but probes in the tenant routing instance fail. What observable result most directly verifies the intended configuration?

  1. Verification result: The internal peer has a valid route to the BGP next hop and installs the prefix.
  2. Closeout evidence: A route lookup shows an active reachable next hop and traffic reaches the customer.
  3. Acceptance check: The tenant-specific lookup resolves and the same source-based test reaches its destination.
  4. The test confirms that a test packet follows the expected active forwarding next hop and interface.

Explanation

Correct Answer

C:

This is the model-intended best choice because instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. The targeted correction is to run route and connectivity checks in the explicitly intended routing instance. Validate it by observing that the tenant-specific lookup resolves and the same source-based test reaches its destination.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. The current case specifically calls for: Run route and connectivity checks in the explicitly intended routing instance. The required observed result is: The tenant-specific lookup resolves and the same source-based test reaches its destination.

B:

This response would target a different source scenario: A provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route. It cannot establish the current acceptance requirement, which is: The tenant-specific lookup resolves and the same source-based test reaches its destination. The relevant action is: Run route and connectivity checks in the explicitly intended routing instance.

D:

The alternative addresses a route shows as active but the interface destination still drops traffic after an interface move, not the present root cause. Here the selected correction must reflect instance-aware troubleshooting prevents a successful master-table probe from masking tenant isolation issues. Test for: The tenant-specific lookup resolves and the same source-based test reaches its destination.

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