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 21

Question 200

A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. Which corrective action and confirmation pair is most appropriate?

  1. Repair: Review filter-based forwarding classification and the intended next-table selection. Check: A trace of matching and nonmatching packets shows the approved lookup table.
  2. Change: Compare RIB selection with forwarding-table installation and next-hop resolution. Test: The forwarding entry uses the correct next hop for the active route.
  3. Implement: Review each interface's OSPF metric and compare end-to-end computed costs. Verify: A post-change route view selects the approved shortest path.
  4. Control: Inspect the configuration, active route state and next-hop reachability before changing preference. Accepted result: The static route becomes active after the actual next-hop fault is corrected.

Explanation

Correct Answer

B:

Correct diagnosis: Control-plane route visibility and installed forwarding state are distinct evidence. The appropriate action is: Compare RIB selection with forwarding-table installation and next-hop resolution. The follow-up evidence required is: The forwarding entry uses the correct next hop for the active route.

Incorrect Answers

A:

This answer would be more suitable when a router selects a route in one routing instance while the forwarding policy sends matching traffic into a different table, where the corrective action is to review filter-based forwarding classification and the intended next-table selection. The failure here is different: Control-plane route visibility and installed forwarding state are distinct evidence. Required validation: The forwarding entry uses the correct next hop for the active route.

C:

OSPF forwarding decisions depend on cumulative metric, not interface bandwidth labels alone describes a neighboring protocol concern. In this case the controlling fact is control-plane route visibility and installed forwarding state are distinct evidence. A correct remediation would compare RIB selection with forwarding-table installation and next-hop resolution and demonstrate: The forwarding entry uses the correct next hop for the active route.

D:

The proposed principle concerns another network fault: Operational route troubleshooting starts with active state and resolution evidence. Here, control-plane route visibility and installed forwarding state are distinct evidence. The most direct correction is to compare RIB selection with forwarding-table installation and next-hop resolution, confirmed by the forwarding entry uses the correct next hop for the active route.

Question 201

Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. What remediation is most directly applicable?

  1. Recommended change: Review supported mutual exclusivity and select the intended HA control-plane method.
  2. Next step: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.
  3. Corrective action: Explain root and alternate roles in a loop-free spanning-tree topology.
  4. Apply this control: Inspect interface faults and control-plane events before changing STP timers.

Explanation

Correct Answer

B:

The selected response implements the principle that rSTP can converge faster using explicit roles and handshakes where conditions allow. The engineer should compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. Successful confirmation means: A link-failure test shows the supported rapid role transition.

Incorrect Answers

A:

This response would target a different source scenario: A provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device. It cannot establish the current acceptance requirement, which is: A link-failure test shows the supported rapid role transition. The relevant action is: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions.

C:

The alternative addresses a switch has a root port and alternate port, but the operator assumes both must forward to use all physical bandwidth, not the present root cause. Here the selected correction must reflect rSTP can converge faster using explicit roles and handshakes where conditions allow. Test for: A link-failure test shows the supported rapid role transition.

D:

This answer would be more suitable when an RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement, where the corrective action is to inspect interface faults and control-plane events before changing STP timers. The failure here is different: RSTP can converge faster using explicit roles and handshakes where conditions allow. Required validation: A link-failure test shows the supported rapid role transition.

Question 202

An MPLS service fails after penultimate-hop popping is changed without reviewing the egress disposition. What implementation step and validation result should be selected?

  1. Change: Inspect inet6 family negotiation, filters and IPv6 next-hop validity. Test: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.
  2. Implement: Review explicit or constraint-based path selection against current resource availability. Verify: An operational path check excludes the unapproved transit link.
  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: Verify the label action and egress handling for the intended service stack. Evidence: A traced packet arrives at egress with the correct remaining stack or payload.

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:

IPv4 BGP session liveness does not prove IPv6 family route exchange 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: Traffic-engineering intent must be reflected in the signaled operational LSP path. 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 203

Layer 2 forwarding is disrupted during Routing Engine replacement even though high availability was enabled for routing. What operational check demonstrates that the intended outcome occurred?

  1. Verification result: A controlled switchover retains the expected bridge state and host connectivity.
  2. Closeout evidence: The corrected topology converges without opening an Ethernet loop.
  3. Acceptance check: A tested switchover maintains the required liveness behavior without false failure.
  4. The test confirms that the configuration commits with an approved supported HA combination.

Explanation

Correct Answer

A:

The case turns on the distinction that layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Apply this concrete engineering step: Inspect whether nonstop bridging is available and configured for the relevant L2 control plane. An acceptable verification outcome is: A controlled switchover retains the expected bridge state and host connectivity.

Incorrect Answers

B:

This answer would be more suitable when an alternate uplink remains blocked after the primary path fails because expected BPDUs disappear, where the corrective action is to inspect spanning-tree loop-protection events, root path and link state. The failure here is different: Layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Required validation: A controlled switchover retains the expected bridge state and host connectivity.

C:

This option overlooks the decisive condition. Its supporting principle is bFD HA behavior depends on platform processing placement and timer tolerances, while this scenario depends on layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. Verify the correction with: A controlled switchover retains the expected bridge state and host connectivity.

D:

NSR and graceful restart on the local restarting device are different approaches and can conflict describes a neighboring protocol concern. In this case the controlling fact is layer 3 routing HA does not automatically guarantee L2 bridge-control continuity. A correct remediation would inspect whether nonstop bridging is available and configured for the relevant L2 control plane and demonstrate: A controlled switchover retains the expected bridge state and host connectivity.

Question 204

An inbound MED is assumed to control outgoing traffic even though the receiving network has its own path-selection policies. Which cause-and-remedy pairing reflects the observed problem?

  1. Cause: BGP sessions require sustained TCP connectivity independent of physical interface health. Response: Inspect TCP reachability, permitted port 179, and authentication on the transport path.
  2. Diagnosis: BGP MED influence is conditional on the receiving network's path selection rules. Action: Distinguish an advertised inbound hint from neighboring-AS route policy decisions.
  3. Explanation: BGP message types have separate roles in session formation and reachability exchange. Repair: Distinguish session negotiation from UPDATE message route advertisements.
  4. Fault mechanism: Layered neighbor troubleshooting should separate transport from OSPF parameter mismatches. Remediation: Compare area, interface mode, timers, authentication and physical status on both endpoints.

Explanation

Correct Answer

B:

Because bGP MED influence is conditional on the receiving network's path selection rules, the best response is to distinguish an advertised inbound hint from neighboring-AS route policy decisions. A reviewer can close the technical case only after confirming that a controlled route lookup confirms the neighbor's actual selected entry path.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An EBGP peer drops repeatedly after a firewall change despite clean interface counters. The current case specifically calls for: Distinguish an advertised inbound hint from neighboring-AS route policy decisions. The required observed result is: A controlled route lookup confirms the neighbor's actual selected entry path.

C:

Distinguish session negotiation from UPDATE message route advertisements is a relevant step for the separate scenario in which a provider engineer treats a BGP OPEN message as if it already advertises reachable customer prefixes. It does not directly fix this case. Instead distinguish an advertised inbound hint from neighboring-AS route policy decisions; verify: A controlled route lookup confirms the neighbor's actual selected entry path.

D:

The alternative addresses a new OSPF uplink remains down at the adjacency stage after a router replacement, not the present root cause. Here the selected correction must reflect bGP MED influence is conditional on the receiving network's path selection rules. Test for: A controlled route lookup confirms the neighbor's actual selected entry path.

Question 205

Two equal-capacity IS-IS links receive unequal metrics and traffic takes an unexpected path. What remediation is most directly applicable?

  1. Next step: Compute total advertised IS-IS metrics instead of assuming capacity implies preference.
  2. Corrective action: Compare path metrics and each router's route selection before altering LSP state.
  3. Apply this control: Identify TLVs as structured information within IS-IS protocol data units.
  4. Remediation: Verify compatible network and Hello parameters including mask where applicable.

Explanation

Correct Answer

A:

The critical observation is: IS-IS path selection is based on link-state topology and metrics. Correct it by taking this action: Compute total advertised IS-IS metrics instead of assuming capacity implies preference. Confirm the outcome with: The forwarding route follows the lowest intended metric path.

Incorrect Answers

B:

Common topology information can still produce direction-dependent shortest paths describes a neighboring protocol concern. In this case the controlling fact is iS-IS path selection is based on link-state topology and metrics. A correct remediation would compute total advertised IS-IS metrics instead of assuming capacity implies preference and demonstrate: The forwarding route follows the lowest intended metric path.

C:

The proposed principle concerns another network fault: IS-IS advertises extensible routing attributes using TLV-encoded fields. Here, iS-IS path selection is based on link-state topology and metrics. The most direct correction is to compute total advertised IS-IS metrics instead of assuming capacity implies preference, confirmed by the forwarding route follows the lowest intended metric path.

D:

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: Compute total advertised IS-IS metrics instead of assuming capacity implies preference. The required observed result is: The forwarding route follows the lowest intended metric path.

Question 206

A provider applies an overly broad route import policy and customer prefixes enter an unintended tenant instance. What implementation step and validation result should be selected?

  1. Implement: Restrict routing-policy matches and validate the import and export boundary. Verify: A negative test proves the unrelated customer prefix is absent from the target table.
  2. Control: Separate route-selection and lookup-table changes and test each with candidate configuration. Accepted result: The rollback and candidate checks show the exact intended RIB and FIB outcomes.
  3. Action: Review router priorities and the nonpreemptive properties of DR elections. Evidence: The elected DR and BDR align with the tested election conditions.
  4. Repair: Distinguish equal-cost multipath from the exact traffic-distribution algorithm used by the forwarding plane. Check: A controlled flow test verifies the selected load-sharing behavior.

Explanation

Correct Answer

A:

Correct diagnosis: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. The appropriate action is: Restrict routing-policy matches and validate the import and export boundary. The follow-up evidence required is: A negative test proves the unrelated customer prefix is absent from the target table.

Incorrect Answers

B:

The alternative addresses a policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit, not the present root cause. Here the selected correction must reflect route redistribution must be intentionally scoped to prevent cross-tenant leakage. Test for: A negative test proves the unrelated customer prefix is absent from the target table.

C:

This answer would be more suitable when a broadcast OSPF segment experiences repeated DR elections after interface priority changes, where the corrective action is to review router priorities and the nonpreemptive properties of DR elections. The failure here is different: Route redistribution must be intentionally scoped to prevent cross-tenant leakage. Required validation: A negative test proves the unrelated customer prefix is absent from the target table.

D:

This option overlooks the decisive condition. Its supporting principle is multiple eligible forwarding next hops do not guarantee per-packet round-robin use, while this scenario depends on route redistribution must be intentionally scoped to prevent cross-tenant leakage. Verify the correction with: A negative test proves the unrelated customer prefix is absent from the target table.

Question 207

An operator tries to solve a MAC-learning loop by adding a static IP route in the core. What is the most defensible network engineering correction?

  1. Remediation: Trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses.
  2. Recommended change: Apply supported root protection at the appropriate customer-facing boundary.
  3. Next step: Separate provider service identification from customer VLAN identifiers.
  4. Corrective action: Check committed access VLAN settings and operational membership rather than relying on notes.

Explanation

Correct Answer

A:

The selected response implements the principle that layer 2 forwarding loops cannot be reliably corrected through unrelated IP routing alone. The engineer should trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses. Successful confirmation means: The frame loop is removed and learned MAC locations become stable.

Incorrect Answers

B:

That result would be useful for a different failure, namely: A provider STP domain changes root when a customer sends superior BPDUs from an access port. The current case specifically calls for: Trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses. The required observed result is: The frame loop is removed and learned MAC locations become stable.

C:

This response would target a different source scenario: Two network services use identical customer VLAN IDs and the team assumes their frames must share one L2 broadcast domain. It cannot establish the current acceptance requirement, which is: The frame loop is removed and learned MAC locations become stable. The relevant action is: Trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses.

D:

Check committed access VLAN settings and operational membership rather than relying on notes is a relevant step for the separate scenario in which an access switch forwards untagged traffic into VLAN 20 after a port is moved to VLAN 30. It does not directly fix this case. Instead trace Layer 2 topology, learned MACs and spanning-tree or Ethernet loop defenses; verify: The frame loop is removed and learned MAC locations become stable.

Question 208

An access port sends untagged user traffic but the engineer expects a VLAN tag from the endpoint on every frame. What assessment accurately links the fault to its correction?

  1. Diagnosis: Port mode determines which customer frames are tagged or untagged at the boundary. Action: Distinguish access port traffic from trunk tagging behavior.
  2. Explanation: VLAN reassignment must be verified in actual port classification. Repair: Check committed access VLAN settings and operational membership rather than relying on notes.
  3. Fault mechanism: 802.1Q VLAN identifiers have reserved values and platform constraints. Remediation: Validate the usable VLAN-ID range and reserved tag values.
  4. Root issue: Customer control traffic must not displace the authorized provider root. Correction: Apply supported root protection at the appropriate customer-facing boundary.

Explanation

Correct Answer

A:

This is the model-intended best choice because port mode determines which customer frames are tagged or untagged at the boundary. The targeted correction is to distinguish access port traffic from trunk tagging behavior. Validate it by observing that an end-host packet enters the correct VLAN without requiring endpoint tagging.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is vLAN reassignment must be verified in actual port classification, while this scenario depends on port mode determines which customer frames are tagged or untagged at the boundary. Verify the correction with: An end-host packet enters the correct VLAN without requiring endpoint tagging.

C:

802.1Q VLAN identifiers have reserved values and platform constraints describes a neighboring protocol concern. In this case the controlling fact is port mode determines which customer frames are tagged or untagged at the boundary. A correct remediation would distinguish access port traffic from trunk tagging behavior and demonstrate: An end-host packet enters the correct VLAN without requiring endpoint tagging.

D:

The proposed principle concerns another network fault: Customer control traffic must not displace the authorized provider root. Here, port mode determines which customer frames are tagged or untagged at the boundary. The most direct correction is to distinguish access port traffic from trunk tagging behavior, confirmed by an end-host packet enters the correct VLAN without requiring endpoint tagging.

Question 209

An IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted. Which corrective action and confirmation pair is most appropriate?

  1. Action: Evaluate route reflection with defined cluster and client boundaries. Evidence: The route-reflector design distributes approved prefixes without unintended loops.
  2. Repair: Inspect IS-IS interface enablement, levels, area identifiers and link type. Check: The corrected circuit shows the expected neighbor and link-state entries.
  3. Change: Compare path metrics and each router's route selection before altering LSP state. Test: Each direction's active route matches the documented costs and design.
  4. Implement: Distinguish IS-IS adjacency from address-family reachability advertisements. Verify: The expected IPv6 prefix appears after family and policy review.

Explanation

Correct Answer

C:

The critical observation is: Common topology information can still produce direction-dependent shortest paths. Correct it by taking this action: Compare path metrics and each router's route selection before altering LSP state. Confirm the outcome with: Each direction's active route matches the documented costs and design.

Incorrect Answers

A:

This response would target a different source scenario: A small full-mesh iBGP design becomes difficult to maintain as dozens of PEs are added. It cannot establish the current acceptance requirement, which is: Each direction's active route matches the documented costs and design. The relevant action is: Compare path metrics and each router's route selection before altering LSP state.

B:

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 compare path metrics and each router's route selection before altering LSP state; verify: Each direction's active route matches the documented costs and design.

D:

This answer would be more suitable when a core engineer sees that IPv6 reachability is absent despite IS-IS adjacency and concludes the adjacency itself is broken, where the corrective action is to distinguish IS-IS adjacency from address-family reachability advertisements. The failure here is different: Common topology information can still produce direction-dependent shortest paths. Required validation: Each direction's active route matches the documented costs and design.

Question 210

An alternate uplink remains blocked after the primary path fails because expected BPDUs disappear. Which underlying Junos networking principle explains the failure?

  1. Protocol behavior: Loop protection can prevent unsafe forwarding when control-plane information is missing.
  2. Underlying principle: A redundant alternate path can remain nonforwarding until a failure changes roles.
  3. Root design issue: Protective edge-port shutdown is evidence of BPDU policy enforcement.
  4. The governing rule is: 802.1Q VLAN identifiers have reserved values and platform constraints.

Explanation

Correct Answer

A:

Because loop protection can prevent unsafe forwarding when control-plane information is missing, the best response is to inspect spanning-tree loop-protection events, root path and link state. A reviewer can close the technical case only after confirming that the corrected topology converges without opening an Ethernet loop.

Incorrect Answers

B:

The proposed principle concerns another network fault: A redundant alternate path can remain nonforwarding until a failure changes roles. Here, loop protection can prevent unsafe forwarding when control-plane information is missing. The most direct correction is to inspect spanning-tree loop-protection events, root path and link state, confirmed by the corrected topology converges without opening an Ethernet loop.

C:

That result would be useful for a different failure, namely: A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. The current case specifically calls for: Inspect spanning-tree loop-protection events, root path and link state. The required observed result is: The corrected topology converges without opening an Ethernet loop.

D:

This response would target a different source scenario: A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. It cannot establish the current acceptance requirement, which is: The corrected topology converges without opening an Ethernet loop. The relevant action is: Inspect spanning-tree loop-protection events, root path and link state.

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