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 33

Question 320

A route appears in the routing table but an engineer assumes its presence proves it was installed into the forwarding table. What is the most defensible network engineering correction?

  1. Remediation: Validate forwarding load-sharing configuration and run representative multi-flow traffic.
  2. Recommended change: Constrain redistribution and test route policy acceptance for the intended prefixes.
  3. Next step: Review filter-based forwarding classification and the intended next-table selection.
  4. Corrective action: Compare RIB selection with forwarding-table installation and next-hop resolution.

Explanation

Correct Answer

D:

Because control-plane route visibility and installed forwarding state are distinct evidence, the best response is to compare RIB selection with forwarding-table installation and next-hop resolution. A reviewer can close the technical case only after confirming that the forwarding entry uses the correct next hop for the active route.

Incorrect Answers

A:

This answer would be more suitable when an equal-cost path test sends nearly all flows across one member while both links remain operational, where the corrective action is to validate forwarding load-sharing configuration and run representative multi-flow traffic. 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.

B:

This option overlooks the decisive condition. Its supporting principle is routing policy controls which external reachability is injected into OSPF, while this scenario depends on control-plane route visibility and installed forwarding state are distinct evidence. Verify the correction with: The forwarding entry uses the correct next hop for the active route.

C:

Policy-based forwarding can select a routing table independently of the destination lookup in the ingress default table 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.

Question 321

A GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws. Which technical explanation and controlled action address the symptom?

  1. Diagnosis: Label stack changes can be legitimate parts of LSP forwarding design. Action: Verify whether PHP or explicit-null behavior is configured and intended.
  2. Explanation: GRE has no independent path if its outer transport becomes unreachable. Repair: Restore underlay endpoint reachability and then validate the inner tunnel route.
  3. Fault mechanism: Tunneling transport and customer route isolation are separate configurations. Remediation: Verify instance ownership and route policy at both tunnel endpoints.
  4. Root issue: Encapsulation reduces effective payload MTU unless transport accommodates the extra headers. Correction: Account for outer IP and GRE header overhead in the MTU design.

Explanation

Correct Answer

B:

The selected response implements the principle that gRE has no independent path if its outer transport becomes unreachable. The engineer should restore underlay endpoint reachability and then validate the inner tunnel route. Successful confirmation means: Both outer endpoint probes and inner traffic succeed after repair.

Incorrect Answers

A:

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: Both outer endpoint probes and inner traffic succeed after repair. The relevant action is: Restore underlay endpoint reachability and then validate the inner tunnel route.

C:

The alternative addresses a GRE tunnel is reachable from one routing instance but the remote customer route leaks into a different instance, not the present root cause. Here the selected correction must reflect gRE has no independent path if its outer transport becomes unreachable. Test for: Both outer endpoint probes and inner traffic succeed after repair.

D:

This answer would be more suitable when an engineer expects a GRE tunnel to preserve the same maximum payload size as a native Ethernet path, where the corrective action is to account for outer IP and GRE header overhead in the MTU design. The failure here is different: GRE has no independent path if its outer transport becomes unreachable. Required validation: Both outer endpoint probes and inner traffic succeed after repair.

Question 322

A generated route is configured but its expected contributing route is absent from the routing table. What observable result most directly verifies the intended configuration?

  1. Expected observation: The static route becomes active after the actual next-hop fault is corrected.
  2. Verification result: The generated prefix appears only when the required contributing route is active.
  3. Closeout evidence: The summary is advertised only under the approved component-route conditions.
  4. Acceptance check: The internal peer has a valid route to the BGP next hop and installs the prefix.

Explanation

Correct Answer

B:

This is the model-intended best choice because a generated route depends on its contributing-route conditions rather than mere configuration presence. The targeted correction is to verify route contribution and the conditions for route generation. Validate it by observing that the generated prefix appears only when the required contributing route is active.

Incorrect Answers

A:

Operational route troubleshooting starts with active state and resolution evidence describes a neighboring protocol concern. In this case the controlling fact is a generated route depends on its contributing-route conditions rather than mere configuration presence. A correct remediation would verify route contribution and the conditions for route generation and demonstrate: The generated prefix appears only when the required contributing route is active.

C:

That result would be useful for a different failure, namely: A summary route is advertised even though the operator expects every more-specific customer route to remain reachable. The current case specifically calls for: Verify route contribution and the conditions for route generation. The required observed result is: The generated prefix appears only when the required contributing route is active.

D:

This response would target a different source scenario: A provider's iBGP peer receives a route but cannot resolve the external next hop in its own IGP. It cannot establish the current acceptance requirement, which is: The generated prefix appears only when the required contributing route is active. The relevant action is: Verify route contribution and the conditions for route generation.

Question 323

An equal-cost path test sends nearly all flows across one member while both links remain operational. Which next action best resolves this observed routing or switching failure?

  1. Next step: Review martian-address treatment and justify any carefully scoped exception.
  2. Corrective action: Validate forwarding load-sharing configuration and run representative multi-flow traffic.
  3. Apply this control: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route.
  4. Remediation: Constrain redistribution and test route policy acceptance for the intended prefixes.

Explanation

Correct Answer

B:

Underlying cause: Load sharing should be evaluated with relevant flows rather than one ping stream. Corrective action: validate forwarding load-sharing configuration and run representative multi-flow traffic. Verify the outcome: A documented multi-flow test matches the configured distribution policy.

Incorrect Answers

A:

The alternative addresses an operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian, not the present root cause. Here the selected correction must reflect load sharing should be evaluated with relevant flows rather than one ping stream. Test for: A documented multi-flow test matches the configured distribution policy.

C:

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 load sharing should be evaluated with relevant flows rather than one ping stream. Verify the correction with: A documented multi-flow test matches the configured distribution policy.

D:

Routing policy controls which external reachability is injected into OSPF describes a neighboring protocol concern. In this case the controlling fact is load sharing should be evaluated with relevant flows rather than one ping stream. A correct remediation would validate forwarding load-sharing configuration and run representative multi-flow traffic and demonstrate: A documented multi-flow test matches the configured distribution policy.

Question 324

Two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP. Which evidence would justify closing this troubleshooting case?

  1. Acceptance check: A packet capture shows the intended outer and inner VLAN tags end to end.
  2. The test confirms that the approved endpoint reconnects without unexpected BPDUs and protection stays enabled.
  3. Expected observation: A controlled BPDU causes the expected protected-port response.
  4. Verification result: A link-failure test shows the supported rapid role transition.

Explanation

Correct Answer

D:

Correct diagnosis: RSTP can converge faster using explicit roles and handshakes where conditions allow. The appropriate action is: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. The follow-up evidence required is: A link-failure test shows the supported rapid role transition.

Incorrect Answers

A:

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: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. The required observed result is: A link-failure test shows the supported rapid role transition.

B:

This response would target a different source scenario: A customer plugs a small unmanaged switch into a protected edge port and the port disables as soon as BPDUs arrive. It cannot establish the current acceptance requirement, which is: 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:

Apply suitable BPDU protection according to edge-port policy is a relevant step for the separate scenario in which an edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. It does not directly fix this case. Instead compare the rapid proposal/agreement behavior with traditional timer-dependent transitions; verify: A link-failure test shows the supported rapid role transition.

Question 325

A service provider tags prefixes for selective export but applies the community-match policy to the wrong neighbor group. Which change best corrects the failure without losing the intended design?

  1. Remediation: Map inbound and outbound policy points and confirm the intended communities.
  2. Recommended change: Collect hop-local LFIB, label forwarding and interface counters along the LSP.
  3. Next step: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.
  4. Corrective action: Evaluate routing-policy local preference before later BGP path-selection attributes.

Explanation

Correct Answer

A:

The critical observation is: BGP group inheritance and policy direction govern which advertisements are modified. Correct it by taking this action: Map inbound and outbound policy points and confirm the intended communities. Confirm the outcome with: A neighbor advertising test shows precisely the allowed tagged prefixes.

Incorrect Answers

B:

End-to-end signaling state alone cannot pinpoint a data-plane label failure describes a neighboring protocol concern. In this case the controlling fact is bGP group inheritance and policy direction govern which advertisements are modified. A correct remediation would map inbound and outbound policy points and confirm the intended communities and demonstrate: A neighbor advertising test shows precisely the allowed tagged prefixes.

C:

The proposed principle concerns another network fault: IPv4 BGP session liveness does not prove IPv6 family route exchange. Here, bGP group inheritance and policy direction govern which advertisements are modified. The most direct correction is to map inbound and outbound policy points and confirm the intended communities, confirmed by a neighbor advertising test shows precisely the allowed tagged prefixes.

D:

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: Map inbound and outbound policy points and confirm the intended communities. The required observed result is: A neighbor advertising test shows precisely the allowed tagged prefixes.

Question 326

A site sees different OSPF routes after a topology edit and declares the protocol failed without checking LSDB consistency. A reviewer requires a remedy and concrete test evidence. Which pairing fits?

  1. Repair: Inspect link-state databases and SPF output on affected routers. Check: A shared stable topology produces consistent path computation.
  2. Change: Compare withdrawal and blackhole behavior under a lab failure before changing the safety route. Test: The test demonstrates loop prevention without advertising false service reachability.
  3. Implement: Check MTU and interface compatibility and inspect neighbor-state details. Verify: The adjacency advances through database synchronization to Full.
  4. Control: Check the expected DR/BDR versus DROther neighbor-state relationships. Accepted result: The neighbor states match expected DR roles and routing converges.

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 engineer deletes an aggregate discard without first checking whether it prevents a transient routing loop, 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 an OSPF trace shows Hellos received but database synchronization stalls at ExStart or Exchange, where the corrective action is to check MTU and interface compatibility and inspect neighbor-state details. 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 broadcast topology reduces unnecessary full adjacency mesh formation, 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 327

A BFD session flaps during Routing Engine switchover after aggressive timer tuning. Which test result would best confirm a successful fix?

  1. Expected observation: A tested switchover maintains the required liveness behavior without false failure.
  2. Verification result: The fault is visible and surviving members carry traffic within the approved limits.
  3. Closeout evidence: Separate fault injections trigger the intended protection per port role.
  4. Acceptance check: Only the intended master forwards for the virtual gateway under steady state.

Explanation

Correct Answer

A:

The selected response implements the principle that bFD HA behavior depends on platform processing placement and timer tolerances. The engineer should review session type, supported distributed behavior and switchover-appropriate intervals. Successful confirmation means: A tested switchover maintains the required liveness behavior without false failure.

Incorrect Answers

B:

That result would be useful for a different failure, namely: One LAG member fails silently and the service loses capacity even though the logical interface remains active. The current case specifically calls for: Review session type, supported distributed behavior and switchover-appropriate intervals. The required observed result is: A tested switchover maintains the required liveness behavior without false failure.

C:

This response would target a different source scenario: An engineer uses loop protection as if it served the same purpose as BPDU protection on every port. It cannot establish the current acceptance requirement, which is: A tested switchover maintains the required liveness behavior without false failure. The relevant action is: Review session type, supported distributed behavior and switchover-appropriate intervals.

D:

Review VRRP virtual router roles, priority and failover behavior is a relevant step for the separate scenario in which two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan. It does not directly fix this case. Instead review session type, supported distributed behavior and switchover-appropriate intervals; verify: A tested switchover maintains the required liveness behavior without false failure.

Question 328

An RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. Which post-change observation most strongly confirms the correction?

  1. The test confirms that a link-failure test shows the supported rapid role transition.
  2. Expected observation: Only the intended master forwards for the virtual gateway under steady state.
  3. Verification result: Each tested VLAN elects its approved root and loop-free port roles.
  4. Closeout evidence: After fiber repair the port converges and remains in a stable role.

Explanation

Correct Answer

D:

Because sTP instability can be secondary to physical link churn, the best response is to inspect interface faults and control-plane events before changing STP timers. A reviewer can close the technical case only after confirming that after fiber repair the port converges and remains in a stable role.

Incorrect Answers

A:

This answer would be more suitable when two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP, where the corrective action is to compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. The failure here is different: STP instability can be secondary to physical link churn. Required validation: After fiber repair the port converges and remains in a stable role.

B:

This option overlooks the decisive condition. Its supporting principle is vRRP provides a master and backup mechanism for a shared virtual default gateway, while this scenario depends on sTP instability can be secondary to physical link churn. Verify the correction with: After fiber repair the port converges and remains in a stable role.

C:

Per-VLAN spanning-tree behavior can differ across VLANs describes a neighboring protocol concern. In this case the controlling fact is sTP instability can be secondary to physical link churn. A correct remediation would inspect interface faults and control-plane events before changing STP timers and demonstrate: After fiber repair the port converges and remains in a stable role.

Question 329

A provider tries to enable nonstop active routing and graceful-restart mode simultaneously on the same Junos device. What action-and-test pairing directly resolves the case?

  1. Implement: Remove the incompatible local mode and validate the supported HA configuration. Verify: The corrected candidate commits and the Routing Engine synchronization check passes.
  2. Control: Review supported mutual exclusivity and select the intended HA control-plane method. Accepted result: The configuration commits with an approved supported HA combination.
  3. Action: Review VRRP virtual router roles, priority and failover behavior. Evidence: Only the intended master forwards for the virtual gateway under steady state.
  4. Repair: Compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. Check: A link-failure test shows the supported rapid role transition.

Explanation

Correct Answer

B:

The selected response implements the principle that nSR and graceful restart on the local restarting device are different approaches and can conflict. The engineer should review supported mutual exclusivity and select the intended HA control-plane method. Successful confirmation means: The configuration commits with an approved supported HA combination.

Incorrect Answers

A:

This response would target a different source scenario: An NSR configuration fails commit after an operator adds graceful restart on the same device. It cannot establish the current acceptance requirement, which is: The configuration commits with an approved supported HA combination. The relevant action is: Review supported mutual exclusivity and select the intended HA control-plane method.

C:

The alternative addresses two edge routers advertise one gateway service and an engineer expects both to be virtual master without a redundancy plan, not the present root cause. Here the selected correction must reflect nSR and graceful restart on the local restarting device are different approaches and can conflict. Test for: The configuration commits with an approved supported HA combination.

D:

This answer would be more suitable when two switches have compatible STP but an engineer expects RSTP to use identical convergence procedures as legacy STP, where the corrective action is to compare the rapid proposal/agreement behavior with traditional timer-dependent transitions. The failure here is different: NSR and graceful restart on the local restarting device are different approaches and can conflict. Required validation: The configuration commits with an approved supported HA combination.

Question 330

A provider exports an unexpectedly broad set of routes into OSPF after accepting a generic routing policy. Which technical distinction best describes the observed symptom?

  1. The governing rule is: Passive OSPF interfaces can advertise networks without forming neighbors on that interface.
  2. The key distinction is: Address validity and martian filtering affect which route sources are considered acceptable.
  3. Protocol behavior: Routing policy controls which external reachability is injected into OSPF.
  4. Underlying principle: OSPF route type and LSA scope depend on where routing information originates.

Explanation

Correct Answer

C:

Correct diagnosis: Routing policy controls which external reachability is injected into OSPF. The appropriate action is: Constrain redistribution and test route policy acceptance for the intended prefixes. The follow-up evidence required is: Only approved external prefixes appear in the OSPF domain.

Incorrect Answers

A:

Passive OSPF interfaces can advertise networks without forming neighbors on that interface describes a neighboring protocol concern. In this case the controlling fact is routing policy controls which external reachability is injected into OSPF. A correct remediation would constrain redistribution and test route policy acceptance for the intended prefixes and demonstrate: Only approved external prefixes appear in the OSPF domain.

B:

The proposed principle concerns another network fault: Address validity and martian filtering affect which route sources are considered acceptable. Here, routing policy controls which external reachability is injected into OSPF. The most direct correction is to constrain redistribution and test route policy acceptance for the intended prefixes, confirmed by only approved external prefixes appear in the OSPF domain.

D:

This response would target a different source scenario: A link-state database shows intra-area information but a site expects external routes from an unconfigured redistribution policy. It cannot establish the current acceptance requirement, which is: Only approved external prefixes appear in the OSPF domain. The relevant action is: Constrain redistribution and test route policy acceptance for the intended prefixes.

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