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 42

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.

Question 411

A MAC table is empty after a restart and an operator manually inserts dozens of addresses before sending test traffic. What assessment accurately links the fault to its correction?

  1. Root issue: Logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. Correction: Document VLAN-aware versus flexible tagging and unit classification requirements.
  2. Cause: Provider outer VLAN classification must preserve tenant isolation. Response: Assign distinct service encapsulation and verify edge translation rules.
  3. Diagnosis: Conflicting local GR and NSR configuration must be resolved before activation. Action: Remove the incompatible local mode and validate the supported HA configuration.
  4. Explanation: Dynamic MAC tables are populated by observed frames and need not be prefilled. Repair: Generate controlled frames and observe normal learning on the correct bridge domain.

Explanation

Correct Answer

D:

The critical observation is: Dynamic MAC tables are populated by observed frames and need not be prefilled. Correct it by taking this action: Generate controlled frames and observe normal learning on the correct bridge domain. Confirm the outcome with: A source MAC appears on the expected port after a test frame.

Incorrect Answers

A:

The alternative addresses an Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation, 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.

B:

This answer would be more suitable when a Q-in-Q customer service leaks traffic between two tenants after the outer service VLAN is reused incorrectly, where the corrective action is to assign distinct service encapsulation and verify edge translation rules. 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.

C:

This option overlooks the decisive condition. Its supporting principle is conflicting local GR and NSR configuration must be resolved before activation, while this scenario depends on dynamic MAC tables are populated by observed frames and need not be prefilled. Verify the correction with: A source MAC appears on the expected port after a test frame.

Question 412

Tagged frames arrive at the provider edge with the expected inner VLAN but the outer service tag is missing. Which technical distinction best describes the observed symptom?

  1. The key distinction is: Provider bridging service tags must be applied and removed at the designed boundaries.
  2. Protocol behavior: Dynamic MAC tables are populated by observed frames and need not be prefilled.
  3. Underlying principle: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover.
  4. Root design issue: Untagged frame classification is local to the receiving interface.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Provider bridging service tags must be applied and removed at the designed boundaries. Remedy: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff. Proof: A capture shows the expected outer service tag between provider edges.

Incorrect Answers

B:

This response would target a different source scenario: A MAC table is empty after a restart and an operator manually inserts dozens of addresses before sending test traffic. It cannot establish the current acceptance requirement, which is: A capture shows the expected outer service tag between provider edges. The relevant action is: Check Q-in-Q input/output encapsulation and rewrite behavior at the handoff.

C:

Evaluate nonstop bridging together with the supported Routing Engine redundancy design is a relevant step for the separate scenario in which an Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. 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.

D:

The alternative addresses a native untagged VLAN mismatch makes two switches place the same untagged frames into different segments, not the present root cause. Here the selected correction must reflect provider bridging service tags must be applied and removed at the designed boundaries. Test for: A capture shows the expected outer service tag between provider edges.

Question 413

An Ethernet service must retain bridge state during Routing Engine failover but only Layer 3 HA settings are considered. Which statement identifies the key design assumption that failed?

  1. The governing rule is: NSR and graceful restart on the local restarting device are different approaches and can conflict.
  2. The key distinction is: Conflicting local GR and NSR configuration must be resolved before activation.
  3. Protocol behavior: Loop prevention depends on compatible STP participation across redundant Ethernet links.
  4. Underlying principle: Nonstop bridging protects relevant Layer 2 control-protocol state during switchover.

Explanation

Correct Answer

D:

The selected response implements the principle that nonstop bridging protects relevant Layer 2 control-protocol state during switchover. The engineer should evaluate nonstop bridging together with the supported Routing Engine redundancy design. Successful confirmation means: An authorized switchover maintains bridge control state and service reachability.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is nSR and graceful restart on the local restarting device are different approaches and can conflict, while this scenario depends on nonstop bridging protects relevant Layer 2 control-protocol state during switchover. Verify the correction with: An authorized switchover maintains bridge control state and service reachability.

B:

Conflicting local GR and NSR configuration must be resolved before activation describes a neighboring protocol concern. In this case the controlling fact is nonstop bridging protects relevant Layer 2 control-protocol state during switchover. A correct remediation would evaluate nonstop bridging together with the supported Routing Engine redundancy design and demonstrate: An authorized switchover maintains bridge control state and service reachability.

C:

The proposed principle concerns another network fault: Loop prevention depends on compatible STP participation across redundant Ethernet links. Here, nonstop bridging protects relevant Layer 2 control-protocol state during switchover. The most direct correction is to evaluate nonstop bridging together with the supported Routing Engine redundancy design, confirmed by an authorized switchover maintains bridge control state and service reachability.

Question 414

A provider accepts a route with its own AS in the received path after a risky bypass of loop prevention. What is the most defensible network engineering correction?

  1. Apply this control: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  2. Remediation: Investigate AS-path loop prevention rather than overriding it without risk review.
  3. Recommended change: Align the area membership and verify OSPF interface settings on both sides.
  4. Next step: Restore standard AS-path checks and review any justified exception with design authority.

Explanation

Correct Answer

D:

This is the model-intended best choice because disabling loop prevention can introduce persistent interdomain routing loops. The targeted correction is to restore standard AS-path checks and review any justified exception with design authority. Validate it by observing that an unwanted looped route is rejected in a lab before production change.

Incorrect Answers

A:

Inspect TCP reachability, permitted port 179, and authentication on the transport path is a relevant step for the separate scenario in which an EBGP peer drops repeatedly after a firewall change despite clean interface counters. It does not directly fix this case. Instead restore standard AS-path checks and review any justified exception with design authority; verify: An unwanted looped route is rejected in a lab before production change.

B:

The alternative addresses a provider advertises a customer prefix with its own AS number already present in the return AS path, not the present root cause. Here the selected correction must reflect disabling loop prevention can introduce persistent interdomain routing loops. Test for: An unwanted looped route is rejected in a lab before production change.

C:

This answer would be more suitable when two Junos routers on the same link have mismatched OSPF area identifiers and never form a neighbor relationship, where the corrective action is to align the area membership and verify OSPF interface settings on both sides. The failure here is different: Disabling loop prevention can introduce persistent interdomain routing loops. Required validation: An unwanted looped route is rejected in a lab before production change.

Question 415

Two routers exchange IS-IS Hellos but one rejects the neighbor during area validation. Which test result would best confirm a successful fix?

  1. Expected observation: A protocol check shows the authorized level and matching adjacency.
  2. Verification result: The report explains the fault from interface through neighbor to selected route.
  3. Closeout evidence: Only approved customer prefixes enter the provider's active routing table.
  4. Acceptance check: A point-to-point link reaches the expected adjacency state without DIS election.

Explanation

Correct Answer

A:

The selected response implements the principle that area mismatch can affect Level 1 adjacency even when packets are received. The engineer should compare NET area addresses and intended L1 or L2 adjacency mode. Successful confirmation means: A protocol check shows the authorized level and matching adjacency.

Incorrect Answers

B:

That result would be useful for a different failure, namely: An IS-IS troubleshooting report shows interface counters only, with no adjacency or link-state evidence. The current case specifically calls for: Compare NET area addresses and intended L1 or L2 adjacency mode. The required observed result is: A protocol check shows the authorized level and matching adjacency.

C:

This response would target a different source scenario: A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. It cannot establish the current acceptance requirement, which is: A protocol check shows the authorized level and matching adjacency. The relevant action is: Compare NET area addresses and intended L1 or L2 adjacency mode.

D:

Differentiate multiaccess DIS election from point-to-point adjacency behavior is a relevant step for the separate scenario in which an engineer expects an IS-IS Designated Intermediate System election on a point-to-point core link. It does not directly fix this case. Instead compare NET area addresses and intended L1 or L2 adjacency mode; verify: A protocol check shows the authorized level and matching adjacency.

Question 416

An OSPF interface is accidentally set passive on a provider edge and its neighbor never appears. Which next action best resolves this observed routing or switching failure?

  1. Next step: Differentiate multiaccess DIS election from point-to-point adjacency behavior.
  2. Corrective action: Review hierarchical OSPF backbone attachment and area border placement.
  3. Apply this control: Review the passive-interface configuration and required active neighbor links.
  4. Remediation: Inspect ABR area configuration, route export rules and summary policy.

Explanation

Correct Answer

C:

This option addresses the stated case rather than another networking issue. Principle: Passive OSPF interfaces can advertise networks without forming neighbors on that interface. Remedy: Review the passive-interface configuration and required active neighbor links. Proof: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

Incorrect Answers

A:

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: Passive OSPF interfaces can advertise networks without forming neighbors on that interface. Required validation: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

B:

This option overlooks the decisive condition. Its supporting principle is multi-area OSPF design requires attention to backbone connectivity, while this scenario depends on passive OSPF interfaces can advertise networks without forming neighbors on that interface. Verify the correction with: The intended backbone neighbor forms and customer-only passive interfaces remain passive.

D:

The proposed principle concerns another network fault: Interarea reachability depends on the ABR's view and allowed advertisements. Here, passive OSPF interfaces can advertise networks without forming neighbors on that interface. The most direct correction is to review the passive-interface configuration and required active neighbor links, confirmed by the intended backbone neighbor forms and customer-only passive interfaces remain passive.

Question 417

A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. What action-and-test pairing directly resolves the case?

  1. Implement: Create explicit import policy and prefix limits aligned to customer contracts. Verify: Only approved customer prefixes enter the provider's active routing table.
  2. Control: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Accepted result: The test demonstrates loop prevention without advertising false service reachability.
  3. Action: Document the discard behavior and determine whether the aggregate should remain advertised. Evidence: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.
  4. Repair: 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.

Explanation

Correct Answer

C:

The critical observation is: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong. Correct it by taking this action: Document the discard behavior and determine whether the aggregate should remain advertised. Confirm the outcome with: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.

Incorrect Answers

A:

This response would target a different source scenario: A new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes. It cannot establish the current acceptance requirement, which is: Loss-of-specific-route testing produces the approved withdrawal or discard outcome. The relevant action is: Document the discard behavior and determine whether the aggregate should remain advertised.

B:

Compare withdrawal and blackhole behavior under a lab failure before changing the safety route is a relevant step for the separate scenario in which an engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop. It does not directly fix this case. Instead document the discard behavior and determine whether the aggregate should remain advertised; verify: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.

D:

This answer would be more suitable when a summary route is advertised even though the operator expects every more-specific customer route to remain reachable, where the corrective action is to distinguish aggregate reachability from specific-route forwarding and test loss of component routes. The failure here is different: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong. Required validation: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.

Question 418

An engineer modifies BGP keepalive or hold timers and the session flaps during CPU pressure. Which statement identifies the key design assumption that failed?

  1. The governing rule is: LDP signaling depends on the routing and transport state of its endpoints.
  2. The key distinction is: Aggressive liveness settings can magnify loss or processing delays.
  3. Protocol behavior: BGP best-path selection considers higher-priority decision attributes before AS-path length.
  4. Underlying principle: BGP group-level export policies must preserve customer routing isolation.

Explanation

Correct Answer

B:

This is the model-intended best choice because aggressive liveness settings can magnify loss or processing delays. The targeted correction is to compare negotiated timers and protocol logs with routing-engine and packet conditions. Validate it by observing that the restored session remains stable while meeting the approved detection target.

Incorrect Answers

A:

LDP signaling depends on the routing and transport state of its endpoints describes a neighboring protocol concern. In this case the controlling fact is aggressive liveness settings can magnify loss or processing delays. A correct remediation would compare negotiated timers and protocol logs with routing-engine and packet conditions and demonstrate: The restored session remains stable while meeting the approved detection target.

C:

That result would be useful for a different failure, namely: Two BGP paths have different local preferences and a technician expects the shorter AS path always to win. The current case specifically calls for: Compare negotiated timers and protocol logs with routing-engine and packet conditions. The required observed result is: The restored session remains stable while meeting the approved detection target.

D:

This response would target a different source scenario: One customer’s new prefixes are advertised to a second unrelated customer via a shared export group. It cannot establish the current acceptance requirement, which is: The restored session remains stable while meeting the approved detection target. The relevant action is: Compare negotiated timers and protocol logs with routing-engine and packet conditions.

Question 419

An MPLS packet trace shows the outer label is removed earlier than expected and the engineer calls it a malformed packet. Which root-cause explanation and corrective action fit the case?

  1. Diagnosis: Traffic-engineering intent must be reflected in the signaled operational LSP path. Action: Review explicit or constraint-based path selection against current resource availability.
  2. Explanation: BGP sessions require sustained TCP connectivity independent of physical interface health. Repair: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  3. Fault mechanism: An upstream LSR can remove a label before the egress in an appropriate PHP design. Remediation: Recognize penultimate-hop popping as an allowed LSP forwarding behavior.
  4. Root issue: Label stack changes can be legitimate parts of LSP forwarding design. Correction: Verify whether PHP or explicit-null behavior is configured and intended.

Explanation

Correct Answer

D:

The critical observation is: Label stack changes can be legitimate parts of LSP forwarding design. Correct it by taking this action: Verify whether PHP or explicit-null behavior is configured and intended. Confirm the outcome with: The observed penultimate and egress labels agree with the supported LSP behavior.

Incorrect Answers

A:

The alternative addresses an RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change, not the present root cause. Here the selected correction must reflect label stack changes can be legitimate parts of LSP forwarding design. Test for: The observed penultimate and egress labels agree with the supported LSP behavior.

B:

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: Label stack changes can be legitimate parts of LSP forwarding design. Required validation: The observed penultimate and egress labels agree with the supported LSP behavior.

C:

This option overlooks the decisive condition. Its supporting principle is an upstream LSR can remove a label before the egress in an appropriate PHP design, while this scenario depends on label stack changes can be legitimate parts of LSP forwarding design. Verify the correction with: The observed penultimate and egress labels agree with the supported LSP behavior.

Question 420

An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. What observable result most directly verifies the intended configuration?

  1. Expected observation: The corrected transit hop forwards the expected incoming label to its planned outgoing label.
  2. Verification result: The repaired hop has the expected swap operation and carries a test packet.
  3. Closeout evidence: A packet decode identifies label fields separately from the carried IP packet.
  4. Acceptance check: The intended local preference policy selects the approved egress.

Explanation

Correct Answer

B:

Because label-switching errors can occur even when control-plane endpoint reachability is good, the best response is to inspect the incoming label, outgoing label and interface on each affected LSR. A reviewer can close the technical case only after confirming that the repaired hop has the expected swap operation and carries a test packet.

Incorrect Answers

A:

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: Inspect the incoming label, outgoing label and interface on each affected LSR. The required observed result is: The repaired hop has the expected swap operation and carries a test packet.

C:

Distinguish the MPLS shim label stack from the encapsulated payload is a relevant step for the separate scenario in which an operator expects an MPLS label to represent an entire customer IP packet header. It does not directly fix this case. Instead inspect the incoming label, outgoing label and interface on each affected LSR; verify: The repaired hop has the expected swap operation and carries a test packet.

D:

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 label-switching errors can occur even when control-plane endpoint reachability is good. Test for: The repaired hop has the expected swap operation and carries a test packet.

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