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 56

Question 550

An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. Which change best corrects the failure without losing the intended design?

  1. Recommended change: Inspect IS-IS interface enablement, levels, area identifiers and link type.
  2. Next step: Review Level 1 and Level 2 routing roles and their intended boundaries.
  3. Corrective action: Check client definitions, route-reflector session state and export policy.
  4. Apply this control: Collect protocol adjacency, LSP and routing-table outputs for the affected route.

Explanation

Correct Answer

D:

This is the model-intended best choice because structured protocol-layer evidence separates link health from routing convergence issues. The targeted correction is to collect protocol adjacency, LSP and routing-table outputs for the affected route. Validate it by observing that the report explains the fault from interface through neighbor to selected route.

Incorrect Answers

A:

Inspect IS-IS interface enablement, levels, area identifiers and link type is a relevant step for the separate scenario in which a Junos router shows no IS-IS adjacency after a circuit migration though the interface is physically up. It does not directly fix this case. Instead collect protocol adjacency, LSP and routing-table outputs for the affected route; verify: The report explains the fault from interface through neighbor to selected route.

B:

The alternative addresses a router learns a local IS-IS topology but cannot infer reachability in a remote area from its Level 1-only view, not the present root cause. Here the selected correction must reflect structured protocol-layer evidence separates link health from routing convergence issues. Test for: The report explains the fault from interface through neighbor to selected route.

C:

This answer would be more suitable when a route reflector receives a new branch prefix but one iBGP client never learns it, where the corrective action is to check client definitions, route-reflector session state and export policy. The failure here is different: Structured protocol-layer evidence separates link health from routing convergence issues. Required validation: The report explains the fault from interface through neighbor to selected route.

Question 551

A provider's LDP neighbors disappear after an IGP outage while physical links remain up. Which change best corrects the failure without losing the intended design?

  1. Remediation: Narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes.
  2. Recommended change: Check transport reachability, LDP session state and the relevant IGP routes.
  3. Next step: Verify whether PHP or explicit-null behavior is configured and intended.
  4. Corrective action: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.

Explanation

Correct Answer

B:

The critical observation is: LDP signaling depends on the routing and transport state of its endpoints. Correct it by taking this action: Check transport reachability, LDP session state and the relevant IGP routes. Confirm the outcome with: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

Incorrect Answers

A:

The proposed principle concerns another network fault: Filter-based routing policy requires explicit match conditions and a safe default behavior. Here, lDP signaling depends on the routing and transport state of its endpoints. The most direct correction is to check transport reachability, LDP session state and the relevant IGP routes, confirmed by lDP sessions recover and labeled FEC bindings reappear after underlay repair.

C:

This response would target a different source scenario: An MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. It cannot establish the current acceptance requirement, which is: LDP sessions recover and labeled FEC bindings reappear after underlay repair. The relevant action is: Check transport reachability, LDP session state and the relevant IGP routes.

D:

Recognize penultimate-hop popping as an allowed LSP forwarding behavior is a relevant step for the separate scenario in which a penultimate router pops a transport label and the egress receives native IP even though the engineer expected a visible final outer label. It does not directly fix this case. Instead check transport reachability, LDP session state and the relevant IGP routes; verify: LDP sessions recover and labeled FEC bindings reappear after underlay repair.

Question 552

A GRE tunnel interface exists but its operational state is unreliable because the source interface was changed. What implementation step and validation result should be selected?

  1. Repair: Treat tunnel decapsulation as a routing and security boundary. Check: Only authorized customer prefixes enter or leave the decapsulated routing context.
  2. Change: Inspect Junos MPLS-related next-hop resolution and available LSP endpoints. Test: The remote PE service route resolves over the designated LSP.
  3. Implement: Test effective MTU and path MTU discovery across the encapsulated route. Verify: A controlled large-payload test succeeds after MTU or MSS adjustment.
  4. Control: Verify configured tunnel source and destination and their active underlay routing. Accepted result: The tunnel endpoints pass test traffic after source correction.

Explanation

Correct Answer

D:

Because tunnel endpoint parameters must correspond to actual reachable interfaces, the best response is to verify configured tunnel source and destination and their active underlay routing. A reviewer can close the technical case only after confirming that the tunnel endpoints pass test traffic after source correction.

Incorrect Answers

A:

This answer would be more suitable when a provider tunnels traffic for customer isolation but makes no decision about routing-policy exposure at the tunnel edge, where the corrective action is to treat tunnel decapsulation as a routing and security boundary. The failure here is different: Tunnel endpoint parameters must correspond to actual reachable interfaces. Required validation: The tunnel endpoints pass test traffic after source correction.

B:

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 tunnel endpoint parameters must correspond to actual reachable interfaces. Verify the correction with: The tunnel endpoints pass test traffic after source correction.

C:

GRE encapsulation overhead can expose MTU blackholes for larger payloads describes a neighboring protocol concern. In this case the controlling fact is tunnel endpoint parameters must correspond to actual reachable interfaces. A correct remediation would verify configured tunnel source and destination and their active underlay routing and demonstrate: The tunnel endpoints pass test traffic after source correction.

Question 553

A MAC table is empty after a restart and an operator manually inserts dozens of addresses before sending test traffic. Which underlying Junos networking principle explains the failure?

  1. Underlying principle: A trunk carries only its configured authorized VLANs.
  2. Root design issue: Dynamic MAC tables are populated by observed frames and need not be prefilled.
  3. The governing rule is: Provider bridging service tags must be applied and removed at the designed boundaries.
  4. The key distinction is: GRES preserves forwarding and kernel interface state but does not by itself retain the routing control plane.

Explanation

Correct Answer

B:

The selected response implements the principle that dynamic MAC tables are populated by observed frames and need not be prefilled. The engineer should generate controlled frames and observe normal learning on the correct bridge domain. Successful confirmation means: A source MAC appears on the expected port after a test frame.

Incorrect Answers

A:

This response would target a different source scenario: A trunk permits VLAN 110 but excludes VLAN 120 while users on VLAN 120 report isolation from the remote switch. It cannot establish the current acceptance requirement, which is: A source MAC appears on the expected port after a test frame. The relevant action is: Generate controlled frames and observe normal learning on the correct bridge domain.

C:

The alternative addresses tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing, not the present root cause. Here the selected correction must reflect dynamic MAC tables are populated by observed frames and need not be prefilled. Test for: A source MAC appears on the expected port after a test frame.

D:

This answer would be more suitable when a dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature, where the corrective action is to differentiate forwarding continuity under GRES from routing-protocol state preservation. The failure here is different: Dynamic MAC tables are populated by observed frames and need not be prefilled. Required validation: A source MAC appears on the expected port after a test frame.

Question 554

An MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition. Which protocol behavior most directly determines the correct diagnosis?

  1. Protocol behavior: A healthy transport LSP does not guarantee a correct overlay label mapping.
  2. Underlying principle: A configured static route need not become usable forwarding state when its next hop cannot resolve.
  3. Root design issue: Outer and inner labels can have distinct transport and service roles.
  4. The governing rule is: Incorrect label removal can expose payload handling that the egress does not expect.

Explanation

Correct Answer

D:

This option addresses the stated case rather than another networking issue. Principle: Incorrect label removal can expose payload handling that the egress does not expect. Remedy: Verify the label action and egress handling for the intended service stack. Proof: A traced packet arrives at egress with the correct remaining stack or payload.

Incorrect Answers

A:

A healthy transport LSP does not guarantee a correct overlay label mapping describes a neighboring protocol concern. In this case the controlling fact is incorrect label removal can expose payload handling that the egress does not expect. A correct remediation would verify the label action and egress handling for the intended service stack and demonstrate: A traced packet arrives at egress with the correct remaining stack or payload.

B:

The proposed principle concerns another network fault: A configured static route need not become usable forwarding state when its next hop cannot resolve. Here, incorrect label removal can expose payload handling that the egress does not expect. The most direct correction is to verify the label action and egress handling for the intended service stack, confirmed by a traced packet arrives at egress with the correct remaining stack or payload.

C:

That result would be useful for a different failure, namely: A router sees multiple labels on a packet but an engineer only examines the innermost label when troubleshooting transit transport. The current case specifically calls for: Verify the label action and egress handling for the intended service stack. The required observed result is: A traced packet arrives at egress with the correct remaining stack or payload.

Question 555

A service provider adds a second VLAN tag to customer frames but the downstream switch treats it as an ordinary single tag. Which corrective action and confirmation pair is most appropriate?

  1. Implement: Validate outer tag encapsulation and EtherType expectations across the handoff. Verify: A packet capture shows the intended outer and inner VLAN tags end to end.
  2. Control: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. Accepted result: A capture shows the expected outer service tag between provider edges.
  3. Action: Review root protection at the provider-facing boundary. Evidence: A superior BPDU test does not move the approved provider root.
  4. Repair: Set appropriate port mode and tag handling at the service edge. Check: The test frame is accepted only under the approved tagging plan.

Explanation

Correct Answer

A:

The case turns on the distinction that stacked VLAN services require compatible tagging interpretation at both ends. Apply this concrete engineering step: Validate outer tag encapsulation and EtherType expectations across the handoff. An acceptable verification outcome is: A packet capture shows the intended outer and inner VLAN tags end to end.

Incorrect Answers

B:

This answer would be more suitable when tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing, where the corrective action is to check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. The failure here is different: Stacked VLAN services require compatible tagging interpretation at both ends. Required validation: A packet capture shows the intended outer and inner VLAN tags end to end.

C:

This option overlooks the decisive condition. Its supporting principle is root protection can prevent undesired superior-root claims from changing root placement, while this scenario depends on stacked VLAN services require compatible tagging interpretation at both ends. Verify the correction with: A packet capture shows the intended outer and inner VLAN tags end to end.

D:

Customer-facing encapsulation must match the traffic format at ingress describes a neighboring protocol concern. In this case the controlling fact is stacked VLAN services require compatible tagging interpretation at both ends. A correct remediation would validate outer tag encapsulation and EtherType expectations across the handoff and demonstrate: A packet capture shows the intended outer and inner VLAN tags end to end.

Question 556

An RSVP LSP needs to avoid a congested link but its path is left to ordinary unconstrained routing. Which protocol behavior most directly determines the correct diagnosis?

  1. The governing rule is: LDP signaling depends on the routing and transport state of its endpoints.
  2. The key distinction is: RSVP-TE path choice can account for configured topology constraints and resources.
  3. Protocol behavior: Control-plane route visibility and installed forwarding state are distinct evidence.
  4. Underlying principle: MPLS forwarding relies on label bindings and compatible next-hop state.

Explanation

Correct Answer

B:

Because rSVP-TE path choice can account for configured topology constraints and resources, the best response is to review explicit-path or constraint-based RSVP traffic-engineering intent. A reviewer can close the technical case only after confirming that the installed LSP avoids the prohibited link in a failure-free test.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A provider's LDP neighbors disappear after an IGP outage while physical links remain up. The current case specifically calls for: Review explicit-path or constraint-based RSVP traffic-engineering intent. The required observed result is: The installed LSP avoids the prohibited link in a failure-free test.

C:

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 review explicit-path or constraint-based RSVP traffic-engineering intent; verify: The installed LSP avoids the prohibited link in a failure-free test.

D:

The alternative addresses a provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table, not the present root cause. Here the selected correction must reflect rSVP-TE path choice can account for configured topology constraints and resources. Test for: The installed LSP avoids the prohibited link in a failure-free test.

Question 557

Two BGP paths have different local preferences and a technician expects the shorter AS path always to win. Which post-change observation most strongly confirms the correction?

  1. Verification result: A packet trace shows OPEN and KEEPALIVE before accepted UPDATE information.
  2. Closeout evidence: The intended local preference policy selects the approved egress.
  3. Acceptance check: The session reaches Established only with the documented correct peer AS.
  4. The test confirms that lDP sessions recover and labeled FEC bindings reappear after underlay repair.

Explanation

Correct Answer

B:

The case turns on the distinction that bGP best-path selection considers higher-priority decision attributes before AS-path length. Apply this concrete engineering step: Evaluate routing-policy local preference before later BGP path-selection attributes. An acceptable verification outcome is: The intended local preference policy selects the approved egress.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is bGP message types have separate roles in session formation and reachability exchange, while this scenario depends on bGP best-path selection considers higher-priority decision attributes before AS-path length. Verify the correction with: The intended local preference policy selects the approved egress.

C:

The proposed principle concerns another network fault: BGP OPEN negotiation includes AS identity that must match peering intent. Here, bGP best-path selection considers higher-priority decision attributes before AS-path length. The most direct correction is to evaluate routing-policy local preference before later BGP path-selection attributes, confirmed by the intended local preference policy selects the approved egress.

D:

That result would be useful for a different failure, namely: A provider's LDP neighbors disappear after an IGP outage while physical links remain up. The current case specifically calls for: Evaluate routing-policy local preference before later BGP path-selection attributes. The required observed result is: The intended local preference policy selects the approved egress.

Question 558

A routing peer detects a dead neighbor too slowly for a real-time service even when the interface stays up. Which test result would best confirm a successful fix?

  1. Expected observation: A controlled forwarding failure is detected within the approved target.
  2. Verification result: A switchover test assesses both packet forwarding and routing neighbor continuity.
  3. Closeout evidence: A shared stable topology produces consistent path computation.
  4. Acceptance check: A planned switchover test documents forwarding and neighbor behavior against the HA design.

Explanation

Correct Answer

A:

Correct diagnosis: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. The appropriate action is: Evaluate BFD liveness detection with the associated routing protocol. The follow-up evidence required is: A controlled forwarding failure is detected within the approved target.

Incorrect Answers

B:

The alternative addresses a dual-Routing-Engine chassis uses GRES but an engineer assumes routing protocol control state is preserved without any other feature, not the present root cause. Here the selected correction must reflect bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Test for: A controlled forwarding failure is detected within the approved target.

C:

This answer would be more suitable when a site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency, where the corrective action is to inspect link-state databases and SPF output on affected routers. The failure here is different: BFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Required validation: A controlled forwarding failure is detected within the approved target.

D:

This option overlooks the decisive condition. Its supporting principle is forwarding-plane continuity does not prove control-plane routing continuity, while this scenario depends on bFD provides faster forwarding-path liveness information than ordinary long protocol timers in supported deployments. Verify the correction with: A controlled forwarding failure is detected within the approved target.

Question 559

Tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing. Which combined repair and acceptance criterion is strongest?

  1. Control: Review root bridge priority and MAC-based bridge identifier comparison. Accepted result: The intended device is root under the tested priorities and tie-breakers.
  2. Action: Validate outer tag encapsulation and EtherType expectations across the handoff. Evidence: A packet capture shows the intended outer and inner VLAN tags end to end.
  3. Repair: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. Check: A capture shows the expected outer service tag between provider edges.
  4. Change: Generate controlled frames and observe normal learning on the correct bridge domain. Test: A source MAC appears on the expected port after a test frame.

Explanation

Correct Answer

C:

The case turns on the distinction that provider bridging service tags must be applied and removed at the designed boundaries. Apply this concrete engineering step: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. An acceptable verification outcome is: A capture shows the expected outer service tag between provider edges.

Incorrect Answers

A:

The proposed principle concerns another network fault: Traditional spanning-tree root election favors the lowest bridge ID. Here, provider bridging service tags must be applied and removed at the designed boundaries. The most direct correction is to check Q-in-Q input/output encapsulation and rewrite behavior at the handoff, confirmed by a capture shows the expected outer service tag between provider edges.

B:

That result would be useful for a different failure, namely: A service provider adds a second VLAN tag to customer frames but the downstream switch treats it as an ordinary single tag. The current case specifically calls for: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. The required observed result is: A capture shows the expected outer service tag between provider edges.

D:

Generate controlled frames and observe normal learning on the correct bridge domain is a relevant step for the separate scenario in which a MAC table is empty after a restart and an operator manually inserts dozens of addresses before sending test traffic. It does not directly fix this case. Instead check Q-in-Q input/output encapsulation and rewrite behavior at the handoff; verify: A capture shows the expected outer service tag between provider edges.

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.

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