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 34

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.

Question 331

An operator changes MED and sees no route change because the target AS prioritizes other attributes. Which combined repair and acceptance criterion is strongest?

  1. Repair: Check client definitions, route-reflector session state and export policy. Check: The missing client receives the correct next-hop-resolvable route.
  2. Change: Explain local label significance and neighbor label binding. Test: A path test records locally valid incoming and outgoing label mappings.
  3. Implement: Compare MED use with actual prior BGP decision attributes and neighbor policy. Verify: A captured received-path comparison explains which attribute selected the route.
  4. Control: Verify negotiated address families and family-specific routing tables. Accepted result: The intended inet6 family receives and selects the IPv6 prefix.

Explanation

Correct Answer

C:

The selected response implements the principle that mED is not guaranteed to override local policy or earlier attributes. The engineer should compare MED use with actual prior BGP decision attributes and neighbor policy. Successful confirmation means: A captured received-path comparison explains which attribute selected the route.

Incorrect Answers

A:

The alternative addresses a route reflector receives a new branch prefix but one iBGP client never learns it, not the present root cause. Here the selected correction must reflect mED is not guaranteed to override local policy or earlier attributes. Test for: A captured received-path comparison explains which attribute selected the route.

B:

This answer would be more suitable when an operator assumes MPLS labels are globally unique across the provider network, where the corrective action is to explain local label significance and neighbor label binding. The failure here is different: MED is not guaranteed to override local policy or earlier attributes. Required validation: A captured received-path comparison explains which attribute selected the route.

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 mED is not guaranteed to override local policy or earlier attributes. A correct remediation would compare MED use with actual prior BGP decision attributes and neighbor policy and demonstrate: A captured received-path comparison explains which attribute selected the route.

Question 332

A GRE tunnel is reachable from one routing instance but the remote customer route leaks into a different instance. Which technical explanation and controlled action address the symptom?

  1. Cause: Tunneling transport and customer route isolation are separate configurations. Response: Verify instance ownership and route policy at both tunnel endpoints.
  2. Diagnosis: GRE has no independent path if its outer transport becomes unreachable. Action: Restore underlay endpoint reachability and then validate the inner tunnel route.
  3. Explanation: A tunnel can carry inner packet types over an underlay forwarding only the outer header. Repair: Distinguish the inner routed payload from outer unicast encapsulation.
  4. Fault mechanism: Successful ordinary IP forwarding does not isolate MPLS packet forwarding faults. Remediation: Compare ingress label imposition with transit LFIB and egress disposition.

Explanation

Correct Answer

A:

This option addresses the stated case rather than another networking issue. Principle: Tunneling transport and customer route isolation are separate configurations. Remedy: Verify instance ownership and route policy at both tunnel endpoints. Proof: Traffic uses the tunnel in the intended customer routing instance only.

Incorrect Answers

B:

This response would target a different source scenario: A GRE tunnel over an IPv4 core stops passing traffic immediately after an underlay route withdraws. It cannot establish the current acceptance requirement, which is: Traffic uses the tunnel in the intended customer routing instance only. The relevant action is: Verify instance ownership and route policy at both tunnel endpoints.

C:

Distinguish the inner routed payload from outer unicast encapsulation is a relevant step for the separate scenario in which an operator sends a multicast routing-protocol packet over a GRE tunnel and assumes all physical transit routers must process the inner multicast. It does not directly fix this case. Instead verify instance ownership and route policy at both tunnel endpoints; verify: Traffic uses the tunnel in the intended customer routing instance only.

D:

The alternative addresses one branch reaches a PE over IP but fails when the same traffic is forwarded across the MPLS core, not the present root cause. Here the selected correction must reflect tunneling transport and customer route isolation are separate configurations. Test for: Traffic uses the tunnel in the intended customer routing instance only.

Question 333

A provider advertises a customer prefix with its own AS number already present in the return AS path. Which protocol behavior most directly determines the correct diagnosis?

  1. Protocol behavior: Disabling loop prevention can introduce persistent interdomain routing loops.
  2. Underlying principle: BGP AS-path information can prevent routes from looping into an AS.
  3. Root design issue: An Established BGP session can exist with zero accepted routes or unusable next hops.
  4. The governing rule is: Different segment types express different routing or link steering semantics.

Explanation

Correct Answer

B:

The case turns on the distinction that bGP AS-path information can prevent routes from looping into an AS. Apply this concrete engineering step: Investigate AS-path loop prevention rather than overriding it without risk review. An acceptable verification outcome is: The route is accepted only after the AS-path design is corrected.

Incorrect Answers

A:

This option overlooks the decisive condition. Its supporting principle is disabling loop prevention can introduce persistent interdomain routing loops, while this scenario depends on bGP AS-path information can prevent routes from looping into an AS. Verify the correction with: The route is accepted only after the AS-path design is corrected.

C:

The proposed principle concerns another network fault: An Established BGP session can exist with zero accepted routes or unusable next hops. Here, bGP AS-path information can prevent routes from looping into an AS. The most direct correction is to investigate AS-path loop prevention rather than overriding it without risk review, confirmed by the route is accepted only after the AS-path design is corrected.

D:

That result would be useful for a different failure, namely: A segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. The current case specifically calls for: Investigate AS-path loop prevention rather than overriding it without risk review. The required observed result is: The route is accepted only after the AS-path design is corrected.

Question 334

A customer advertises an unauthorized more-specific and the PE propagates it across the provider core. Which corrective action and confirmation pair is most appropriate?

  1. Implement: Review route-reflector client and cluster design, including loop-prevention attributes. Verify: A test prefix reaches permitted clients without cycling through reflector clusters.
  2. Control: Tighten customer import route filtering and test permitted prefix lengths. Accepted result: The unauthorized more-specific is rejected while approved aggregates remain.
  3. Action: Separate RSVP-signaled LSP functions from LDP label distribution. Evidence: The chosen protocol establishes the intended type of LSP.
  4. Repair: Inspect inet6 family negotiation, filters and IPv6 next-hop validity. Check: The expected IPv6 NLRI is received and becomes an eligible IPv6 route.

Explanation

Correct Answer

B:

This option addresses the stated case rather than another networking issue. Principle: BGP edge hygiene protects the routing domain from unauthorized reachability. Remedy: Tighten customer import route filtering and test permitted prefix lengths. Proof: The unauthorized more-specific is rejected while approved aggregates remain.

Incorrect Answers

A:

Review route-reflector client and cluster design, including loop-prevention attributes is a relevant step for the separate scenario in which a route reflector advertises routes to the wrong clients after a change in group membership. It does not directly fix this case. Instead tighten customer import route filtering and test permitted prefix lengths; verify: The unauthorized more-specific is rejected while approved aggregates remain.

C:

This answer would be more suitable when a network design assumes RSVP and LDP use identical path signaling and traffic engineering controls, where the corrective action is to separate RSVP-signaled LSP functions from LDP label distribution. The failure here is different: BGP edge hygiene protects the routing domain from unauthorized reachability. Required validation: The unauthorized more-specific is rejected while approved aggregates remain.

D:

This option overlooks the decisive condition. Its supporting principle is iPv4 BGP session liveness does not prove IPv6 family route exchange, while this scenario depends on bGP edge hygiene protects the routing domain from unauthorized reachability. Verify the correction with: The unauthorized more-specific is rejected while approved aggregates remain.

Question 335

Two routers exchange IS-IS Hellos but one rejects the neighbor during area validation. Which root-cause explanation and corrective action fit the case?

  1. Explanation: MED is not guaranteed to override local policy or earlier attributes. Repair: Compare MED use with actual prior BGP decision attributes and neighbor policy.
  2. Fault mechanism: Frequent topology churn can stem from physical and configuration issues rather than DIS alone. Remediation: Inspect link quality, interface settings and DIS state before forcing election behavior.
  3. Root issue: The designated system serves LAN pseudonode advertisement and election semantics. Correction: Review current DIS election rules for the network and protocol instance.
  4. Cause: Area mismatch can affect Level 1 adjacency even when packets are received. Response: Compare NET area addresses and intended L1 or L2 adjacency mode.

Explanation

Correct Answer

D:

Underlying cause: Area mismatch can affect Level 1 adjacency even when packets are received. Corrective action: compare NET area addresses and intended L1 or L2 adjacency mode. Verify the outcome: A protocol check shows the authorized level and matching adjacency.

Incorrect Answers

A:

The proposed principle concerns another network fault: MED is not guaranteed to override local policy or earlier attributes. Here, area mismatch can affect Level 1 adjacency even when packets are received. The most direct correction is to compare NET area addresses and intended L1 or L2 adjacency mode, confirmed by a protocol check shows the authorized level and matching adjacency.

B:

That result would be useful for a different failure, namely: An IS-IS LAN is unstable after a VLAN move and DIS changes accompany repeated adjacency loss. The current case specifically calls for: Compare NET area addresses and intended L1 or L2 adjacency mode. The required observed result is: A protocol check shows the authorized level and matching adjacency.

C:

This response would target a different source scenario: An IS-IS LAN elects a new DIS and the engineer assumes the result must preempt every existing elected node. It cannot establish the current acceptance requirement, which is: A protocol check shows the authorized level and matching adjacency. The relevant action is: Compare NET area addresses and intended L1 or L2 adjacency mode.

Question 336

An IS-IS neighbor appears only at Level 2 even though the design expects a Level 1 core segment. Which post-change observation most strongly confirms the correction?

  1. Verification result: The neighbor table shows the intended level and stable adjacency.
  2. Closeout evidence: A protocol check shows the authorized level and matching adjacency.
  3. Acceptance check: A captured received-path comparison explains which attribute selected the route.
  4. The test confirms that the intended Level 1 or Level 2 adjacency forms with the expected topology scope.

Explanation

Correct Answer

A:

This is the model-intended best choice because compatible IS-IS levels and area information determine available adjacency types. The targeted correction is to compare interface level settings and area configuration. Validate it by observing that the neighbor table shows the intended level and stable adjacency.

Incorrect Answers

B:

This option overlooks the decisive condition. Its supporting principle is area mismatch can affect Level 1 adjacency even when packets are received, while this scenario depends on compatible IS-IS levels and area information determine available adjacency types. Verify the correction with: The neighbor table shows the intended level and stable adjacency.

C:

MED is not guaranteed to override local policy or earlier attributes describes a neighboring protocol concern. In this case the controlling fact is compatible IS-IS levels and area information determine available adjacency types. A correct remediation would compare interface level settings and area configuration and demonstrate: The neighbor table shows the intended level and stable adjacency.

D:

The proposed principle concerns another network fault: IS-IS Level 1 adjacency formation depends on common area context. Here, compatible IS-IS levels and area information determine available adjacency types. The most direct correction is to compare interface level settings and area configuration, confirmed by the neighbor table shows the intended level and stable adjacency.

Question 337

A filter-based forwarding term matching one subscriber address also captures an overlapping shared services subnet. What observable result most directly verifies the intended configuration?

  1. Expected observation: The route is accepted only after the AS-path design is corrected.
  2. Verification result: Only the subscriber's approved traffic enters the alternate routing instance.
  3. Closeout evidence: The test demonstrates loop prevention without advertising false service reachability.
  4. Acceptance check: The generated prefix appears only when the required contributing route is active.

Explanation

Correct Answer

B:

The selected response implements the principle that overlapping address classification makes precise route-filter and policy terms essential. The engineer should tighten the filter match and verify the next-table lookup with explicit positive and negative examples. Successful confirmation means: Only the subscriber's approved traffic enters the alternate routing instance.

Incorrect Answers

A:

This response would target a different source scenario: A provider advertises a customer prefix with its own AS number already present in the return AS path. It cannot establish the current acceptance requirement, which is: Only the subscriber's approved traffic enters the alternate routing instance. The relevant action is: Tighten the filter match and verify the next-table lookup with explicit positive and negative examples.

C:

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 overlapping address classification makes precise route-filter and policy terms essential. Test for: Only the subscriber's approved traffic enters the alternate routing instance.

D:

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: Overlapping address classification makes precise route-filter and policy terms essential. Required validation: Only the subscriber's approved traffic enters the alternate routing instance.

Question 338

A segment routing node uses a prefix segment but the operator treats it as a local adjacency segment. What action-and-test pairing directly resolves the case?

  1. Control: Review martian-address treatment and justify any carefully scoped exception. Accepted result: The rejected address remains excluded or a documented narrowly scoped exception is applied.
  2. Action: Review reservation constraints and available resources rather than resetting all label sessions. Evidence: A compatible bandwidth or path choice allows the target RSVP LSP to establish.
  3. Repair: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. Check: A segment trace follows the desired prefix or explicit adjacency.
  4. Change: Inspect label-switched next-hop resolution separately from generic IP reachability. Test: The labeled service route resolves after the intended LSP is restored.

Explanation

Correct Answer

C:

Correct diagnosis: Different segment types express different routing or link steering semantics. The appropriate action is: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions. The follow-up evidence required is: A segment trace follows the desired prefix or explicit adjacency.

Incorrect Answers

A:

Address validity and martian filtering affect which route sources are considered acceptable describes a neighboring protocol concern. In this case the controlling fact is different segment types express different routing or link steering semantics. A correct remediation would distinguish prefix-based segment reachability from adjacency-specific forwarding instructions and demonstrate: A segment trace follows the desired prefix or explicit adjacency.

B:

The proposed principle concerns another network fault: RSVP LSP setup can fail resource or path constraints even with valid IP reachability. Here, different segment types express different routing or link steering semantics. The most direct correction is to distinguish prefix-based segment reachability from adjacency-specific forwarding instructions, confirmed by a segment trace follows the desired prefix or explicit adjacency.

D:

This response would target a different source scenario: A loopback loses its MPLS-resolvable route but ordinary IP routing to the loopback remains reachable. It cannot establish the current acceptance requirement, which is: A segment trace follows the desired prefix or explicit adjacency. The relevant action is: Distinguish prefix-based segment reachability from adjacency-specific forwarding instructions.

Question 339

A BGP export policy matches a community but no routes leave the peer after a group-level policy reorder. Which technical distinction best describes the observed symptom?

  1. The key distinction is: An LSP cannot follow an unavailable required hop.
  2. Protocol behavior: An Established BGP session can exist with zero accepted routes or unusable next hops.
  3. Underlying principle: MED is not guaranteed to override local policy or earlier attributes.
  4. Root design issue: Policy inheritance and term action order affect BGP route advertisement.

Explanation

Correct Answer

D:

The critical observation is: Policy inheritance and term action order affect BGP route advertisement. Correct it by taking this action: Inspect effective group and neighbor export policy evaluation order. Confirm the outcome with: A neighbor route view confirms the approved community-tagged routes are sent.

Incorrect Answers

A:

The alternative addresses an operator configured an explicit RSVP path through a link that is now administratively down, not the present root cause. Here the selected correction must reflect policy inheritance and term action order affect BGP route advertisement. Test for: A neighbor route view confirms the approved community-tagged routes are sent.

B:

This answer would be more suitable when an eBGP peer sends frequent KEEPALIVEs but the operator assumes this proves the best route is installed, where the corrective action is to separate session liveness from prefix acceptance and RIB installation. The failure here is different: Policy inheritance and term action order affect BGP route advertisement. Required validation: A neighbor route view confirms the approved community-tagged routes are sent.

C:

This option overlooks the decisive condition. Its supporting principle is mED is not guaranteed to override local policy or earlier attributes, while this scenario depends on policy inheritance and term action order affect BGP route advertisement. Verify the correction with: A neighbor route view confirms the approved community-tagged routes are sent.

Question 340

Several VLANs have unexpected root placement under VSTP after port membership changes. Which next action best resolves this observed routing or switching failure?

  1. Remediation: Validate the usable VLAN-ID range and reserved tag values.
  2. Recommended change: Apply suitable BPDU protection according to edge-port policy.
  3. Next step: Inspect interface faults and control-plane events before changing STP timers.
  4. Corrective action: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.

Explanation

Correct Answer

D:

Correct diagnosis: Per-VLAN spanning-tree behavior can differ across VLANs. The appropriate action is: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary. The follow-up evidence required is: Each tested VLAN elects its approved root and loop-free port roles.

Incorrect Answers

A:

That result would be useful for a different failure, namely: A customer requests VLAN 4096 as an ordinary 802.1Q customer VLAN without checking valid tag IDs. The current case specifically calls for: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary. The required observed result is: Each tested VLAN elects its approved root and loop-free port roles.

B:

This response would target a different source scenario: An edge port connected to a user device unexpectedly receives BPDUs from an unauthorized switch. It cannot establish the current acceptance requirement, which is: Each tested VLAN elects its approved root and loop-free port roles. The relevant action is: Inspect per-VLAN STP instances and configured priorities, not just a global STP summary.

C:

Inspect interface faults and control-plane events before changing STP timers is a relevant step for the separate scenario in which an RSTP uplink continues to flap between discarding and forwarding after an unstable fiber replacement. It does not directly fix this case. Instead inspect per-VLAN STP instances and configured priorities, not just a global STP summary; verify: Each tested VLAN elects its approved root and loop-free port roles.

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