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 49

Question 480

An operator tries to solve a MAC-learning loop by adding a static IP route in the core. What operational check demonstrates that the intended outcome occurred?

  1. Expected observation: A tagged test frame reaches the approved remote port in the same domain.
  2. Verification result: The same controlled untagged frame maps to the intended VLAN on both sides.
  3. Closeout evidence: A superior BPDU test preserves the intended root with a logged protective state.
  4. Acceptance check: The frame loop is removed and learned MAC locations become stable.

Explanation

Correct Answer

D:

Because layer 2 forwarding loops cannot be reliably corrected through unrelated IP routing alone, the best response is to trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses. A reviewer can close the technical case only after confirming that the frame loop is removed and learned MAC locations become stable.

Incorrect Answers

A:

This answer would be more suitable when a port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain, where the corrective action is to trace frame classification and virtual-switch bridge-domain association. The failure here is different: Layer 2 forwarding loops cannot be reliably corrected through unrelated IP routing alone. Required validation: The frame loop is removed and learned MAC locations become stable.

B:

This option overlooks the decisive condition. Its supporting principle is untagged frame classification is local to the receiving interface, while this scenario depends on layer 2 forwarding loops cannot be reliably corrected through unrelated IP routing alone. Verify the correction with: The frame loop is removed and learned MAC locations become stable.

C:

Customer control traffic must not displace the authorized provider root describes a neighboring protocol concern. In this case the controlling fact is layer 2 forwarding loops cannot be reliably corrected through unrelated IP routing alone. A correct remediation would trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses and demonstrate: The frame loop is removed and learned MAC locations become stable.

Question 481

An engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop. Which combined repair and acceptance criterion is strongest?

  1. Control: Document the discard behavior and determine whether the aggregate should remain advertised. Accepted result: Loss-of-specific-route testing produces the approved withdrawal or discard outcome.
  2. Action: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Evidence: The test demonstrates loop prevention without advertising false service reachability.
  3. Repair: Inspect TCP reachability, permitted port 179, and authentication on the transport path. Check: An authenticated TCP session stays Established after the rule correction.
  4. Change: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples. Test: Only the subscriber's approved traffic enters the alternate routing instance.

Explanation

Correct Answer

B:

The selected response implements the principle that discard routes may intentionally bound routing loops while dynamic specifics converge. The engineer should compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Successful confirmation means: The test demonstrates loop prevention without advertising false service reachability.

Incorrect Answers

A:

This response would target a different source scenario: A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. It cannot establish the current acceptance requirement, which is: The test demonstrates loop prevention without advertising false service reachability. The relevant action is: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.

C:

The alternative addresses an EBGP peer drops repeatedly after a firewall change despite clean interface counters, not the present root cause. Here the selected correction must reflect discard routes may intentionally bound routing loops while dynamic specifics converge. Test for: The test demonstrates loop prevention without advertising false service reachability.

D:

This answer would be more suitable when a filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet, where the corrective action is to tighten the filter match and verify the next-table lookup with explicit positive and negative examples. The failure here is different: Discard routes may intentionally bound routing loops while dynamic specifics converge. Required validation: The test demonstrates loop prevention without advertising false service reachability.

Question 482

A policy change unexpectedly makes a backup transit provider carry most outbound traffic. What implementation step and validation result should be selected?

  1. Implement: Inspect TCP reachability, permitted port 179, and authentication on the transport path. Verify: An authenticated TCP session stays Established after the rule correction.
  2. Control: Verify the label action and egress handling for the intended service stack. Accepted result: A traced packet arrives at egress with the correct remaining stack or payload.
  3. Action: Inspect local preference, export/import inheritance and selected BGP path attributes. Evidence: Traffic uses the primary provider until the documented failover condition occurs.
  4. Repair: Review EBGP multihop transport reachability and session parameters. Check: The TCP session establishes across the intended transport path.

Explanation

Correct Answer

C:

Correct diagnosis: Routing policy changes can override expected primary and backup peering intent. The appropriate action is: Inspect local preference, export/import inheritance and selected BGP path attributes. The follow-up evidence required is: Traffic uses the primary provider until the documented failover condition occurs.

Incorrect Answers

A:

BGP sessions require sustained TCP connectivity independent of physical interface health 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.

B:

The proposed principle concerns another network fault: Incorrect label removal can expose payload handling that the egress does not expect. 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.

D:

This response would target a different source scenario: A multihop EBGP session is configured like a directly connected neighbor and never establishes across the transit hop. It cannot establish the current acceptance requirement, which is: Traffic uses the primary provider until the documented failover condition occurs. The relevant action is: Inspect local preference, export/import inheritance and selected BGP path attributes.

Question 483

A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. Which cause-and-remedy pairing reflects the observed problem?

  1. Explanation: iBGP can preserve externally learned next-hop information that internal speakers must resolve. Repair: Review BGP next-hop reachability and explicit next-hop handling.
  2. Fault mechanism: OSPF neighbor-state interpretation depends on multiaccess election roles. Remediation: Check DR and BDR roles and expected 2-Way peers before changing a healthy segment.
  3. Root issue: BGP OPEN negotiation includes AS identity that must match peering intent. Correction: Confirm the configured local and peer AS values with the authoritative design.
  4. Cause: BGP transport connectivity does not guarantee every address family is negotiated and active. Response: Verify negotiated address families and family-specific routing tables.

Explanation

Correct Answer

A:

The case turns on the distinction that iBGP can preserve externally learned next-hop information that internal speakers must resolve. Apply this concrete engineering step: Review BGP next-hop reachability and explicit next-hop handling. An acceptable verification outcome is: The internal peer has a valid route to the BGP next hop and installs the prefix.

Incorrect Answers

B:

This answer would be more suitable when a broadcast core VLAN has only one Full adjacency and the engineer wants to reset all routers immediately, where the corrective action is to check DR and BDR roles and expected 2-Way peers before changing a healthy segment. The failure here is different: iBGP can preserve externally learned next-hop information that internal speakers must resolve. Required validation: The internal peer has a valid route to the BGP next hop and installs the prefix.

C:

This option overlooks the decisive condition. Its supporting principle is bGP OPEN negotiation includes AS identity that must match peering intent, while this scenario depends on iBGP can preserve externally learned next-hop information that internal speakers must resolve. Verify the correction with: The internal peer has a valid route to the BGP next hop and installs the prefix.

D:

BGP transport connectivity does not guarantee every address family is negotiated and active describes a neighboring protocol concern. In this case the controlling fact is iBGP can preserve externally learned next-hop information that internal speakers must resolve. A correct remediation would review BGP next-hop reachability and explicit next-hop handling and demonstrate: The internal peer has a valid route to the BGP next hop and installs the prefix.

Question 484

An input firewall filter diverts all transit traffic to a management routing instance by mistake. What is the primary routing or switching concept illustrated?

  1. Root design issue: Overlapping address classification makes precise route-filter and policy terms essential.
  2. The governing rule is: A discard summary can prevent loops but can blackhole traffic when reachability assumptions are wrong.
  3. The key distinction is: Filter-based routing policy requires explicit match conditions and a safe default behavior.
  4. Protocol behavior: Multi-area OSPF design requires attention to backbone connectivity.

Explanation

Correct Answer

C:

This is the model-intended best choice because filter-based routing policy requires explicit match conditions and a safe default behavior. The targeted correction is to narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes. Validate it by observing that only approved traffic uses the alternate table while ordinary transit remains on its path.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. The current case specifically calls for: Narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes. The required observed result is: Only approved traffic uses the alternate table while ordinary transit remains on its path.

B:

This response would target a different source scenario: A static discard route intended as a summary safety mechanism becomes the only active route after customer specifics disappear. It cannot establish the current acceptance requirement, which is: Only approved traffic uses the alternate table while ordinary transit remains on its path. The relevant action is: Narrow filter match terms and validate filter-based forwarding for both matched and unmatched probes.

D:

The alternative addresses a router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0, not the present root cause. Here the selected correction must reflect filter-based routing policy requires explicit match conditions and a safe default behavior. Test for: Only approved traffic uses the alternate table while ordinary transit remains on its path.

Question 485

A branch uses a higher OSPF interface cost but expects that branch to remain the preferred primary path. Which cause-and-remedy pairing reflects the observed problem?

  1. Cause: IS-IS shortest-path output depends on effective metrics across the route. Response: Measure end-to-end route choices and review configured interface metrics.
  2. Diagnosis: OSPF normally prefers the least accumulated metric to a destination. Action: Revisit additive path cost and verify SPF outcomes across alternative links.
  3. Explanation: Receiving topology data does not guarantee a route becomes active and installed. Repair: Compare received LSAs with route selection, area eligibility and next-hop resolution.
  4. Fault mechanism: Multi-area OSPF design requires attention to backbone connectivity. Remediation: Review hierarchical OSPF backbone attachment and area border placement.

Explanation

Correct Answer

B:

The case turns on the distinction that oSPF normally prefers the least accumulated metric to a destination. Apply this concrete engineering step: Revisit additive path cost and verify SPF outcomes across alternative links. An acceptable verification outcome is: The intended lower-total-cost path wins under steady-state conditions.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is iS-IS shortest-path output depends on effective metrics across the route, while this scenario depends on oSPF normally prefers the least accumulated metric to a destination. Verify the correction with: The intended lower-total-cost path wins under steady-state conditions.

C:

The proposed principle concerns another network fault: Receiving topology data does not guarantee a route becomes active and installed. Here, oSPF normally prefers the least accumulated metric to a destination. The most direct correction is to revisit additive path cost and verify SPF outcomes across alternative links, confirmed by the intended lower-total-cost path wins under steady-state conditions.

D:

That result would be useful for a different failure, namely: A router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. The current case specifically calls for: Revisit additive path cost and verify SPF outcomes across alternative links. The required observed result is: The intended lower-total-cost path wins under steady-state conditions.

Question 486

A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. What observable result most directly verifies the intended configuration?

  1. The test confirms that a shared stable topology produces consistent path computation.
  2. Expected observation: The routing table exposes the selection reason and the intended route is installed.
  3. Verification result: A route lookup shows an active reachable next hop and traffic reaches the customer.
  4. Closeout evidence: The intended lower-total-cost path wins under steady-state conditions.

Explanation

Correct Answer

A:

Correct diagnosis: OSPF route selection follows each router's synchronized topology view. The appropriate action is: Inspect link-state databases and SPF output on affected routers. The follow-up evidence required is: A shared stable topology produces consistent path computation.

Incorrect Answers

B:

The alternative addresses an OSPF packet capture shows Link State Updates but the route remains hidden from the active table, not the present root cause. Here the selected correction must reflect oSPF route selection follows each router's synchronized topology view. Test for: A shared stable topology produces consistent path computation.

C:

This answer would be more suitable when a provider router has a static route for a customer prefix but its configured next hop is not reachable through any active route, where the corrective action is to verify recursive next-hop reachability before relying on the static route. The failure here is different: OSPF route selection follows each router's synchronized topology view. Required validation: A shared stable topology produces consistent path computation.

D:

This option overlooks the decisive condition. Its supporting principle is oSPF normally prefers the least accumulated metric to a destination, while this scenario depends on oSPF route selection follows each router's synchronized topology view. Verify the correction with: A shared stable topology produces consistent path computation.

Question 487

An RSVP tunnel unexpectedly crosses a low-capacity link after a traffic-engineering policy change. Which technical distinction best describes the observed symptom?

  1. The key distinction is: BGP best-path selection considers higher-priority decision attributes before AS-path length.
  2. Protocol behavior: Traffic-engineering intent must be reflected in the signaled operational LSP path.
  3. Underlying principle: Label-switching errors can occur even when control-plane endpoint reachability is good.
  4. Root design issue: An upstream LSR can remove a label before the egress in an appropriate PHP design.

Explanation

Correct Answer

B:

The critical observation is: Traffic-engineering intent must be reflected in the signaled operational LSP path. Correct it by taking this action: Review explicit or constraint-based path selection against current resource availability. Confirm the outcome with: An operational path check excludes the unapproved transit link.

Incorrect Answers

A:

The proposed principle concerns another network fault: BGP best-path selection considers higher-priority decision attributes before AS-path length. Here, traffic-engineering intent must be reflected in the signaled operational LSP path. The most direct correction is to review explicit or constraint-based path selection against current resource availability, confirmed by an operational path check excludes the unapproved transit link.

C:

This response would target a different source scenario: An ingress LSP shows up but transit packets are dropped after one router swaps to an unexpected label. It cannot establish the current acceptance requirement, which is: An operational path check excludes the unapproved transit link. The relevant action is: Review explicit or constraint-based path selection against current resource availability.

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 review explicit or constraint-based path selection against current resource availability; verify: An operational path check excludes the unapproved transit link.

Question 488

A router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table. Which cause-and-remedy pairing reflects the observed problem?

  1. Explanation: BGP OPEN negotiation includes AS identity that must match peering intent. Repair: Confirm the configured local and peer AS values with the authoritative design.
  2. Fault mechanism: Discard routes may intentionally bound routing loops while dynamic specifics converge. Remediation: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.
  3. Root issue: Aggregation can hide individual component failures if advertisement policy is not controlled. Correction: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.
  4. Cause: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Response: Review filter-based forwarding classification and the intended next-table selection.

Explanation

Correct Answer

D:

Because policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table, the best response is to review filter-based forwarding classification and the intended next-table selection. A reviewer can close the technical case only after confirming that a trace of matching and nonmatching packets shows the approved lookup table.

Incorrect Answers

A:

This answer would be more suitable when a remote BGP neighbor uses a different AS number than configured and the session fails during OPEN negotiation, where the corrective action is to confirm the configured local and peer AS values with the authoritative design. The failure here is different: Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Required validation: A trace of matching and nonmatching packets shows the approved lookup table.

B:

This option overlooks the decisive condition. Its supporting principle is discard routes may intentionally bound routing loops while dynamic specifics converge, while this scenario depends on policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. Verify the correction with: A trace of matching and nonmatching packets shows the approved lookup table.

C:

Aggregation can hide individual component failures if advertisement policy is not controlled describes a neighboring protocol concern. In this case the controlling fact is policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table. A correct remediation would review filter-based forwarding classification and the intended next-table selection and demonstrate: A trace of matching and nonmatching packets shows the approved lookup table.

Question 489

A provider chooses segment-routing MPLS but assumes every transit hop needs per-LSP RSVP state. Which post-change observation most strongly confirms the correction?

  1. Verification result: A test packet follows its segment list through installed SR forwarding.
  2. Closeout evidence: The backup LSP establishes on a permitted alternate path.
  3. Acceptance check: The restored IGP path permits LDP forwarding to the remote endpoint.
  4. The test confirms that only approved customer prefixes enter the provider's active routing table.

Explanation

Correct Answer

A:

Underlying cause: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Corrective action: review segment identifiers and forwarding under SR-MPLS. Verify the outcome: A test packet follows its segment list through installed SR forwarding.

Incorrect Answers

B:

Update the engineered path constraints and verify candidate topology availability is a relevant step for the separate scenario in which an operator configured an explicit RSVP path through a link that is now administratively down. It does not directly fix this case. Instead review segment identifiers and forwarding under SR-MPLS; verify: A test packet follows its segment list through installed SR forwarding.

C:

The alternative addresses an LDP-signaled LSP fails when the IGP route to the remote loopback disappears, not the present root cause. Here the selected correction must reflect sR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Test for: A test packet follows its segment list through installed SR forwarding.

D:

This answer would be more suitable when a new peer sends more customer routes than expected and the team assumes BGP automatically filters unrelated prefixes, where the corrective action is to create explicit import policy and prefix limits aligned to customer contracts. The failure here is different: SR-MPLS can encode forwarding intent using segment labels without per-path RSVP signaling in transit. Required validation: A test packet follows its segment list through installed SR forwarding.

Question 490

A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. What is the primary routing or switching concept illustrated?

  1. Underlying principle: Configuration intent must be verified against the actual elected spanning-tree root.
  2. Root design issue: Protective edge-port shutdown is evidence of BPDU policy enforcement.
  3. The governing rule is: MSTP can group VLANs into multiple spanning-tree instances under shared region parameters.
  4. The key distinction is: Ethernet forwarding uses bridge-domain context rather than arbitrary IP-route matching.

Explanation

Correct Answer

B:

This is the model-intended best choice because protective edge-port shutdown is evidence of BPDU policy enforcement. The targeted correction is to verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. Validate it by observing that the approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

Incorrect Answers

A:

Configuration intent must be verified against the actual elected spanning-tree root describes a neighboring protocol concern. In this case the controlling fact is protective edge-port shutdown is evidence of BPDU policy enforcement. A correct remediation would verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards and demonstrate: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

C:

That result would be useful for a different failure, namely: A data center needs separate spanning trees for VLAN groupings but the plan uses a single root for every VLAN with no design review. The current case specifically calls for: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards. The required observed result is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled.

D:

This response would target a different source scenario: A port belongs to a VLAN but traffic to a remote site is forwarded through a different bridge domain. It cannot establish the current acceptance requirement, which is: The approved endpoint reconnects without unexpected BPDUs and protection stays enabled. The relevant action is: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.

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