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 4

Question 30

In a separate fictional JNCIS-SP lab review for Harborview ISP 008, a carrier-edge and core routing team, following a monitored network change window, engineers find: A generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. What technical principle underlies the right remedy?

  1. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability.
  2. Generated routes depend on qualifying routes and their configured policy, not merely on a destination name.
  3. Route lookup and default selection occur within the configured routing-instance context.
  4. Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding.

Explanation

Correct Answer

B:

Generated routes depend on qualifying routes and their configured policy, not merely on a destination name. The contributor is visible and the generated default returns with the expected forwarding next hop. Check the generated route contribution and acceptance policy, then restore the intended eligible contributor.

Incorrect Answers

A:

A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. 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 generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

C:

Route lookup and default selection occur within the configured routing-instance context. This relates to a case where a route lookup for a management instance falls back to the global default, which the design prohibits; the current situation is that a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

D:

Logical tunnel status alone is insufficient evidence of end-to-end overlay forwarding. It is useful for situations where monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered; the reported fault, though, is that a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

Question 31

In a separate fictional JNCIS-SP lab review for Harborview ISP 008, a carrier-edge and core routing team, following a monitored network change window, engineers find: A generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. 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 target prefix has the planned preference while unrelated routes retain prior selection.
  3. The route resolves over the intended interface and IPv6 neighbor discovery succeeds.
  4. The contributor is visible and the generated default returns with the expected forwarding next hop.

Explanation

Correct Answer

D:

The contributor is visible and the generated default returns with the expected forwarding next hop. Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. Generated routes depend on qualifying routes and their configured policy, not merely on a destination name.

Incorrect Answers

A:

The lookup for the test destination selects the legitimate more-specific route rather than the broader summary. 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 a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

B:

The target prefix has the planned preference while unrelated routes retain prior selection. It is relevant if a broad routing policy term changes preference for all imported prefixes instead of only the intended test network, but the reported issue is that a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

C:

The route resolves over the intended interface and IPv6 neighbor discovery succeeds. This could help if an IPv6 adjacency uses a link-local next hop, but its interface scope is omitted from the implementation design, but not when a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

Question 32

In a separate fictional JNCIS-SP lab review for Harborview ISP 008, a carrier-edge and core routing team, following a monitored network change window, engineers find: A generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route. 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. A false fix redirects a customer subnet onto an inappropriate aggregate route.
  3. An inappropriate summary attracts packets for destinations the provider cannot actually reach.
  4. Applications suffer selective stalls and retransmissions.

Explanation

Correct Answer

A:

Customers lose an intended default path even though the local route definition still exists. Check the generated route contribution and acceptance policy, then restore the intended eligible contributor. Generated routes depend on qualifying routes and their configured policy, not merely on a destination name.

Incorrect Answers

B:

A false fix redirects a customer subnet onto an inappropriate aggregate route. 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 a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

C:

An inappropriate summary attracts packets for destinations the provider cannot actually reach. It is relevant if a summary prefix is advertised even though operators have not confirmed which customer specifics contribute to it, but the reported issue is that a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

D:

Applications suffer selective stalls and retransmissions. This could help if large packets fail on an overlay while small probes work because encapsulation overhead exceeds path MTU, but not when a generated default route unexpectedly disappears after the upstream routing policy rejects its contributing route.

Question 33

At fictional Greenbridge ISP 009, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Which targeted remediation best fits the reported behavior?

  1. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix.
  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. Review RSVP path constraints and explicit-route settings, then reestablish the LSP.

Explanation

Correct Answer

A:

Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. Martian route handling protects the routing table from addresses that should not be treated as normally reachable. The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately.

Incorrect Answers

B:

Restrict the discard summary and verify that intended specific routes win for live destinations. That could help when a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; here, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

C:

Compare protocol route state with the active route and forwarding-table next-hop installation. This is applicable when an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop; the present condition is that a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

Review RSVP path constraints and explicit-route settings, then reestablish the LSP. It is relevant if an RSVP-signaled LSP follows a congested transit hop instead of the approved engineered route, but the reported issue is that a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

Question 34

At fictional Greenbridge ISP 009, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Why is this particular correction the best fit for the stated defect?

  1. Filter-based forwarding selects a routing lookup context based on packet classification.
  2. Martian route handling protects the routing table from addresses that should not be treated as normally reachable.
  3. A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability.
  4. OSPF peers must satisfy the configured authentication requirements to participate.

Explanation

Correct Answer

B:

Martian route handling protects the routing table from addresses that should not be treated as normally reachable. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately.

Incorrect Answers

A:

Filter-based forwarding selects a routing lookup context based on packet classification. 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 router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

C:

A discard route can protect against loops for unallocated portions of an aggregate but must not mask actual reachability. That could help when a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; here, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

OSPF peers must satisfy the configured authentication requirements to participate. This is applicable when a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree; the present condition is that a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

Question 35

At fictional Greenbridge ISP 009, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. What direct observation would prove the corrective action worked?

  1. A forwarding lookup shows the intended pair of next hops and traffic tests reach both links.
  2. The target table contains the approved route while unrelated tenant tables remain unchanged.
  3. The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately.
  4. Authenticated neighbors become Full and reject intentionally incorrect credentials.

Explanation

Correct Answer

C:

The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately. Martian route handling protects the routing table from addresses that should not be treated as normally reachable. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix.

Incorrect Answers

A:

A forwarding lookup shows the intended pair of next hops and traffic tests reach both links. That option concerns a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. The problem here is different: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

B:

The target table contains the approved route while unrelated tenant tables remain unchanged. 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 router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

Authenticated neighbors become Full and reject intentionally incorrect credentials. That could help when a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree; here, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

Question 36

At fictional Greenbridge ISP 009, a regional service-provider network, during a subscriber traffic restoration exercise, operations observes: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Which failure consequence follows most closely from ignoring this issue?

  1. Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable.
  2. A single uplink becomes overloaded while redundant capacity remains idle.
  3. Invalid or unintended address space can enter forwarding decisions and misdirect traffic.
  4. Some routers calculate stale paths and cannot reach required loopbacks.

Explanation

Correct Answer

C:

Invalid or unintended address space can enter forwarding decisions and misdirect traffic. Martian route handling protects the routing table from addresses that should not be treated as normally reachable. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix.

Incorrect Answers

A:

Routine traffic takes an unintended lower-capacity path and outage behavior becomes unpredictable. The choice would be appropriate if a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Here, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

B:

A single uplink becomes overloaded while redundant capacity remains idle. That option concerns a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. The problem here is different: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

Some routers calculate stale paths and cannot reach required loopbacks. This could matter when a remote PE misses a new loopback route because IS-IS link-state flooding is incomplete after an adjacency reset. In this case, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

Question 37

In a separate fictional JNCIS-SP lab review for Fairhaven Broadband 010, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. What intervention most directly restores the intended routing or switching behavior?

  1. Restrict the discard summary and verify that intended specific routes win for live destinations.
  2. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix.
  3. Validate both usable equal-cost paths and the forwarding-table load-balancing configuration.
  4. Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends.

Explanation

Correct Answer

B:

Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately. Martian route handling protects the routing table from addresses that should not be treated as normally reachable.

Incorrect Answers

A:

Restrict the discard summary and verify that intended specific routes win for live destinations. This addresses a situation in which a provider adds a discard summary but accidentally makes it cover reachable customer addresses more specific routes have not yet advertised; however, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

C:

Validate both usable equal-cost paths and the forwarding-table load-balancing configuration. That option concerns a provider expects two equal-cost links to share traffic, but forwarding consistently chooses one because the second next hop was not installed. The problem here is different: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

Validate outer path, encapsulation counters, inner routing, and decapsulation at both ends. It addresses a different problem: Monitoring declares a GRE circuit healthy based on logical-interface status while no encapsulated user packets are delivered. Here, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

Question 38

In a separate fictional JNCIS-SP lab review for Fairhaven Broadband 010, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Which networking principle explains why the proposed correction is appropriate?

  1. For otherwise comparable routes, Junos route preference influences which eligible route becomes active.
  2. Learning a route in a protocol does not by itself prove it is active or installed for forwarding.
  3. Martian route handling protects the routing table from addresses that should not be treated as normally reachable.
  4. A BGP path cannot be installed for forwarding when its next hop cannot be resolved.

Explanation

Correct Answer

C:

Martian route handling protects the routing table from addresses that should not be treated as normally reachable. The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix.

Incorrect Answers

A:

For otherwise comparable routes, Junos route preference influences which eligible route becomes active. That relates to circumstances in which a fallback static route takes traffic away from a healthy primary connection because its route preference was set too low. Here the problem is that a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

B:

Learning a route in a protocol does not by itself prove it is active or installed for forwarding. This addresses a situation in which an engineer reports recovery because a route appears in protocol output, but the hardware forwarding table still lacks a usable next hop; however, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

A BGP path cannot be installed for forwarding when its next hop cannot be resolved. That option concerns an IBGP-learned external prefix is present but inactive because the advertised next-hop address has no IGP reachability. The problem here is different: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

Question 39

In a separate fictional JNCIS-SP lab review for Fairhaven Broadband 010, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. Which validation result would confirm the design is now functioning?

  1. The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface.
  2. Matched traffic uses the alternate instance, while unmatched packets retain the default lookup.
  3. The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately.
  4. Authenticated neighbors become Full and reject intentionally incorrect credentials.

Explanation

Correct Answer

C:

The rejected prefix is absent from active forwarding and sanctioned exceptions are documented separately. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. Martian route handling protects the routing table from addresses that should not be treated as normally reachable.

Incorrect Answers

A:

The customer route is active in the routing table and its forwarding next hop points to the reachable transit interface. It is useful for situations where a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; the reported fault, though, is that a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

B:

Matched traffic uses the alternate instance, while unmatched packets retain the default lookup. 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 router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

Authenticated neighbors become Full and reject intentionally incorrect credentials. The choice would be appropriate if a newly hardened OSPF transit link stops exchanging neighbors because its authentication parameters do not agree. Here, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

Question 40

In a separate fictional JNCIS-SP lab review for Fairhaven Broadband 010, a carrier-edge and core routing team, following a new customer connectivity turn-up, engineers find: A router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing. What likely service impact does this condition create?

  1. A false fix redirects a customer subnet onto an inappropriate aggregate route.
  2. Packets to the customer prefix are dropped despite the static route statement being present.
  3. Invalid or unintended address space can enter forwarding decisions and misdirect traffic.
  4. IPv6 traffic is entirely lost due to an unsuitable policy match.

Explanation

Correct Answer

C:

Invalid or unintended address space can enter forwarding decisions and misdirect traffic. Review Junos martian-route behavior and explicit exceptions before accepting the suspect prefix. Martian route handling protects the routing table from addresses that should not be treated as normally reachable.

Incorrect Answers

A:

A false fix redirects a customer subnet onto an inappropriate aggregate route. 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 router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

B:

Packets to the customer prefix are dropped despite the static route statement being present. It is useful for situations where a provider edge has a static route for a customer prefix, but its next hop resolves only through a disconnected interface; the reported fault, though, is that a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

D:

IPv6 traffic is entirely lost due to an unsuitable policy match. This addresses a situation in which a prefix-list filter written for IPv4 is applied conceptually to IPv6 routing, and all intended IPv6 routes vanish; however, a router accepts reachability information for an address range the service-provider design treats as invalid for ordinary routing.

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