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 12

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.

Question 111

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. Which acceptance finding demonstrates the affected service has recovered?

  1. The lookup for the test destination selects the legitimate more-specific route rather than the broader summary.
  2. The route is active and the forwarding lookup shows an operational egress next hop.
  3. The suspect path is explained and only eligible loop-free routes are selected.
  4. The target prefix has the planned preference while unrelated routes retain prior selection.

Explanation

Correct Answer

D:

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. Routing policy terms should match only their explicitly intended routes before altering route attributes.

Incorrect Answers

A:

The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. 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 broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

B:

The route is active and the forwarding lookup shows an operational egress next hop. That relates to circumstances in which an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. Here the problem is that a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

C:

The suspect path is explained and only eligible loop-free routes are selected. This addresses a situation in which an engineer blames BGP route rejection on local preference while a route carries an unexpected autonomous-system path; however, a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

Question 112

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 is the direct residual network risk if the fault remains unresolved?

  1. Customers lose an intended default path even though the local route definition still exists.
  2. Packets continue dropping while monitoring incorrectly reports routing as healthy.
  3. A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer.
  4. Unrelated subscribers change transit paths after a narrowly intended policy update.

Explanation

Correct Answer

D:

Unrelated subscribers change transit paths after a narrowly intended policy update. 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.

Incorrect Answers

A:

Customers lose an intended default path even though the local route definition still exists. This relates to a case where a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route; the current situation is that a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

B:

Packets continue dropping while monitoring incorrectly reports routing as healthy. It is useful for situations where an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop; the reported fault, though, is that a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

C:

A mislabeled packet path is overlooked and service troubleshooting targets the wrong layer. That relates to circumstances in which operations assumes a packet is plain IP because the capture display does not decode its MPLS shim header. Here the problem is that a broad routing policy term changes preference for all imported prefixes instead of only the intended test network.

Question 113

At fictional Silverlake Routing 029, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. Which targeted remediation best fits the reported behavior?

  1. Set the backup route preference less favorable than the primary and verify failover under loss of the primary path.
  2. Inspect the aggregate route contributors and align the summary with the intended component prefixes.
  3. Compare protocol route state with the active route and forwarding-table next-hop installation.
  4. Use distinct virtual-switch or bridge-domain contexts with explicit interface membership.

Explanation

Correct Answer

C:

Compare protocol route state with the active route and forwarding-table next-hop installation. Learning a route in a protocol does not by itself prove it is active or installed for forwarding. The route is active and the forwarding lookup shows an operational egress next hop.

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 an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

B:

Inspect the aggregate route contributors and align the summary with the intended component prefixes. This relates to a case where a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; the current situation is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

D:

Use distinct virtual-switch or bridge-domain contexts with explicit interface membership. That relates to circumstances in which two customer VLANs merge unexpectedly after a virtual-switch template is copied across separate services. Here the problem is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

Question 114

At fictional Silverlake Routing 029, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. Why is this particular correction the best fit for the stated defect?

  1. Learning a route in a protocol does not by itself prove it is active or installed for forwarding.
  2. A RIB group permits specifically configured routes to be installed into additional routing tables.
  3. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability.
  4. IS-IS conveys extensible routing attributes in typed TLVs within protocol packets.

Explanation

Correct Answer

A:

Learning a route in a protocol does not by itself prove it is active or installed for forwarding. Compare protocol route state with the active route and forwarding-table next-hop installation. The route is active and the forwarding lookup shows an operational egress next hop.

Incorrect Answers

B:

A RIB group permits specifically configured routes to be installed into additional routing tables. This could help if a route intended for a monitoring routing table is missing because the RIB group does not include the recipient table, but not when an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

C:

A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. This relates to a case where a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; the current situation is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

D:

IS-IS conveys extensible routing attributes in typed TLVs within protocol packets. It is useful for situations where a monitoring parser treats a valid IS-IS reachability TLV as an unsupported fault and pages the operations team; the reported fault, though, is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

Question 115

At fictional Silverlake Routing 029, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. What direct observation would prove the corrective action worked?

  1. Known customer specifics forward normally and uncovered addresses within the aggregate are discarded.
  2. The interface unit is operational and the connected subnet appears in the correct routing table.
  3. The route is active and the forwarding lookup shows an operational egress next hop.
  4. The authorized inet6 routes are accepted while prohibited IPv6 prefixes remain blocked.

Explanation

Correct Answer

C:

The route is active and the forwarding lookup shows an operational egress next hop. Learning a route in a protocol does not by itself prove it is active or installed for forwarding. Compare protocol route state with the active route and forwarding-table next-hop installation.

Incorrect Answers

A:

Known customer specifics forward normally and uncovered addresses within the aggregate are discarded. This is applicable when a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; the present condition is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

B:

The interface unit is operational and the connected subnet appears in the correct routing table. It is relevant if a directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout, but the reported issue is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

D:

The authorized inet6 routes are accepted while prohibited IPv6 prefixes remain blocked. This relates to a case where a prefix-list filter written for IPv4 is applied conceptually to IPv6 routing, and all intended IPv6 routes vanish; the current situation is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

Question 116

At fictional Silverlake Routing 029, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. Which failure consequence follows most closely from ignoring this issue?

  1. An inappropriate summary attracts packets for destinations the provider cannot actually reach.
  2. Traffic crosses a customer boundary and violates contractual segmentation.
  3. Unplanned DIS churn produces extra flooding and convergence disruption.
  4. Packets continue dropping while monitoring incorrectly reports routing as healthy.

Explanation

Correct Answer

D:

Packets continue dropping while monitoring incorrectly reports routing as healthy. Learning a route in a protocol does not by itself prove it is active or installed for forwarding. Compare protocol route state with the active route and forwarding-table next-hop installation.

Incorrect Answers

A:

An inappropriate summary attracts packets for destinations the provider cannot actually reach. That could help when a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it; here, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

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 an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

C:

Unplanned DIS churn produces extra flooding and convergence disruption. It is relevant if operators see two possible LAN-designated routers and assume the wrong one leads routing for the shared segment, but the reported issue is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

Question 117

In a separate fictional JNCIS-SP lab review for Seabrook Metro 030, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. What intervention most directly restores the intended routing or switching behavior?

  1. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix.
  2. Compare protocol route state with the active route and forwarding-table next-hop installation.
  3. Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup.
  4. Restore consistent client-to-reflector peering and reachable loopback endpoints.

Explanation

Correct Answer

B:

Compare protocol route state with the active route and forwarding-table next-hop installation. The route is active and the forwarding lookup shows an operational egress next hop. Learning a route in a protocol does not by itself prove it is active or installed for forwarding.

Incorrect Answers

A:

Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. This could matter when a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. In this case, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

C:

Restore the intended more-specific route and diagnose forwarding with a longest-prefix-match lookup. This is applicable when an operator changes route preference to make a broader prefix override a healthy more-specific prefix; the present condition is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

D:

Restore consistent client-to-reflector peering and reachable loopback endpoints. It is relevant if an internal client learns routes from another client only intermittently after the route-reflector peering address changes, but the reported issue is that an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

Question 118

In a separate fictional JNCIS-SP lab review for Seabrook Metro 030, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. Which networking principle explains why the proposed correction is appropriate?

  1. Junos directly connected reachability depends on active logical interface configuration and state.
  2. For otherwise comparable routes, Junos route preference influences which eligible route becomes active.
  3. IRB traffic must bridge and route within an intentionally consistent service context.
  4. Learning a route in a protocol does not by itself prove it is active or installed for forwarding.

Explanation

Correct Answer

D:

Learning a route in a protocol does not by itself prove it is active or installed for forwarding. The route is active and the forwarding lookup shows an operational egress next hop. Compare protocol route state with the active route and forwarding-table next-hop installation.

Incorrect Answers

A:

Junos directly connected reachability depends on active logical interface configuration and state. It addresses a different problem: A directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. Here, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

B:

For otherwise comparable routes, Junos route preference influences which eligible route becomes active. This could matter when a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. In this case, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

C:

IRB traffic must bridge and route within an intentionally consistent service context. That could help when an IRB gateway is placed in the default routing instance while its tenant VLAN belongs to a separate virtual switch; here, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

Question 119

In a separate fictional JNCIS-SP lab review for Seabrook Metro 030, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. Which validation result would confirm the design is now functioning?

  1. The route is active and the forwarding lookup shows an operational egress next hop.
  2. The interface unit is operational and the connected subnet appears in the correct routing table.
  3. The target prefix has the planned preference while unrelated routes retain prior selection.
  4. Peer details show the intended internal AS relationship and routes propagate by design.

Explanation

Correct Answer

A:

The route is active and the forwarding lookup shows an operational egress next hop. Compare protocol route state with the active route and forwarding-table next-hop installation. Learning a route in a protocol does not by itself prove it is active or installed for forwarding.

Incorrect Answers

B:

The interface unit is operational and the connected subnet appears in the correct routing table. It addresses a different problem: A directly connected peering subnet disappears after a logical interface unit is removed during a maintenance template rollout. Here, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

C:

The target prefix has the planned preference while unrelated routes retain prior selection. This could matter when a broad routing policy term changes preference for all imported prefixes instead of only the intended test network. In this case, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

D:

Peer details show the intended internal AS relationship and routes propagate by design. That could help when an operator configures an internal route-reflector session as EBGP and introduces an unintended AS boundary; here, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

Question 120

In a separate fictional JNCIS-SP lab review for Seabrook Metro 030, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop. What likely service impact does this condition create?

  1. Packets to the customer prefix are dropped despite the static route statement being present.
  2. Customers lose an intended default path even though the local route definition still exists.
  3. Packets continue dropping while monitoring incorrectly reports routing as healthy.
  4. A route leak consumes routing resources and destabilizes production services.

Explanation

Correct Answer

C:

Packets continue dropping while monitoring incorrectly reports routing as healthy. Compare protocol route state with the active route and forwarding-table next-hop installation. Learning a route in a protocol does not by itself prove it is active or installed for forwarding.

Incorrect Answers

A:

Packets to the customer prefix are dropped despite the static route statement being present. The choice would be appropriate if a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface. Here, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

B:

Customers lose an intended default path even though the local route definition still exists. That option concerns a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. The problem here is different: An engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

D:

A route leak consumes routing resources and destabilizes production services. This could matter when a misconfigured customer sends thousands of unintended routes and overwhelms the expected BGP peering scale. In this case, an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop.

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