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 6

Question 50

At fictional Windmere Fiber 013, a regional service-provider network, during a two-site transit migration, operations observes: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Why is this particular correction the best fit for the stated defect?

  1. Junos directly connected reachability depends on active logical interface configuration and state.
  2. Generated routes depend on qualifying routes and their configured policy, not merely on a destination name.
  3. Junos BGP exports only routes accepted by the applicable export policy.
  4. A RIB group permits specifically configured routes to be installed into additional routing tables.

Explanation

Correct Answer

D:

A RIB group permits specifically configured routes to be installed into additional routing tables. Correct the RIB-group import/export table membership and verify only the intended route exchange. The target table contains the approved route while unrelated tenant tables remain unchanged.

Incorrect Answers

A:

Junos directly connected reachability depends on active logical interface configuration and state. That relates to circumstances in which a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. Here the problem is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

B:

Generated routes depend on qualifying routes and their configured policy, not merely on a destination name. This addresses a situation in which a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; however, a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

C:

Junos BGP exports only routes accepted by the applicable export policy. The choice would be appropriate if a customer prefix is not advertised to an upstream peer because the outbound routing policy does not permit it. Here, a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

Question 51

At fictional Windmere Fiber 013, a regional service-provider network, during a two-site transit migration, operations observes: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. What direct observation would prove the corrective action worked?

  1. The management routing-table lookup resolves only to the authorized management gateway.
  2. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface.
  3. Local hosts reach the IRB gateway and authorized routed subnets beyond it.
  4. The target table contains the approved route while unrelated tenant tables remain unchanged.

Explanation

Correct Answer

D:

The target table contains the approved route while unrelated tenant tables remain unchanged. A RIB group permits specifically configured routes to be installed into additional routing tables. Correct the RIB-group import/export table membership and verify only the intended route exchange.

Incorrect Answers

A:

The management routing-table lookup resolves only to the authorized management gateway. It is useful for situations where a route lookup for a management instance falls back to the global default, which the design prohibits; the reported fault, though, is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

B:

The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. 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 route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

C:

Local hosts reach the IRB gateway and authorized routed subnets beyond it. This addresses a situation in which customers on a bridged VLAN can exchange Layer 2 frames but cannot reach other subnets because the IRB gateway is absent; however, a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

Question 52

At fictional Windmere Fiber 013, a regional service-provider network, during a two-site transit migration, operations observes: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Which failure consequence follows most closely from ignoring this issue?

  1. Unrelated subscribers change transit paths after a narrowly intended policy update.
  2. The monitoring function loses required reachability or isolation is weakened by broad route copying.
  3. Sensitive application traffic bypasses the required upstream inspection or transit path.
  4. A hidden encapsulation or decapsulation fault persists behind a green interface alarm.

Explanation

Correct Answer

B:

The monitoring function loses required reachability or isolation is weakened by broad route copying. A RIB group permits specifically configured routes to be installed into additional routing tables. Correct the RIB-group import/export table membership and verify only the intended route exchange.

Incorrect Answers

A:

Unrelated subscribers change transit paths after a narrowly intended policy update. This relates to a case where a broad routing policy term changes preference for all imported prefixes instead of only the intended test network; the current situation is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

C:

Sensitive application traffic bypasses the required upstream inspection or transit path. That relates to circumstances in which a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. Here the problem is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

D:

A hidden encapsulation or decapsulation fault persists behind a green interface alarm. This addresses a situation in which monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; however, a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

Question 53

In a separate fictional JNCIS-SP lab review for Meadowcrest Telecom 014, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. What intervention most directly restores the intended routing or switching behavior?

  1. Inspect the aggregate route contributors and align the summary with the intended component prefixes.
  2. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup.
  3. Set compatible network type and review adjacency expectations on both ends.
  4. Correct the RIB-group import/export table membership and verify only the intended route exchange.

Explanation

Correct Answer

D:

Correct the RIB-group import/export table membership and verify only the intended route exchange. The target table contains the approved route while unrelated tenant tables remain unchanged. A RIB group permits specifically configured routes to be installed into additional routing tables.

Incorrect Answers

A:

Inspect the aggregate route contributors and align the summary with the intended component prefixes. This could help if a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it, but not when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

B:

Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. This relates to a case where an operator changes route preference to make a broader prefix override a healthy more-specific prefix; the current situation is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

C:

Set compatible network type and review adjacency expectations on both ends. It is useful for situations where OSPF adjacency setup fails on a network whose configured link type does not reflect point-to-point topology; the reported fault, though, is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

Question 54

In a separate fictional JNCIS-SP lab review for Meadowcrest Telecom 014, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Which networking principle explains why the proposed correction is appropriate?

  1. Route lookup and default selection occur within the configured routing-instance context.
  2. A configured static route forwards only after Junos can resolve its forwarding next hop.
  3. MPLS transit forwarding depends on installed label operations at each participating node.
  4. A RIB group permits specifically configured routes to be installed into additional routing tables.

Explanation

Correct Answer

D:

A RIB group permits specifically configured routes to be installed into additional routing tables. The target table contains the approved route while unrelated tenant tables remain unchanged. Correct the RIB-group import/export table membership and verify only the intended route exchange.

Incorrect Answers

A:

Route lookup and default selection occur within the configured routing-instance context. It is relevant if a route lookup for a management instance falls back to the global default, which the design prohibits, but the reported issue is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

B:

A configured static route forwards only after Junos can resolve its forwarding next hop. This could help if a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface, but not when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

C:

MPLS transit forwarding depends on installed label operations at each participating node. This relates to a case where an MPLS LSP is reported as configured but the expected outgoing label swap entry is missing; the current situation is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

Question 55

In a separate fictional JNCIS-SP lab review for Meadowcrest Telecom 014, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. Which validation result would confirm the design is now functioning?

  1. The primary path stays selected normally and the backup is activated only when the primary is unavailable.
  2. The target table contains the approved route while unrelated tenant tables remain unchanged.
  3. The interface unit is operational and the connected subnet appears in the correct routing table.
  4. The remote LSDB includes the fresh LSP and the loopback route becomes active.

Explanation

Correct Answer

B:

The target table contains the approved route while unrelated tenant tables remain unchanged. Correct the RIB-group import/export table membership and verify only the intended route exchange. A RIB group permits specifically configured routes to be installed into additional routing tables.

Incorrect Answers

A:

The primary path stays selected normally and the backup is activated only when the primary is unavailable. This is applicable when a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low; the present condition is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

C:

The interface unit is operational and the connected subnet appears in the correct routing table. This could help if a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout, but not when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

D:

The remote LSDB includes the fresh LSP and the loopback route becomes active. This relates to a case where a remote PE misses a new loopback route because IS-IS link-state flooding is incomplete after an adjacency reset; the current situation is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

Question 56

In a separate fictional JNCIS-SP lab review for Meadowcrest Telecom 014, a carrier-edge and core routing team, following a backbone resilience drill, engineers find: A route intended for a monitoring routing table is missing because the RIB group does not include the recipient table. What likely service impact does this condition create?

  1. The monitoring function loses required reachability or isolation is weakened by broad route copying.
  2. An inappropriate summary attracts packets for destinations the provider cannot actually reach.
  3. A single uplink becomes overloaded while redundant capacity remains idle.
  4. Subscriber VLANs collide or customer traffic arrives in the wrong service.

Explanation

Correct Answer

A:

The monitoring function loses required reachability or isolation is weakened by broad route copying. Correct the RIB-group import/export table membership and verify only the intended route exchange. A RIB group permits specifically configured routes to be installed into additional routing tables.

Incorrect Answers

B:

An inappropriate summary attracts packets for destinations the provider cannot actually reach. 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 intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

C:

A single uplink becomes overloaded while redundant capacity remains idle. It is relevant if a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed, but the reported issue is that a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

D:

Subscriber VLANs collide or customer traffic arrives in the wrong service. This could help if provider bridging accidentally rewrites the subscriber VLAN tag when applying an outer service tag, but not when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table.

Question 57

At fictional Bluehaven Backbone 015, a regional service-provider network, during a preproduction design validation, operations observes: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. 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. Correct the RIB-group import/export table membership and verify only the intended route exchange.
  3. Assign a unique network entity title system identifier and verify database identities.
  4. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration.

Explanation

Correct Answer

D:

Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links.

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 provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

B:

Correct the RIB-group import/export table membership and verify only the intended route exchange. That could help when a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table; here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

C:

Assign a unique network entity title system identifier and verify database identities. This is applicable when a device cloned from a lab template has the same IS-IS system ID as a production router; the present condition is that a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

Question 58

At fictional Bluehaven Backbone 015, a regional service-provider network, during a preproduction design validation, operations observes: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. Which Junos forwarding or control-plane rule applies to this case?

  1. For otherwise comparable routes, Junos route preference influences which eligible route becomes active.
  2. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops.
  3. Filter-based forwarding selects a routing lookup context based on packet classification.
  4. A route's presence is insufficient if its selected MPLS transport next hop is unusable.

Explanation

Correct Answer

B:

Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links.

Incorrect Answers

A:

For otherwise comparable routes, Junos route preference influences which eligible route becomes active. It addresses a different problem: A fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

C:

Filter-based forwarding selects a routing lookup context based on packet classification. That could help when a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup; here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

D:

A route's presence is insufficient if its selected MPLS transport next hop is unusable. This is applicable when a service path references an LSP that is down, but its IP route remains visible in the route table; the present condition is that a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

Question 59

At fictional Bluehaven Backbone 015, a regional service-provider network, during a preproduction design validation, operations observes: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. What operational evidence best establishes successful remediation?

  1. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup.
  2. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links.
  3. The contributor is visible and the generated default returns with the expected forwarding next hop.
  4. The path comparison identifies the deciding attributes and final active candidate.

Explanation

Correct Answer

B:

A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration.

Incorrect Answers

A:

Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. That option concerns a traffic class should be steered into an alternate routing instance but the firewall filter maps it to the default route lookup. The problem here is different: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

C:

The contributor is visible and the generated default returns with the expected forwarding next hop. This could matter when a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. In this case, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

D:

The path comparison identifies the deciding attributes and final active candidate. That could help when a prefix switches BGP best paths and operators cannot explain the result because only peer state is monitored; here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

Question 60

At fictional Bluehaven Backbone 015, a regional service-provider network, during a preproduction design validation, operations observes: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. Which operational harm would persist without the intended correction?

  1. A false fix redirects a customer subnet onto an inappropriate aggregate route.
  2. Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable.
  3. IBGP clients lack complete reachability and use inconsistent exits.
  4. A single uplink becomes overloaded while redundant capacity remains idle.

Explanation

Correct Answer

D:

A single uplink becomes overloaded while redundant capacity remains idle. Equal-cost candidate routes alone do not prove that forwarding uses multiple next hops. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration.

Incorrect Answers

A:

A false fix redirects a customer subnet onto an inappropriate aggregate route. The choice would be appropriate if an operator changes route preference to make a broader prefix override a healthy more-specific prefix. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

B:

Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. That option concerns a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. The problem here is different: A provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

C:

IBGP clients lack complete reachability and use inconsistent exits. It addresses a different problem: An internal client learns routes from another client only intermittently after the route-reflector peering address changes. Here, a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed.

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