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 11

Question 100

At fictional Glenwood Connectivity 025, a regional service-provider network, during a preproduction design validation, operations observes: A route lookup for a management instance falls back to the global default, which the design prohibits. Which failure consequence follows most closely from ignoring this issue?

  1. A single uplink becomes overloaded while redundant capacity remains idle.
  2. Neighbor sessions cannot establish because the local link subnet is unreachable.
  3. Management packets leave via a customer-facing path or fail unexpectedly.
  4. IBGP clients lack complete reachability and use inconsistent exits.

Explanation

Correct Answer

C:

Management packets leave via a customer-facing path or fail unexpectedly. Route lookup and default selection occur within the configured routing-instance context. Place an approved default route into the management routing instance and check its specific table.

Incorrect Answers

A:

A single uplink becomes overloaded while redundant capacity remains idle. This relates to a case where a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed; the current situation is that a route lookup for a management instance falls back to the global default, which the design prohibits.

B:

Neighbor sessions cannot establish because the local link subnet is unreachable. It is useful for situations where a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout; the reported fault, though, is that a route lookup for a management instance falls back to the global default, which the design prohibits.

D:

IBGP clients lack complete reachability and use inconsistent exits. This addresses a situation in which an internal client learns routes from another client only intermittently after the route-reflector peering address changes; however, a route lookup for a management instance falls back to the global default, which the design prohibits.

Question 101

In a separate fictional JNCIS-SP lab review for Hillside Transit 026, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A route lookup for a management instance falls back to the global default, which the design prohibits. What intervention most directly restores the intended routing or switching behavior?

  1. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path.
  2. Place an approved default route into the management routing instance and check its specific table.
  3. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup.
  4. Assign unique stable router IDs and safely reestablish affected OSPF adjacencies.

Explanation

Correct Answer

B:

Place an approved default route into the management routing instance and check its specific table. The management routing-table lookup resolves only to the authorized management gateway. Route lookup and default selection occur within the configured routing-instance context.

Incorrect Answers

A:

Set the backup route preference less favorable than the primary and verify failover under loss of the primary path. This could help if a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low, but not when a route lookup for a management instance falls back to the global default, which the design prohibits.

C:

Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. It is useful for situations where an operator changes route preference to make a broader prefix override a healthy more-specific prefix; the reported fault, though, is that a route lookup for a management instance falls back to the global default, which the design prohibits.

D:

Assign unique stable router IDs and safely reestablish affected OSPF adjacencies. That relates to circumstances in which two routers in the same routing domain advertise the same OSPF router ID after cloning a lab template. Here the problem is that a route lookup for a management instance falls back to the global default, which the design prohibits.

Question 102

In a separate fictional JNCIS-SP lab review for Hillside Transit 026, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A route lookup for a management instance falls back to the global default, which the design prohibits. Which networking principle explains why the proposed correction is appropriate?

  1. A RIB group permits specifically configured routes to be installed into additional routing tables.
  2. Independent routing instances provide logically isolated route resolution and forwarding contexts.
  3. Route lookup and default selection occur within the configured routing-instance context.
  4. BGP import policy governs which learned prefixes enter local route selection.

Explanation

Correct Answer

C:

Route lookup and default selection occur within the configured routing-instance context. The management routing-table lookup resolves only to the authorized management gateway. Place an approved default route into the management routing instance and check its specific table.

Incorrect Answers

A:

A RIB group permits specifically configured routes to be installed into additional routing tables. It is relevant if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table, but the reported issue is that a route lookup for a management instance falls back to the global default, which the design prohibits.

B:

Independent routing instances provide logically isolated route resolution and forwarding contexts. This could help if customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table, but not when a route lookup for a management instance falls back to the global default, which the design prohibits.

D:

BGP import policy governs which learned prefixes enter local route selection. It is useful for situations where a provider receives a customer-only prefix from a transit peer that should be blocked by an import policy; the reported fault, though, is that a route lookup for a management instance falls back to the global default, which the design prohibits.

Question 103

In a separate fictional JNCIS-SP lab review for Hillside Transit 026, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A route lookup for a management instance falls back to the global default, which the design prohibits. Which validation result would confirm the design is now functioning?

  1. The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances.
  2. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup.
  3. The management routing-table lookup resolves only to the authorized management gateway.
  4. A test frame relearns the source MAC and later packets forward as known unicast.

Explanation

Correct Answer

C:

The management routing-table lookup resolves only to the authorized management gateway. Place an approved default route into the management routing instance and check its specific table. Route lookup and default selection occur within the configured routing-instance context.

Incorrect Answers

A:

The route detail identifies the intended contributing prefixes and the summary is active only in the planned circumstances. This is applicable when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; the present condition is that a route lookup for a management instance falls back to the global default, which the design prohibits.

B:

Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. It is relevant if a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup, but the reported issue is that a route lookup for a management instance falls back to the global default, which the design prohibits.

D:

A test frame relearns the source MAC and later packets forward as known unicast. This relates to a case where a customer observes occasional unknown-unicast flooding after long inactivity and assumes every flood is a loop; the current situation is that a route lookup for a management instance falls back to the global default, which the design prohibits.

Question 104

In a separate fictional JNCIS-SP lab review for Hillside Transit 026, a carrier-edge and core routing team, following a maintenance rollback review, engineers find: A route lookup for a management instance falls back to the global default, which the design prohibits. What likely service impact does this condition create?

  1. Management packets leave via a customer-facing path or fail unexpectedly.
  2. Traffic crosses a customer boundary and violates contractual segmentation.
  3. Legitimate customer traffic is blackholed by an overbroad discard definition.
  4. Tunnel establishment loops or collapses during forwarding changes.

Explanation

Correct Answer

A:

Management packets leave via a customer-facing path or fail unexpectedly. Place an approved default route into the management routing instance and check its specific table. Route lookup and default selection occur within the configured routing-instance context.

Incorrect Answers

B:

Traffic crosses a customer boundary and violates contractual segmentation. This is applicable when customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table; the present condition is that a route lookup for a management instance falls back to the global default, which the design prohibits.

C:

Legitimate customer traffic is blackholed by an overbroad discard definition. It is relevant if a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised, but the reported issue is that a route lookup for a management instance falls back to the global default, which the design prohibits.

D:

Tunnel establishment loops or collapses during forwarding changes. This could help if a route to a GRE destination is learned through the same tunnel, creating recursive or looping resolution, but not when a route lookup for a management instance falls back to the global default, which the design prohibits.

Question 105

At fictional Westbridge Exchange 027, a regional service-provider network, during a core-routing acceptance test, operations observes: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network. Which configuration or operational correction most directly addresses this failure?

  1. Put each tenant's interfaces and routes into the intended routing instances and verify separate lookups.
  2. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration.
  3. Verify active next-hop resolution and transit forwarding after OSPF convergence.
  4. Constrain the policy match by precise destination and routing context, then inspect imported active routes.

Explanation

Correct Answer

D:

Constrain the policy match by precise destination and routing context, then inspect imported active routes. Routing policy terms should match only their explicitly intended routes before altering route attributes. The target prefix has the planned preference while unrelated routes retain prior selection.

Incorrect Answers

A:

Put each tenant's interfaces and routes into the intended routing instances and verify separate lookups. This could matter when customer A traffic resolves through Customer B's route because both tenants were inadvertently configured in the same routing table. In this case, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

B:

Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. That could help when a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed; here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

C:

Verify active next-hop resolution and transit forwarding after OSPF convergence. This is applicable when an engineer sees an OSPF route in the routing table and closes the incident without testing the egress path; the present condition is that a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

Question 106

At fictional Westbridge Exchange 027, a regional service-provider network, during a core-routing acceptance test, operations observes: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network. Which Junos forwarding or control-plane rule applies to this case?

  1. A RIB group permits specifically configured routes to be installed into additional routing tables.
  2. Routing policy terms should match only their explicitly intended routes before altering route attributes.
  3. For otherwise comparable routes, Junos route preference influences which eligible route becomes active.
  4. A BGP path cannot be installed for forwarding when its next hop cannot be resolved.

Explanation

Correct Answer

B:

Routing policy terms should match only their explicitly intended routes before altering route attributes. Constrain the policy match by precise destination and routing context, then inspect imported active routes. The target prefix has the planned preference while unrelated routes retain prior selection.

Incorrect Answers

A:

A RIB group permits specifically configured routes to be installed into additional routing tables. It addresses a different problem: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

C:

For otherwise comparable routes, Junos route preference influences which eligible route becomes active. That could help when a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low; here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

D:

A BGP path cannot be installed for forwarding when its next hop cannot be resolved. This is applicable when an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability; the present condition is that a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

Question 107

At fictional Westbridge Exchange 027, a regional service-provider network, during a core-routing acceptance test, operations observes: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network. What operational evidence best establishes successful remediation?

  1. The interface unit is operational and the connected subnet appears in the correct routing table.
  2. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup.
  3. The target prefix has the planned preference while unrelated routes retain prior selection.
  4. LSP signaling succeeds with compatible reservation values and reported resource state.

Explanation

Correct Answer

C:

The target prefix has the planned preference while unrelated routes retain prior selection. Routing policy terms should match only their explicitly intended routes before altering route attributes. Constrain the policy match by precise destination and routing context, then inspect imported active routes.

Incorrect Answers

A:

The interface unit is operational and the connected subnet appears in the correct routing table. That option concerns a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. The problem here is different: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

B:

Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. It addresses a different problem: A traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

D:

LSP signaling succeeds with compatible reservation values and reported resource state. That could help when an RSVP LSP setup fails after requested bandwidth exceeds available reservable capacity on a transit link; here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

Question 108

At fictional Westbridge Exchange 027, a regional service-provider network, during a core-routing acceptance test, operations observes: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network. Which operational harm would persist without the intended correction?

  1. The monitoring function loses required reachability or isolation is weakened by broad route copying.
  2. Unrelated subscribers change transit paths after a narrowly intended policy update.
  3. Invalid or unintended address space can enter forwarding decisions and misdirect traffic.
  4. Routers compute incompatible paths and traffic loops or blackholes can result.

Explanation

Correct Answer

B:

Unrelated subscribers change transit paths after a narrowly intended policy update. Routing policy terms should match only their explicitly intended routes before altering route attributes. Constrain the policy match by precise destination and routing context, then inspect imported active routes.

Incorrect Answers

A:

The monitoring function loses required reachability or isolation is weakened by broad route copying. The choice would be appropriate if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

C:

Invalid or unintended address space can enter forwarding decisions and misdirect traffic. It addresses a different problem: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

D:

Routers compute incompatible paths and traffic loops or blackholes can result. This could matter when two supposed adjacent routers have different views of a backbone link because database synchronization never completes. In this case, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

Question 109

In a separate fictional JNCIS-SP lab review for Crestland Networks 028, a carrier-edge and core routing team, following a monitored network change window, engineers find: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network. What should the Junos specialist change first to resolve this specific fault?

  1. Constrain the policy match by precise destination and routing context, then inspect imported active routes.
  2. Restrict the discard summary and verify that intended specific routes win for live destinations.
  3. Compare protocol route state with the active route and forwarding-table next-hop installation.
  4. Apply the supported LDP and IGP synchronization design and verify staged activation.

Explanation

Correct Answer

A:

Constrain the policy match by precise destination and routing context, then inspect imported active routes. The target prefix has the planned preference while unrelated routes retain prior selection. Routing policy terms should match only their explicitly intended routes before altering route attributes.

Incorrect Answers

B:

Restrict the discard summary and verify that intended specific routes win for live destinations. The choice would be appropriate if a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised. Here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

C:

Compare protocol route state with the active route and forwarding-table next-hop installation. That option concerns an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. The problem here is different: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

D:

Apply the supported LDP and IGP synchronization design and verify staged activation. It addresses a different problem: A new core link attracts IP routes before its LDP labels are ready, causing a transient service outage. Here, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

Question 110

In a separate fictional JNCIS-SP lab review for Crestland Networks 028, a carrier-edge and core routing team, following a monitored network change window, engineers find: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network. What technical principle underlies the right remedy?

  1. A configured static route forwards only after Junos can resolve its forwarding next hop.
  2. For otherwise comparable routes, Junos route preference influences which eligible route becomes active.
  3. Routing policy terms should match only their explicitly intended routes before altering route attributes.
  4. LAG availability depends on traffic being redirected to healthy active members after failure.

Explanation

Correct Answer

C:

Routing policy terms should match only their explicitly intended routes before altering route attributes. The target prefix has the planned preference while unrelated routes retain prior selection. Constrain the policy match by precise destination and routing context, then inspect imported active routes.

Incorrect Answers

A:

A configured static route forwards only after Junos can resolve its forwarding next hop. That relates to circumstances in which a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Here the problem is that a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

B:

For otherwise comparable routes, Junos route preference influences which eligible route becomes active. This addresses a situation in which a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low; however, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

D:

LAG availability depends on traffic being redirected to healthy active members after failure. That option concerns a provider assumes a two-member LAG is redundant but has never checked forwarding when one member fails. The problem here is different: A broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

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