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 41

Question 400

An IPv6 packet exceeds an underlay path MTU and the operator expects intermediate IPv6 routers to fragment it. What should the operations engineer do first to address the stated fault?

  1. Remediation: Apply and verify supported route policy at the intended routing import or export boundary.
  2. Recommended change: Review IPv6 path MTU discovery and endpoint fragmentation requirements.
  3. Next step: Inspect longest-match results and forwarding routes for the specific destination.
  4. Corrective action: Enable and verify the intended IPv6 BGP family and export policy.

Explanation

Correct Answer

B:

Correct diagnosis: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. The appropriate action is: Review IPv6 path MTU discovery and endpoint fragmentation requirements. The follow-up evidence required is: The sender adapts to a validated path MTU and payload delivery succeeds.

Incorrect Answers

A:

This answer would be more suitable when an engineer wants to filter routing information at an IS-IS boundary but applies a policy to the wrong routing context, where the corrective action is to apply and verify supported route policy at the intended routing import or export boundary. The failure here is different: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Required validation: The sender adapts to a validated path MTU and payload delivery succeeds.

C:

More-specific routes can override an otherwise healthy IPv6 fallback describes a neighboring protocol concern. In this case the controlling fact is intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. A correct remediation would review IPv6 path MTU discovery and endpoint fragmentation requirements and demonstrate: The sender adapts to a validated path MTU and payload delivery succeeds.

D:

The proposed principle concerns another network fault: BGP family negotiation and route policy control IPv6 NLRI exchange. Here, intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. The most direct correction is to review IPv6 path MTU discovery and endpoint fragmentation requirements, confirmed by the sender adapts to a validated path MTU and payload delivery succeeds.

Question 401

An operator expects an MPLS label to represent an entire customer IP packet header. What operational check demonstrates that the intended outcome occurred?

  1. The test confirms that a packet trace verifies the intended stack at the penultimate and egress hops.
  2. Expected observation: The observed penultimate and egress labels agree with the supported LSP behavior.
  3. Verification result: A packet decode identifies label fields separately from the carried IP packet.
  4. Closeout evidence: The unauthorized customer receives no leaked prefixes in a route advertisement check.

Explanation

Correct Answer

C:

The critical observation is: MPLS forwarding typically uses labels to select the next label-switched hop. Correct it by taking this action: Distinguish the MPLS shim label stack from the encapsulated payload. Confirm the outcome with: A packet decode identifies label fields separately from the carried IP packet.

Incorrect Answers

A:

This response would target a different source scenario: A penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. It cannot establish the current acceptance requirement, which is: A packet decode identifies label fields separately from the carried IP packet. The relevant action is: Distinguish the MPLS shim label stack from the encapsulated payload.

B:

Verify whether PHP or explicit-null behavior is configured and intended is a relevant step for the separate scenario in which an MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. It does not directly fix this case. Instead distinguish the MPLS shim label stack from the encapsulated payload; verify: A packet decode identifies label fields separately from the carried IP packet.

D:

This answer would be more suitable when one customer’s new prefixes are advertised to a second unrelated customer via a shared export group, where the corrective action is to split export policy by authorized customer scope and verify negative advertisements. The failure here is different: MPLS forwarding typically uses labels to select the next label-switched hop. Required validation: A packet decode identifies label fields separately from the carried IP packet.

Question 402

An operator plans provider bridging but assumes the customer's C-tag is removed from every frame. What observable result most directly verifies the intended configuration?

  1. Acceptance check: A capture shows the expected outer service tag between provider edges.
  2. The test confirms that a tagged test frame reaches the approved remote port in the same domain.
  3. Expected observation: An ingress-to-egress capture confirms the intended stacked tagging.
  4. Verification result: The fault is visible and surviving members carry traffic within the approved limits.

Explanation

Correct Answer

C:

Correct diagnosis: Provider bridging can carry customer VLAN tags inside a provider service tag. The appropriate action is: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design. The follow-up evidence required is: An ingress-to-egress capture confirms the intended stacked tagging.

Incorrect Answers

A:

Provider bridging service tags must be applied and removed at the designed boundaries describes a neighboring protocol concern. In this case the controlling fact is provider bridging can carry customer VLAN tags inside a provider service tag. A correct remediation would clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design and demonstrate: An ingress-to-egress capture confirms the intended stacked tagging.

B:

The proposed principle concerns another network fault: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching. Here, provider bridging can carry customer VLAN tags inside a provider service tag. The most direct correction is to clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design, confirmed by an ingress-to-egress capture confirms the intended stacked tagging.

D:

This response would target a different source scenario: One LAG member fails silently and the service loses capacity even though the logical interface remains active. It cannot establish the current acceptance requirement, which is: An ingress-to-egress capture confirms the intended stacked tagging. The relevant action is: Clarify C-tag preservation and S-tag encapsulation in a Q-in-Q design.

Question 403

An EBGP peer drops repeatedly after a firewall change despite clean interface counters. What implementation step and validation result should be selected?

  1. Change: Review EBGP multihop transport reachability and session parameters. Test: The TCP session establishes across the intended transport path.
  2. Implement: Inspect TCP reachability, permitted port 179, and authentication on the transport path. Verify: An authenticated TCP session stays Established after the rule correction.
  3. Control: Inspect the full MPLS label stack and outgoing label operation. Accepted result: A capture identifies the label used at each transit stage.
  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:

Underlying cause: BGP sessions require sustained TCP connectivity independent of physical interface health. Corrective action: inspect TCP reachability, permitted port 179, and authentication on the transport path. Verify the outcome: An authenticated TCP session stays Established after the rule correction.

Incorrect Answers

A:

The alternative addresses a multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop, not the present root cause. Here the selected correction must reflect bGP sessions require sustained TCP connectivity independent of physical interface health. Test for: An authenticated TCP session stays Established after the rule correction.

C:

This option overlooks the decisive condition. Its supporting principle is outer and inner labels can have distinct transport and service roles, while this scenario depends on bGP sessions require sustained TCP connectivity independent of physical interface health. Verify the correction with: An authenticated TCP session stays Established after the rule correction.

D:

MED is not guaranteed to override local policy or earlier attributes describes a neighboring protocol concern. In this case the controlling fact is bGP sessions require sustained TCP connectivity independent of physical interface health. A correct remediation would inspect TCP reachability, permitted port 179, and authentication on the transport path and demonstrate: An authenticated TCP session stays Established after the rule correction.

Question 404

A broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately. What should the operations engineer do first to address the stated fault?

  1. Apply this control: Verify compatible network and Hello parameters including mask where applicable.
  2. Remediation: Measure end-to-end route choices and review configured interface metrics.
  3. Recommended change: Review the passive-interface configuration and required active neighbor links.
  4. Next step: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.

Explanation

Correct Answer

D:

Correct diagnosis: OSPF neighbor-state interpretation depends on multiaccess election roles. The appropriate action is: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. The follow-up evidence required is: The segment passes route and database tests with the expected neighbor states.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A router sends OSPF Hello packets but remains stuck because the subnet mask differs across neighbors on a broadcast link. The current case specifically calls for: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment. The required observed result is: The segment passes route and database tests with the expected neighbor states.

B:

This response would target a different source scenario: A transit operator changes IS-IS metrics on one interface and later discovers a traffic-engineering imbalance. It cannot establish the current acceptance requirement, which is: The segment passes route and database tests with the expected neighbor states. The relevant action is: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.

C:

Review the passive-interface configuration and required active neighbor links is a relevant step for the separate scenario in which an OSPF interface is accidentally set passive on a provider edge and its neighbor never appears. It does not directly fix this case. Instead check DR and BDR roles and expected 2-Way peers before changing a healthy segment; verify: The segment passes route and database tests with the expected neighbor states.

Question 405

A router sees multiple labels on a packet but an engineer only examines the innermost label when troubleshooting transit transport. Which combined repair and acceptance criterion is strongest?

  1. Action: Verify whether PHP or explicit-null behavior is configured and intended. Evidence: The observed penultimate and egress labels agree with the supported LSP behavior.
  2. Repair: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes. Check: The summary is advertised only under the approved component-route conditions.
  3. Change: Review LDP dependence on reachability and routing of the transport endpoints. Test: The restored IGP path permits LDP forwarding to the remote endpoint.
  4. Implement: Inspect the full MPLS label stack and outgoing label operation. Verify: A capture identifies the label used at each transit stage.

Explanation

Correct Answer

D:

The selected response implements the principle that outer and inner labels can have distinct transport and service roles. The engineer should inspect the full MPLS label stack and outgoing label operation. Successful confirmation means: A capture identifies the label used at each transit stage.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is label stack changes can be legitimate parts of LSP forwarding design, 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.

B:

Aggregation can hide individual component failures if advertisement policy is not controlled describes a neighboring protocol concern. In this case the controlling fact is outer and inner labels can have distinct transport and service roles. A correct remediation would inspect the full MPLS label stack and outgoing label operation and demonstrate: A capture identifies the label used at each transit stage.

C:

The proposed principle concerns another network fault: LDP label bindings are useful only with a functional path to the FEC next hop. 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.

Question 406

A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. What implementation step and validation result should be selected?

  1. Control: Recognize IS-IS as a link-layer routing protocol with its own PDUs. Accepted result: A link-level packet trace observes the relevant IS-IS PDUs.
  2. Action: Confirm the configured local and peer AS values with the authoritative design. Evidence: The session reaches Established only with the documented correct peer AS.
  3. Repair: Collect protocol adjacency, LSP and routing-table outputs for the affected route. Check: The report explains the fault from interface through neighbor to selected route.
  4. Change: Place the correct L1/L2 boundary and evaluate flooding scope. Test: The planned area topology reaches distant prefixes through eligible Level 2 routing.

Explanation

Correct Answer

D:

This is the model-intended best choice because iS-IS route dissemination follows hierarchical level boundaries. The targeted correction is to place the correct L1/L2 boundary and evaluate flooding scope. Validate it by observing that the planned area topology reaches distant prefixes through eligible Level 2 routing.

Incorrect Answers

A:

Recognize IS-IS as a link-layer routing protocol with its own PDUs is a relevant step for the separate scenario in which a technician tries to diagnose an IS-IS area failure only by inspecting IP multicast Hellos. It does not directly fix this case. Instead place the correct L1/L2 boundary and evaluate flooding scope; verify: The planned area topology reaches distant prefixes through eligible Level 2 routing.

B:

The alternative addresses a remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation, not the present root cause. Here the selected correction must reflect iS-IS route dissemination follows hierarchical level boundaries. Test for: The planned area topology reaches distant prefixes through eligible Level 2 routing.

C:

This answer would be more suitable when an IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence, where the corrective action is to collect protocol adjacency, LSP and routing-table outputs for the affected route. The failure here is different: IS-IS route dissemination follows hierarchical level boundaries. Required validation: The planned area topology reaches distant prefixes through eligible Level 2 routing.

Question 407

A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. What observable result most directly verifies the intended configuration?

  1. Acceptance check: A topology test leaves one redundant path nonforwarding and traffic remains reachable.
  2. The test confirms that a capture shows the expected outer service tag between provider edges.
  3. Expected observation: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.
  4. Verification result: Each VLAN maps to its intended instance and designated root.

Explanation

Correct Answer

D:

Underlying cause: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters. Corrective action: evaluate MSTP instances and explicit VLAN-to-instance mapping. Verify the outcome: Each VLAN maps to its intended instance and designated root.

Incorrect Answers

A:

The proposed principle concerns another network fault: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Here, mSTP can group VLANs into multiple spanning-tree instances under shared region parameters. The most direct correction is to evaluate MSTP instances and explicit VLAN-to-instance mapping, confirmed by each VLAN maps to its intended instance and designated root.

B:

That result would be useful for a different failure, namely: Tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing. The current case specifically calls for: Evaluate MSTP instances and explicit VLAN-to-instance mapping. The required observed result is: Each VLAN maps to its intended instance and designated root.

C:

This response would target a different source scenario: A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. It cannot establish the current acceptance requirement, which is: Each VLAN maps to its intended instance and designated root. The relevant action is: Evaluate MSTP instances and explicit VLAN-to-instance mapping.

Question 408

A provider tunnels traffic for customer isolation but makes no decision about routing-policy exposure at the tunnel edge. Which evidence would justify closing this troubleshooting case?

  1. Closeout evidence: A controlled large-payload test succeeds after MTU or MSS adjustment.
  2. Acceptance check: Underlay traces show the outer endpoint traffic without transit processing of inner routes.
  3. The test confirms that only authorized customer prefixes enter or leave the decapsulated routing context.
  4. Expected observation: The intended IPv6 neighbor and destination routes appear and traffic succeeds.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Encapsulation does not replace explicit customer route filtering and access policy. Remedy: Treat tunnel decapsulation as a routing and security boundary. Proof: Only authorized customer prefixes enter or leave the decapsulated routing context.

Incorrect Answers

A:

This answer would be more suitable when small probes pass through GRE but large customer packets are intermittently dropped, where the corrective action is to test effective MTU and path MTU discovery across the encapsulated route. The failure here is different: Encapsulation does not replace explicit customer route filtering and access policy. Required validation: Only authorized customer prefixes enter or leave the decapsulated routing context.

B:

This option overlooks the decisive condition. Its supporting principle is a tunnel can carry inner packet types over an underlay forwarding only the outer header, while this scenario depends on encapsulation does not replace explicit customer route filtering and access policy. Verify the correction with: Only authorized customer prefixes enter or leave the decapsulated routing context.

D:

The proposed principle concerns another network fault: IPv4 operational success does not prove IPv6 forwarding configuration. Here, encapsulation does not replace explicit customer route filtering and access policy. The most direct correction is to treat tunnel decapsulation as a routing and security boundary, confirmed by only authorized customer prefixes enter or leave the decapsulated routing context.

Question 409

A service provider tunnels IPv6 over an IPv4 core but expects native IPv6 forwarding at every transit hop. Which protocol behavior most directly determines the correct diagnosis?

  1. Root design issue: IPv4 operational success does not prove IPv6 forwarding configuration.
  2. The governing rule is: Tunneling carries one protocol over an underlay that may not route that payload natively.
  3. The key distinction is: BGP family negotiation and route policy control IPv6 NLRI exchange.
  4. Protocol behavior: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links.

Explanation

Correct Answer

B:

The selected response implements the principle that tunneling carries one protocol over an underlay that may not route that payload natively. The engineer should model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport. Successful confirmation means: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

Incorrect Answers

A:

This response would target a different source scenario: A new Junos edge router can ping IPv4 customers but cannot route IPv6 traffic to the same site. It cannot establish the current acceptance requirement, which is: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint. The relevant action is: Model endpoint encapsulation and decapsulation for IPv6-over-IPv4 transport.

C:

The alternative addresses a BGP peer carries IPv4 prefixes but the team assumes IPv6 prefixes are automatically shared, not the present root cause. Here the selected correction must reflect tunneling carries one protocol over an underlay that may not route that payload natively. Test for: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

D:

This answer would be more suitable when an engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link, where the corrective action is to differentiate multiaccess DIS election from point-to-point adjacency behavior. The failure here is different: Tunneling carries one protocol over an underlay that may not route that payload natively. Required validation: A tunnel packet is carried over IPv4 and decapsulated to IPv6 at the endpoint.

Question 410

A transit operator changes IS-IS metrics on one interface and later discovers a traffic-engineering imbalance. Which evidence would justify closing this troubleshooting case?

  1. Expected observation: The TCP session establishes across the intended transport path.
  2. Verification result: The report explains the fault from interface through neighbor to selected route.
  3. Closeout evidence: Traffic and route lookup follow the documented optimized path.
  4. Acceptance check: The planned area topology reaches distant prefixes through eligible Level 2 routing.

Explanation

Correct Answer

C:

Correct diagnosis: IS-IS shortest-path output depends on effective metrics across the route. The appropriate action is: Measure end-to-end route choices and review configured interface metrics. The follow-up evidence required is: Traffic and route lookup follow the documented optimized path.

Incorrect Answers

A:

EBGP speakers separated by intermediate devices require deliberate transport reachability and hop policy 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.

B:

The proposed principle concerns another network fault: Structured protocol-layer evidence separates link health from routing convergence issues. Here, iS-IS shortest-path output depends on effective metrics across the route. The most direct correction is to measure end-to-end route choices and review configured interface metrics, confirmed by traffic and route lookup follow the documented optimized path.

D:

This response would target a different source scenario: A provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding. It cannot establish the current acceptance requirement, which is: Traffic and route lookup follow the documented optimized path. The relevant action is: Measure end-to-end route choices and review configured interface metrics.

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