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 75

Question 740

A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. What remediation is most directly applicable?

  1. Next step: Review martian-address treatment and justify any carefully scoped exception.
  2. Corrective action: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples.
  3. Apply this control: Restore the intended route preferences and check selected forwarding next hops.
  4. Remediation: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

Explanation

Correct Answer

B:

Because overlapping address classification makes precise route-filter and policy terms essential, the best response is to tighten the filter match and verify the next-table lookup with explicit positive and negative examples. A reviewer can close the technical case only after confirming that only the subscriber's approved traffic enters the alternate routing instance.

Incorrect Answers

A:

That result would be useful for a different failure, namely: An operator accepts a source-address block as an ordinary next-hop network even though the address is classified as martian. The current case specifically calls for: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples. The required observed result is: Only the subscriber's approved traffic enters the alternate routing instance.

C:

Restore the intended route preferences and check selected forwarding next hops is a relevant step for the separate scenario in which a backup path becomes primary after a preference edit even though the design called for failover only. It does not directly fix this case. Instead tighten the filter match and verify the next-table lookup with explicit positive and negative examples; verify: Only the subscriber's approved traffic enters the alternate routing instance.

D:

The alternative addresses an OSPF route appears longer than expected after failover because a backup link's cost was never verified, not the present root cause. Here the selected correction must reflect overlapping address classification makes precise route-filter and policy terms essential. Test for: Only the subscriber's approved traffic enters the alternate routing instance.

Question 741

An Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation. What is the most defensible network engineering correction?

  1. Recommended change: Verify the BPDU protection event and remove the unauthorized bridge rather than blindly disabling safeguards.
  2. Next step: Trace trunk authorization, bridge-domain membership and MAC learning across the path.
  3. Corrective action: Separate customer bridge domains and validate virtual-switch membership.
  4. Apply this control: Document VLAN-aware versus flexible tagging and unit classification requirements.

Explanation

Correct Answer

D:

The selected response implements the principle that logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. The engineer should document VLAN-aware versus flexible tagging and unit classification requirements. Successful confirmation means: Both test logical units classify tagged traffic into their intended bridge domains.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is protective edge-port shutdown is evidence of BPDU policy enforcement, while this scenario depends on logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. Verify the correction with: Both test logical units classify tagged traffic into their intended bridge domains.

B:

A working IRB gateway does not validate all L2 paths and trunk members describes a neighboring protocol concern. In this case the controlling fact is logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. A correct remediation would document VLAN-aware versus flexible tagging and unit classification requirements and demonstrate: Both test logical units classify tagged traffic into their intended bridge domains.

C:

The proposed principle concerns another network fault: Layer 2 isolation depends on bridge-domain and logical switch boundaries. Here, logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model. The most direct correction is to document VLAN-aware versus flexible tagging and unit classification requirements, confirmed by both test logical units classify tagged traffic into their intended bridge domains.

Question 742

A policy adjustment changes both routing preference and forwarding instance selection in one unreviewed commit. Which corrective action and confirmation pair is most appropriate?

  1. Change: Audit aggregate or generated-route contributors and policy conditions. Test: A loss-of-last-contributor test causes the intended summary behavior.
  2. Implement: Restore appropriate IGP next-hop reachability or approved next-hop-self behavior. Verify: The internal router resolves the next hop and installs the intended route.
  3. Control: Verify route contribution and the conditions for route generation. Accepted result: The generated prefix appears only when the required contributing route is active.
  4. Action: Separate route-selection and lookup-table changes and test each with candidate configuration. Evidence: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

Explanation

Correct Answer

D:

This is the model-intended best choice because small reversible route-policy changes simplify troubleshooting and rollback. The targeted correction is to separate route-selection and lookup-table changes and test each with candidate configuration. Validate it by observing that the rollback and candidate checks show the exact intended RIB and FIB outcomes.

Incorrect Answers

A:

Audit aggregate or generated-route contributors and policy conditions is a relevant step for the separate scenario in which an aggregated customer advertisement persists while all contributing specifics have withdrawn. It does not directly fix this case. Instead separate route-selection and lookup-table changes and test each with candidate configuration; verify: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

B:

The alternative addresses an iBGP route is hidden because the next hop learned from an edge router is unreachable inside the backbone, not the present root cause. Here the selected correction must reflect small reversible route-policy changes simplify troubleshooting and rollback. Test for: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

C:

This answer would be more suitable when a generated route is configured but its expected contributing route is absent from the routing table, where the corrective action is to verify route contribution and the conditions for route generation. The failure here is different: Small reversible route-policy changes simplify troubleshooting and rollback. Required validation: The rollback and candidate checks show the exact intended RIB and FIB outcomes.

Question 743

An OSPF route appears longer than expected after failover because a backup link's cost was never verified. Which next action best resolves this observed routing or switching failure?

  1. Apply this control: Check import destinations, next-hop resolution and effective routes in every receiving table.
  2. Remediation: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.
  3. Recommended change: Review each interface's OSPF metric and compare end-to-end computed costs.
  4. Next step: Review hierarchical OSPF backbone attachment and area border placement.

Explanation

Correct Answer

B:

The critical observation is: Failover paths are governed by their actual configured metrics. Correct it by taking this action: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs. Confirm the outcome with: When the primary fails the documented backup path is selected without loops.

Incorrect Answers

A:

The proposed principle concerns another network fault: Imported routes must be validated in the destination lookup context. Here, failover paths are governed by their actual configured metrics. The most direct correction is to confirm the explicit cost plan in a failure rehearsal using route and topology outputs, confirmed by when the primary fails the documented backup path is selected without loops.

C:

This response would target a different source scenario: OSPF route preference changes after a new link is added and a latency-sensitive service takes the wrong path. It cannot establish the current acceptance requirement, which is: When the primary fails the documented backup path is selected without loops. The relevant action is: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.

D:

Review hierarchical OSPF backbone attachment and area border placement is a relevant step for the separate scenario in which a router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. It does not directly fix this case. Instead confirm the explicit cost plan in a failure rehearsal using route and topology outputs; verify: When the primary fails the documented backup path is selected without loops.

Question 744

A provider assumes an ordinary IP destination lookup and an MPLS label lookup always use the same forwarding table. What remediation is most directly applicable?

  1. Corrective action: Distinguish aggregate reachability from specific-route forwarding and test loss of component routes.
  2. Apply this control: Distinguish IP RIB entries from label forwarding information and LSP resolution.
  3. Remediation: Review explicit-path or constraint-based RSVP traffic-engineering intent.
  4. Recommended change: Compare ingress label imposition with transit LFIB and egress disposition.

Explanation

Correct Answer

B:

Correct diagnosis: MPLS forwarding relies on label bindings and compatible next-hop state. The appropriate action is: Distinguish IP RIB entries from label forwarding information and LSP resolution. The follow-up evidence required is: The transit LSR selects an authorized outgoing label and interface.

Incorrect Answers

A:

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: MPLS forwarding relies on label bindings and compatible next-hop state. Required validation: The transit LSR selects an authorized outgoing label and interface.

C:

RSVP-TE path choice can account for configured topology constraints and resources describes a neighboring protocol concern. In this case the controlling fact is mPLS forwarding relies on label bindings and compatible next-hop state. A correct remediation would distinguish IP RIB entries from label forwarding information and LSP resolution and demonstrate: The transit LSR selects an authorized outgoing label and interface.

D:

The proposed principle concerns another network fault: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Here, mPLS forwarding relies on label bindings and compatible next-hop state. The most direct correction is to distinguish IP RIB entries from label forwarding information and LSP resolution, confirmed by the transit LSR selects an authorized outgoing label and interface.

Question 745

An IPv6 BGP route is accepted but cannot be forwarded because its next hop lacks neighbor resolution. What observable result most directly verifies the intended configuration?

  1. The test confirms that the IPv6 FIB resolves the intended next hop and a test packet crosses the link.
  2. Expected observation: The accepted OSPFv3 IPv6 routes become active in the expected routing table.
  3. Verification result: The route installs with the expected IPv6 next hop and packet delivery succeeds.
  4. Closeout evidence: Each direction's active route matches the documented costs and design.

Explanation

Correct Answer

C:

The critical observation is: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Correct it by taking this action: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path. Confirm the outcome with: The route installs with the expected IPv6 next hop and packet delivery succeeds.

Incorrect Answers

A:

This response would target a different source scenario: A router has an IPv6 default route but no usable next-hop reachability on the egress link. It cannot establish the current acceptance requirement, which is: The route installs with the expected IPv6 next hop and packet delivery succeeds. The relevant action is: Verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path.

B:

Check OSPFv3 family enablement, LSAs and routing-policy route acceptance is a relevant step for the separate scenario in which after enabling OSPFv3 a provider sees IPv6 neighbors but no remote IPv6 customer prefixes. It does not directly fix this case. Instead verify IPv6 next-hop reachability and Neighbor Discovery on the outgoing path; verify: The route installs with the expected IPv6 next hop and packet delivery succeeds.

D:

This answer would be more suitable when an IS-IS link has asymmetric traffic despite synchronized LSPs and the engineer assumes the LSDB itself is corrupted, where the corrective action is to compare path metrics and each router's route selection before altering LSP state. The failure here is different: An IPv6 BGP route requires a resolvable eligible next hop for forwarding. Required validation: The route installs with the expected IPv6 next hop and packet delivery succeeds.

Question 746

An engineer uses loop protection as if it served the same purpose as BPDU protection on every port. What is the primary routing or switching concept illustrated?

  1. The key distinction is: Spanning-tree security mechanisms protect distinct topology and control-plane risks.
  2. Protocol behavior: Spanning tree prevents forwarding loops by selecting a loop-free active topology.
  3. Underlying principle: Logical service segmentation requires the physical Ethernet encapsulation to match the intended tag model.
  4. Root design issue: Configuration intent must be verified against the actual elected spanning-tree root.

Explanation

Correct Answer

A:

Because spanning-tree security mechanisms protect distinct topology and control-plane risks, the best response is to match loop, BPDU and root protection to their different fault conditions. A reviewer can close the technical case only after confirming that separate fault injections trigger the intended protection per port role.

Incorrect Answers

B:

The proposed principle concerns another network fault: Spanning tree prevents forwarding loops by selecting a loop-free active topology. Here, spanning-tree security mechanisms protect distinct topology and control-plane risks. The most direct correction is to match loop, BPDU and root protection to their different fault conditions, confirmed by separate fault injections trigger the intended protection per port role.

C:

That result would be useful for a different failure, namely: An Ethernet access design has multiple logical units using one physical port without specifying frame encapsulation. The current case specifically calls for: Match loop, BPDU and root protection to their different fault conditions. The required observed result is: Separate fault injections trigger the intended protection per port role.

D:

This response would target a different source scenario: A planned root bridge migration is configured but the operational root remains on the old switch. It cannot establish the current acceptance requirement, which is: Separate fault injections trigger the intended protection per port role. The relevant action is: Match loop, BPDU and root protection to their different fault conditions.

Question 747

An IS-IS backbone forms an adjacency but omits IPv6 reachability when the family is not enabled. Which root-cause explanation and corrective action fit the case?

  1. Explanation: IS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Repair: Enable and verify the intended IPv6 address-family reachability advertisements.
  2. Fault mechanism: The IS-IS DIS concept applies to LANs rather than ordinary point-to-point links. Remediation: Differentiate multiaccess DIS election from point-to-point adjacency behavior.
  3. Root issue: Intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets. Correction: Review IPv6 path MTU discovery and endpoint fragmentation requirements.
  4. Cause: Neighbor establishment is distinct from prefix advertisement and installation. Response: Check OSPFv3 family enablement, LSAs and routing-policy route acceptance.

Explanation

Correct Answer

A:

The case turns on the distinction that iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Apply this concrete engineering step: Enable and verify the intended IPv6 address-family reachability advertisements. An acceptable verification outcome is: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

Incorrect Answers

B:

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: IS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Required validation: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

C:

This option overlooks the decisive condition. Its supporting principle is intermediate IPv6 routers do not perform ordinary IPv4-style fragmentation of transit packets, while this scenario depends on iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. Verify the correction with: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

D:

Neighbor establishment is distinct from prefix advertisement and installation describes a neighboring protocol concern. In this case the controlling fact is iS-IS adjacency and IPv6 prefix exchange are separate operational concerns. A correct remediation would enable and verify the intended IPv6 address-family reachability advertisements and demonstrate: IPv6 destination prefixes become visible without disturbing stable IS-IS neighbors.

Question 748

Two static routes for the same prefix have unequal preferences and the operator expects both paths to share traffic. Which root-cause explanation and corrective action fit the case?

  1. Diagnosis: Overlapping address classification makes precise route-filter and policy terms essential. Action: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples.
  2. Explanation: Interarea reachability depends on the ABR's view and allowed advertisements. Repair: Inspect ABR area configuration, route export rules and summary policy.
  3. Fault mechanism: Route preference determines the selected route before any multipath decision. Remediation: Review route preference before considering equivalent forwarding paths.
  4. 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.

Explanation

Correct Answer

C:

This is the model-intended best choice because route preference determines the selected route before any multipath decision. The targeted correction is to review route preference before considering equivalent forwarding paths. Validate it by observing that the selected path and its preference match the intended backup policy.

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: Review route preference before considering equivalent forwarding paths. The required observed result is: The selected path and its preference match the intended backup policy.

B:

This response would target a different source scenario: An area border router stops advertising an expected summarized interarea route after a policy change. It cannot establish the current acceptance requirement, which is: The selected path and its preference match the intended backup policy. The relevant action is: Review route preference before considering equivalent forwarding paths.

D:

The alternative addresses a summary route is advertised even though the operator expects every more-specific customer route to remain reachable, not the present root cause. Here the selected correction must reflect route preference determines the selected route before any multipath decision. Test for: The selected path and its preference match the intended backup policy.

Question 749

A customer overlay fails across an MPLS core only for one service label. What should the operations engineer do first to address the stated fault?

  1. Corrective action: Inspect outer transport and inner service label handling separately.
  2. Apply this control: Review explicit-path or constraint-based RSVP traffic-engineering intent.
  3. Remediation: Inspect inet6 family negotiation, filters and IPv6 next-hop validity.
  4. Recommended change: Restore the required transport route and inspect label-signaling and next-hop state.

Explanation

Correct Answer

A:

The critical observation is: A healthy transport LSP does not guarantee a correct overlay label mapping. Correct it by taking this action: Inspect outer transport and inner service label handling separately. Confirm the outcome with: The test service label is retained and accepted at the target PE.

Incorrect Answers

B:

RSVP-TE path choice can account for configured topology constraints and resources describes a neighboring protocol concern. In this case the controlling fact is a healthy transport LSP does not guarantee a correct overlay label mapping. A correct remediation would inspect outer transport and inner service label handling separately and demonstrate: The test service label is retained and accepted at the target PE.

C:

The proposed principle concerns another network fault: IPv4 BGP session liveness does not prove IPv6 family route exchange. Here, a healthy transport LSP does not guarantee a correct overlay label mapping. The most direct correction is to inspect outer transport and inner service label handling separately, confirmed by the test service label is retained and accepted at the target PE.

D:

That result would be useful for a different failure, namely: A route policy makes a transport prefix unavailable to the MPLS forwarding context while preserving customer IP routes. The current case specifically calls for: Inspect outer transport and inner service label handling separately. The required observed result is: The test service label is retained and accepted at the target PE.

Question 750

A router in a nonbackbone area cannot reach a newly connected area through a topology that skips Area 0. Which change best corrects the failure without losing the intended design?

  1. Next step: Confirm the explicit cost plan in a failure rehearsal using route and topology outputs.
  2. Corrective action: Place the correct L1/L2 boundary and evaluate flooding scope.
  3. Apply this control: Review hierarchical OSPF backbone attachment and area border placement.
  4. Remediation: Check the expected DR/BDR versus DROther neighbor-state relationships.

Explanation

Correct Answer

C:

Because multi-area OSPF design requires attention to backbone connectivity, the best response is to review hierarchical OSPF backbone attachment and area border placement. A reviewer can close the technical case only after confirming that the planned ABR topology provides verified interarea reachability.

Incorrect Answers

A:

Confirm the explicit cost plan in a failure rehearsal using route and topology outputs is a relevant step for the separate scenario in which an OSPF route appears longer than expected after failover because a backup link's cost was never verified. It does not directly fix this case. Instead review hierarchical OSPF backbone attachment and area border placement; verify: The planned ABR topology provides verified interarea reachability.

B:

The alternative addresses a provider uses a Level 1-only router to interconnect two independent IS-IS areas and expects unrestricted cross-area flooding, not the present root cause. Here the selected correction must reflect multi-area OSPF design requires attention to backbone connectivity. Test for: The planned ABR topology provides verified interarea reachability.

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 multi-area OSPF design requires attention to backbone connectivity. Verify the correction with: The planned ABR topology provides verified interarea reachability.

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