McAfee Secured

Exam Code: JN0-364

Exam Name: Service Provider Routing and Switching, Specialist (JNCIS-SP)

Certification Provider: Juniper

100% Juniper JN0-364 Guaranteed Success With Testking Training Materials

Get Real JN0-364 Exam Questions & Expert Verified Answers as Experienced on the Real Exam!

69 Questions & Answers with Testing Engine

"Service Provider Routing and Switching, Specialist (JNCIS-SP) Exam", also known as JN0-364 exam, is a Juniper certification exam.

Pass your tests with the always up-to-date JN0-364 Exam Engine. Your JN0-364 training materials keep you at the head of the pack!

Satisfaction Guaranteed

Money Back Guarantee

Testking provides hassle-free money back guarantee with our products. That is because we have 100% trust in the abilities of our professional and experience product team, and our record is a proof of that.

99.6% PASS RATE
Was: $137.49
Now: $124.99

Juniper JN0-364 Practice Test 41

Question 400

In a separate fictional JNCIS-SP lab review for Glenwood Connectivity 100, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset. What is the direct residual network risk if the fault remains unresolved?

  1. Outbound traffic takes an expensive or congested transit link.
  2. Attempts to fix policy distract from a network reachability failure.
  3. Undetected route oscillation harms network stability.
  4. Packets cannot reach the intended next hop despite a syntactically valid address.

Explanation

Correct Answer

A:

Outbound traffic takes an expensive or congested transit link. Restore deliberate local-preference assignment and check selected egress paths. Higher BGP LOCAL_PREF is favored among otherwise eligible paths within an AS.

Incorrect Answers

B:

Attempts to fix policy distract from a network reachability failure. It is useful for situations where a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable; the reported fault, though, is that a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

C:

Undetected route oscillation harms network stability. That relates to circumstances in which a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored. Here the problem is that a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

D:

Packets cannot reach the intended next hop despite a syntactically valid address. This addresses a situation in which an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design; however, a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset.

Question 401

At fictional Hillside Transit 101, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Which targeted remediation best fits the reported behavior?

  1. Correct the import policy term to reject the unauthorized route while preserving contracted prefixes.
  2. Confirm MED comparison applicability and use a suitable local outbound policy if needed.
  3. Review planned OSPF costs in both directions and correct the traffic-engineering values.
  4. Inspect AS path and applicable policy before changing unrelated preference settings.

Explanation

Correct Answer

D:

Inspect AS path and applicable policy before changing unrelated preference settings. BGP AS path information supports loop avoidance and participates in route selection. The suspect path is explained and only eligible loop-free routes are selected.

Incorrect Answers

A:

Correct the import policy term to reject the unauthorized route while preserving contracted prefixes. This could help if a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy, but not when an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

B:

Confirm MED comparison applicability and use a suitable local outbound policy if needed. This relates to a case where a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems; the current situation is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

C:

Review planned OSPF costs in both directions and correct the traffic-engineering values. It is useful for situations where provider traffic takes a long backup path because OSPF interface costs were changed inconsistently; the reported fault, though, is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 402

At fictional Hillside Transit 101, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Why is this particular correction the best fit for the stated defect?

  1. BGP AS path information supports loop avoidance and participates in route selection.
  2. Route reflectors distribute selected IBGP reachability within the configured client topology.
  3. BGP depends on working IP transport to establish its TCP session.
  4. IS-IS elects a designated intermediate system on broadcast networks to manage pseudonode representation.

Explanation

Correct Answer

A:

BGP AS path information supports loop avoidance and participates in route selection. Inspect AS path and applicable policy before changing unrelated preference settings. The suspect path is explained and only eligible loop-free routes are selected.

Incorrect Answers

B:

Route reflectors distribute selected IBGP reachability within the configured client topology. This could help if an internal client learns routes from another client only intermittently after the route-reflector peering address changes, but not when an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

C:

BGP depends on working IP transport to establish its TCP session. This relates to a case where a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable; the current situation is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

D:

IS-IS elects a designated intermediate system on broadcast networks to manage pseudonode representation. It is useful for situations where operators see two possible LAN-designated routers and assume the wrong one leads routing for the shared segment; the reported fault, though, is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 403

At fictional Hillside Transit 101, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. What direct observation would prove the corrective action worked?

  1. Route detail shows intended local preference values and traffic exits through the designated link.
  2. The suspect path is explained and only eligible loop-free routes are selected.
  3. Tagged prefixes receive the documented policy action and untagged routes are unaffected.
  4. The observed TLV maps to the expected reachability entry without false parser alarms.

Explanation

Correct Answer

B:

The suspect path is explained and only eligible loop-free routes are selected. BGP AS path information supports loop avoidance and participates in route selection. Inspect AS path and applicable policy before changing unrelated preference settings.

Incorrect Answers

A:

Route detail shows intended local preference values and traffic exits through the designated link. This is applicable when a customer AS should prefer a primary exit but its IBGP paths have the same local preference after a policy reset; the present condition is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

C:

Tagged prefixes receive the documented policy action and untagged routes are unaffected. This could help if an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning, but not when an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

D:

The observed TLV maps to the expected reachability entry without false parser alarms. This relates to a case where a monitoring parser treats a valid IS-IS reachability TLV as an unsupported fault and pages the operations team; the current situation is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 404

At fictional Hillside Transit 101, a regional service-provider network, during a planned PE-to-core handoff, operations observes: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Which failure consequence follows most closely from ignoring this issue?

  1. IPv6 customers lose external paths despite healthy IPv4 peering.
  2. A route loop or false path preference persists due to misdiagnosis.
  3. Attempts to fix policy distract from a network reachability failure.
  4. GRE packets are discarded by a transit filter despite valid inner routes.

Explanation

Correct Answer

B:

A route loop or false path preference persists due to misdiagnosis. BGP AS path information supports loop avoidance and participates in route selection. Inspect AS path and applicable policy before changing unrelated preference settings.

Incorrect Answers

A:

IPv6 customers lose external paths despite healthy IPv4 peering. That could help when an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled; here, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

C:

Attempts to fix policy distract from a network reachability failure. It is relevant if a BGP peer has a correct AS number but cannot connect because its TCP transport address is unreachable, but the reported issue is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

D:

GRE packets are discarded by a transit filter despite valid inner routes. This could help if a GRE tunnel appears operational in configuration but sources packets from an interface not permitted by the core ACL, but not when an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 405

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 102, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. What intervention most directly restores the intended routing or switching behavior?

  1. Configure the appropriate BGP IPv6 family on the peers and confirm route exchange.
  2. Add an explicit approved community match and verify the intended import or export action.
  3. Inspect AS path and applicable policy before changing unrelated preference settings.
  4. Correct the QinQ service tag mapping and verify the inner customer tag remains intact.

Explanation

Correct Answer

C:

Inspect AS path and applicable policy before changing unrelated preference settings. The suspect path is explained and only eligible loop-free routes are selected. BGP AS path information supports loop avoidance and participates in route selection.

Incorrect Answers

A:

Configure the appropriate BGP IPv6 family on the peers and confirm route exchange. This could matter when an IPv6 BGP session establishes at TCP level but does not exchange IPv6 reachability because the address family was not enabled. In this case, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

B:

Add an explicit approved community match and verify the intended import or export action. That could help when an upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning; here, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

D:

Correct the QinQ service tag mapping and verify the inner customer tag remains intact. It is relevant if provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag, but the reported issue is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 406

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 102, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Which networking principle explains why the proposed correction is appropriate?

  1. BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent.
  2. BGP AS path information supports loop avoidance and participates in route selection.
  3. An established BGP session does not by itself establish which received path will be preferred.
  4. OSPF topological information must be refreshed and synchronized to remain valid.

Explanation

Correct Answer

B:

BGP AS path information supports loop avoidance and participates in route selection. The suspect path is explained and only eligible loop-free routes are selected. Inspect AS path and applicable policy before changing unrelated preference settings.

Incorrect Answers

A:

BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent. It addresses a different problem: A network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems. Here, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

C:

An established BGP session does not by itself establish which received path will be preferred. That could help when a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; here, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

D:

OSPF topological information must be refreshed and synchronized to remain valid. This is applicable when an OSPF route vanishes intermittently because a neighbor cannot refresh topology information after repeated link resets; the present condition is that an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 407

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 102, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. Which validation result would confirm the design is now functioning?

  1. The suspect path is explained and only eligible loop-free routes are selected.
  2. Tagged prefixes receive the documented policy action and untagged routes are unaffected.
  3. The expected customer prefix appears in the advertised-route output and unintended prefixes do not.
  4. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances.

Explanation

Correct Answer

A:

The suspect path is explained and only eligible loop-free routes are selected. Inspect AS path and applicable policy before changing unrelated preference settings. BGP AS path information supports loop avoidance and participates in route selection.

Incorrect Answers

B:

Tagged prefixes receive the documented policy action and untagged routes are unaffected. It addresses a different problem: An upstream advertises a community tag to influence treatment but an import policy ignores the agreed meaning. Here, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

C:

The expected customer prefix appears in the advertised-route output and unintended prefixes do not. This could matter when a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. In this case, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

D:

The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. That could help when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; here, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 408

In a separate fictional JNCIS-SP lab review for Westbridge Exchange 102, a carrier-edge and core routing team, following an audit of service-provider handoff behavior, engineers find: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path. What likely service impact does this condition create?

  1. A route loop or false path preference persists due to misdiagnosis.
  2. Remote networks cannot reach the customer or a broad policy leaks infrastructure routes.
  3. Policy and reachability behavior is distorted by a false external session.
  4. Healthy MPLS transport is disrupted by a false fault diagnosis.

Explanation

Correct Answer

A:

A route loop or false path preference persists due to misdiagnosis. Inspect AS path and applicable policy before changing unrelated preference settings. BGP AS path information supports loop avoidance and participates in route selection.

Incorrect Answers

B:

Remote networks cannot reach the customer or a broad policy leaks infrastructure routes. That option concerns a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. The problem here is different: An engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

C:

Policy and reachability behavior is distorted by a false external session. It addresses a different problem: An operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. Here, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

D:

Healthy MPLS transport is disrupted by a false fault diagnosis. This could matter when an operator sees the transport label removed near the egress and flags a failure despite the design allowing PHP. In this case, an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path.

Question 409

At fictional Crestland Networks 103, a regional service-provider network, during a two-site transit migration, operations observes: A network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems. Which configuration or operational correction most directly addresses this failure?

  1. Confirm MED comparison applicability and use a suitable local outbound policy if needed.
  2. Inspect BGP update history, peer flaps and policy events before changing transit selection.
  3. Place precise deny/accept logic in the intended evaluation order and validate policy results.
  4. Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery.

Explanation

Correct Answer

A:

Confirm MED comparison applicability and use a suitable local outbound policy if needed. BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent. The chosen path follows documented selection policy with MED considered only where applicable.

Incorrect Answers

B:

Inspect BGP update history, peer flaps and policy events before changing transit selection. The choice would be appropriate if an upstream prefix repeatedly withdraws and returns but the operations view shows only the current best route. Here, a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems.

C:

Place precise deny/accept logic in the intended evaluation order and validate policy results. That option concerns a broad accept term in a BGP policy is evaluated before a specific reject term, letting unwanted routes through. The problem here is different: A network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems.

D:

Apply compatible supported authentication settings on the intended OSPF interfaces and verify adjacency recovery. It addresses a different problem: A newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree. Here, a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems.

Question 410

At fictional Crestland Networks 103, a regional service-provider network, during a two-site transit migration, operations observes: A network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems. Which Junos forwarding or control-plane rule applies to this case?

  1. IBGP connects peers within an AS while EBGP represents inter-AS exchange with different policy expectations.
  2. BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent.
  3. BGP import policy governs which learned prefixes enter local route selection.
  4. The IS-IS overload indication can discourage transit use during control-plane recovery.

Explanation

Correct Answer

B:

BGP MED expresses a neighboring AS's ingress preference and its comparison scope is policy-dependent. Confirm MED comparison applicability and use a suitable local outbound policy if needed. The chosen path follows documented selection policy with MED considered only where applicable.

Incorrect Answers

A:

IBGP connects peers within an AS while EBGP represents inter-AS exchange with different policy expectations. That relates to circumstances in which an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary. Here the problem is that a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems.

C:

BGP import policy governs which learned prefixes enter local route selection. The choice would be appropriate if a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy. Here, a network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems.

D:

The IS-IS overload indication can discourage transit use during control-plane recovery. That option concerns a newly rebooted core router attracts transit traffic while its forwarding state is still being restored. The problem here is different: A network expects MED to control all outbound peer choices even when comparing routes learned from unrelated neighboring autonomous systems.

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