cert
cert-1
cert-2

Pass Juniper JN0-664 Exam in First Attempt Guaranteed!

Get 100% Latest Exam Questions, Accurate & Verified Answers to Pass the Actual Exam!
30 Days Free Updates, Instant Download!

cert-5
cert-6
JN0-664 Exam - Verified By Experts
JN0-664 Premium File

JN0-664 Premium File

$69.99
$76.99
  • Premium File 96 Questions & Answers. Last Update: Nov 19, 2026

Whats Included:

  • Latest Questions
  • 100% Accurate Answers
  • Fast Exam Updates
 
$76.99
$69.99
accept 20 downloads in the last 7 days
block-screenshots
Juniper JN0-664 Practice Test 15

Question 140

A Junos service-provider routing engineer investigates this service-provider network scenario. After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
  2. Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
  3. Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
  4. Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
  5. Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.

Explanation

Correct Answers

D:

The case-specific routing and services action is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. Verify the decision through: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.

E:

The direct discriminating observation is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.

Incorrect Answers

A:

This alternative proposes: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP best-path attributes and local preference.

B:

This alternative proposes: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. It concerns a different Junos engineering issue Source-specific multicast and IGMPv3 source filtering, not the directly tested provider-network issue BGP best-path attributes and local preference.

C:

This alternative proposes: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP best-path attributes and local preference.

Question 141

A Junos service-provider routing engineer investigates the following routing and service incident: A PE learns VPN-related prefixes from a route reflector but cannot resolve the advertising PE loopback through its underlay forwarding table. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
  2. Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
  3. Verify address-family negotiation and route transport for IPv4 unicast, VPNv4, VPNv6 or EVPN separately rather than treating Established BGP TCP state as proof each family works.
  4. Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.

Explanation

Correct Answer

A:

A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel. Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.

Incorrect Answers

B:

This alternative proposes: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

C:

This alternative proposes: Verify address-family negotiation and route transport for IPv4 unicast, VPNv4, VPNv6 or EVPN separately rather than treating Established BGP TCP state as proof each family works. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

D:

This alternative proposes: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Question 142

A provider routing design review considers this situation. A PE learns VPN-related prefixes from a route reflector but cannot resolve the advertising PE loopback through its underlay forwarding table. A colleague proposes: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. Which technical principle BEST supports that action? Select ONE best answer.

  1. BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
  2. Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.
  3. On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive.
  4. A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel.

Explanation

Correct Answer

D:

The relevant Junos service-provider networking principle is: A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel. In the described provider-network case (A PE learns VPN-related prefixes from a route reflector but cannot resolve the advertising PE loopback through its underlay forwarding table.), it supports the planned action: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

Incorrect Answers

A:

This alternative proposes: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

B:

This alternative proposes: Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

C:

This alternative proposes: On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Question 143

A Juniper service-provider engineer needs decisive verification evidence for this situation. A PE learns VPN-related prefixes from a route reflector but cannot resolve the advertising PE loopback through its underlay forwarding table. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover.
  2. Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
  3. Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.
  4. Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.

Explanation

Correct Answer

C:

The direct discriminating observation is: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. In the stated situation (A PE learns VPN-related prefixes from a route reflector but cannot resolve the advertising PE loopback through its underlay forwarding table.), the intended acceptance outcome is: The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.

Incorrect Answers

A:

This alternative proposes: Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

B:

This alternative proposes: Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

D:

This alternative proposes: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Question 144

A service-provider acceptance team reviews the result of a provider-service change. A PE learns VPN-related prefixes from a route reflector but cannot resolve the advertising PE loopback through its underlay forwarding table. The intended verification is: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. Which outcome BEST demonstrates success? Select ONE best answer.

  1. The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
  2. Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
  3. The two attachment circuits join only their authorized sites and the pseudowire status and customer traffic counters remain stable.
  4. The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.

Explanation

Correct Answer

D:

The verified success outcome is: The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure. Confirm this by: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.

Incorrect Answers

A:

That option concerns BGP best-path attributes and local preference. The related controlled intervention is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

B:

That option concerns BGP multipath equal cost and per-flow forwarding. The related controlled intervention is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

C:

That option concerns LDP signaled Layer 2 circuit pseudowire status and VC identifiers. The related controlled intervention is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

Question 145

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A PE learns VPN-related prefixes from a route reflector but cannot resolve the advertising PE loopback through its underlay forwarding table. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ.
  2. Configure aggressive route damping globally and assume any withdrawn customer prefix instantly becomes available after its neighbor comes back up.
  3. Enable receiver IGMP membership on every LAN and assert RPF is irrelevant to the provider's upstream multicast forwarding decisions.
  4. Apply maximum local preference to a path with an unresolved BGP next hop and insist that policy alone creates reachability to the next-hop address.

Explanation

Correct Answer

D:

That conflicts with the edge-to-cloud principle: A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel.

Incorrect Answers

A:

This alternative proposes: Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

B:

This alternative proposes: Configure aggressive route damping globally and assume any withdrawn customer prefix instantly becomes available after its neighbor comes back up. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

C:

This alternative proposes: Enable receiver IGMP membership on every LAN and assert RPF is irrelevant to the provider's upstream multicast forwarding decisions. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Question 146

A Junos service-provider routing engineer investigates the following routing and service incident: An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
  2. Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies.
  3. Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
  4. Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.

Explanation

Correct Answer

A:

The case-specific routing and services action is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. The governing Junos routing/service principle is: A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel.

Incorrect Answers

B:

This alternative proposes: Validate the PE-to-CE routing protocol and routing-instance binding before exporting customer routes into MP-BGP or changing provider-core policies. It concerns a different Junos engineering issue PE to CE routing and customer route redistribution, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

C:

This alternative proposes: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

D:

This alternative proposes: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Question 147

A provider routing design review considers this situation. An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback. A colleague proposes: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. Which technical principle BEST supports that action? Select ONE best answer.

  1. Behavior-aggregate classification examines existing packet markings whereas multifield classification can evaluate packet header fields; a configured classifier must be applied to the correct interface.
  2. MP-BGP carries routes for negotiated address families and associated path attributes; mismatched family configuration can block specific NLRI even when the underlying BGP session remains up.
  3. A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel.
  4. BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.

Explanation

Correct Answer

C:

The relevant Junos service-provider networking principle is: A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel. In the described provider-network case (An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback.), it supports the planned action: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

Incorrect Answers

A:

This alternative proposes: Behavior-aggregate classification examines existing packet markings whereas multifield classification can evaluate packet header fields; a configured classifier must be applied to the correct interface. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

B:

This alternative proposes: MP-BGP carries routes for negotiated address families and associated path attributes; mismatched family configuration can block specific NLRI even when the underlying BGP session remains up. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

D:

This alternative proposes: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Question 148

A Juniper service-provider engineer needs decisive verification evidence for this situation. An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
  2. Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.
  3. Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.
  4. Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts.

Explanation

Correct Answer

B:

The direct discriminating observation is: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. In the stated situation (An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback.), the intended acceptance outcome is: The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.

Incorrect Answers

A:

This alternative proposes: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

C:

This alternative proposes: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

D:

This alternative proposes: Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts. It concerns a different Junos engineering issue Source-specific multicast and IGMPv3 source filtering, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Question 149

A service-provider acceptance team reviews the result of a provider-service change. An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback. The intended verification is: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. Which outcome BEST demonstrates success? Select ONE best answer.

  1. The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.
  2. The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.
  3. Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer.
  4. After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes.

Explanation

Correct Answer

A:

The verified success outcome is: The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure. Confirm this by: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport. The related controlled intervention is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

Incorrect Answers

B:

That option concerns OSPF adjacency MTU and hello compatibility diagnosis. The related controlled intervention is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

C:

That option concerns BGP communities and selective transit routing policy. The related controlled intervention is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

D:

That option concerns BGP flap damping penalties and recovery. The related controlled intervention is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

Question 150

A Junos service-provider routing engineer investigates this service-provider network scenario. An iBGP route is present in protocol output yet hidden after an IGP policy mistakenly suppresses reachability to the BGP next-hop loopback. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
  2. Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior.
  3. Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
  4. Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.
  5. Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.

Explanation

Correct Answers

D:

The direct discriminating observation is: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.

E:

The case-specific routing and services action is: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. The governing Junos routing/service principle is: A BGP route can be accepted yet hidden or unusable when the advertised next hop cannot be resolved through an appropriate routing table or transport tunnel. Verify the decision through: Examine show route hidden, show route extensive, next-hop addresses, inet.0 or inet.3 as applicable, loopback IGP reachability and the labeled forwarding transport.

Incorrect Answers

A:

This alternative proposes: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

B:

This alternative proposes: Verify IPv6 customer prefixes across a supported L3VPN by checking VPNv6 MP-BGP family, route targets and IPv6 customer forwarding independently of IPv4 VPNv4 behavior. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

C:

This alternative proposes: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. It concerns a different Junos engineering issue Source-specific multicast and IGMPv3 source filtering, not the directly tested provider-network issue BGP NEXT_HOP reachability and inet.3 recursion.

Service Provider Routing and Switching, Professional (JNCIP-SP) (JN0-664) Practice Tests