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 18

Question 170

A Junos service-provider routing engineer investigates this service-provider network scenario. A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
  2. Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
  3. Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
  4. Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
  5. Trace a VPNv4 prefix from MP-BGP reception to a customer VRF routing table, distinguishing provider VPN control-plane storage and installed customer forwarding routes.

Explanation

Correct Answers

B:

The direct discriminating observation is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.

D:

The case-specific routing and services action is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. Verify the decision through: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.

Incorrect Answers

A:

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 export import policy and prefix controls.

C:

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 export import policy and prefix controls.

E:

This alternative proposes: Trace a VPNv4 prefix from MP-BGP reception to a customer VRF routing table, distinguishing provider VPN control-plane storage and installed customer forwarding routes. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue BGP export import policy and prefix controls in the stated situation (A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet.). A better case-specific check is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. The more targeted action is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.

Question 171

A Junos service-provider routing engineer investigates the following routing and service incident: An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. 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.
  2. Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
  3. Validate that all nonbackbone OSPF areas have a supported logical connection to area 0, and use virtual links only as a documented transitional design.
  4. Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Explanation

Correct Answer

D:

The case-specific routing and services action is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior. The governing Junos routing/service principle is: Standard and extended communities are attributes that policies may match; the effect of a community depends on the receiving network's documented interpretation and configuration.

Incorrect Answers

A:

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 communities and selective transit routing policy.

B:

This alternative proposes: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue BGP communities and selective transit routing policy.

C:

This alternative proposes: Validate that all nonbackbone OSPF areas have a supported logical connection to area 0, and use virtual links only as a documented transitional design. It concerns a different Junos engineering issue OSPF multi-area backbone connectivity and virtual-link limitations, not the directly tested provider-network issue BGP communities and selective transit routing policy.

Question 172

A provider routing design review considers this situation. An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term. A colleague proposes: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior. Which technical principle BEST supports that action? Select ONE best answer.

  1. Standard and extended communities are attributes that policies may match; the effect of a community depends on the receiving network's documented interpretation and configuration.
  2. Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
  3. 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.
  4. Multipoint Ethernet services learn source MAC locations and flood unknown unicast, broadcast and multicast within permitted service boundaries; split-horizon rules limit loop-causing PW-to-PW forwarding.

Explanation

Correct Answer

A:

The relevant Junos service-provider networking principle is: Standard and extended communities are attributes that policies may match; the effect of a community depends on the receiving network's documented interpretation and configuration. In the described provider-network case (An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term.), it supports the planned action: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Incorrect Answers

B:

This alternative proposes: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP communities and selective transit routing policy.

C:

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 communities and selective transit routing policy.

D:

This alternative proposes: Multipoint Ethernet services learn source MAC locations and flood unknown unicast, broadcast and multicast within permitted service boundaries; split-horizon rules limit loop-causing PW-to-PW forwarding. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue BGP communities and selective transit routing policy.

Question 173

A Juniper service-provider engineer needs decisive verification evidence for this situation. An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. 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.
  2. Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
  3. Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.
  4. Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state.

Explanation

Correct Answer

C:

The direct discriminating observation is: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. In the stated situation (An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term.), the intended acceptance outcome is: Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer.

Incorrect Answers

A:

This alternative proposes: 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. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue BGP communities and selective transit routing policy in the stated situation (An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term.). A better case-specific check is: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. The more targeted action is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

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 communities and selective transit routing policy.

D:

This alternative proposes: Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue BGP communities and selective transit routing policy.

Question 174

A service-provider acceptance team reviews the result of a provider-service change. An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term. The intended verification is: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. Which outcome BEST demonstrates success? Select ONE best answer.

  1. Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer.
  2. The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
  3. Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.
  4. The traffic arrives on an eligible RPF interface and reaches subscribed downstream links without introducing a multicast loop.

Explanation

Correct Answer

A:

The verified success outcome is: Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer. Confirm this by: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.

Incorrect Answers

B:

That option concerns BGP best-path attributes and local preference. The related controlled intervention is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

C:

That option concerns BGP route reflectors originator and cluster loop prevention. The related controlled intervention is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

D:

That option concerns Multicast RPF validation and source reachability. The related controlled intervention is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Question 175

A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An ISP advertises a prefix with a documented peer community but a downstream carrier never changes treatment because the receiving policy lacks the matching term. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.

  1. Configure aggressive route damping globally and assume any withdrawn customer prefix instantly becomes available after its neighbor comes back up.
  2. Enable MP-BGP VPN unicast for a tenant and promise its source multicast group will automatically traverse provider PEs with no MVPN or multicast setup.
  3. Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference.
  4. Set an arbitrary unused BGP community and promise every transit operator will lower its preference without agreeing a corresponding community policy.

Explanation

Correct Answer

D:

That conflicts with the edge-to-cloud principle: Standard and extended communities are attributes that policies may match; the effect of a community depends on the receiving network's documented interpretation and configuration.

Incorrect Answers

A:

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 communities and selective transit routing policy.

B:

This alternative proposes: Enable MP-BGP VPN unicast for a tenant and promise its source multicast group will automatically traverse provider PEs with no MVPN or multicast setup. It concerns a different Junos engineering issue Multicast VPN provider and customer traffic separation, not the directly tested provider-network issue BGP communities and selective transit routing policy.

C:

This alternative proposes: Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue BGP communities and selective transit routing policy.

Question 176

A Junos service-provider routing engineer investigates the following routing and service incident: A maintenance window requires limiting one customer's upstream export, and the technician proposes deleting all routes rather than honoring agreed community controls. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.

  1. Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.
  2. Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
  3. Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm.
  4. Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Explanation

Correct Answer

D:

The case-specific routing and services action is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior. The governing Junos routing/service principle is: Standard and extended communities are attributes that policies may match; the effect of a community depends on the receiving network's documented interpretation and configuration. Verify the decision through: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.

Incorrect Answers

A:

This alternative proposes: Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP communities and selective transit routing policy.

B:

This alternative proposes: Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue BGP communities and selective transit routing policy.

C:

This alternative proposes: Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue BGP communities and selective transit routing policy.

Question 177

A provider routing design review considers this situation. A maintenance window requires limiting one customer's upstream export, and the technician proposes deleting all routes rather than honoring agreed community controls. A colleague proposes: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior. Which technical principle BEST supports that action? Select ONE best answer.

  1. Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
  2. Standard and extended communities are attributes that policies may match; the effect of a community depends on the receiving network's documented interpretation and configuration.
  3. Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements.
  4. VPN topology is shaped by which prefixes are imported/exported between sites, and a shared service or Internet breakout must be explicitly engineered rather than assumed by one RT value.

Explanation

Correct Answer

B:

The relevant Junos service-provider networking principle is: Standard and extended communities are attributes that policies may match; the effect of a community depends on the receiving network's documented interpretation and configuration. In the described provider-network case (A maintenance window requires limiting one customer's upstream export, and the technician proposes deleting all routes rather than honoring agreed community controls.), it supports the planned action: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Incorrect Answers

A:

This alternative proposes: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP communities and selective transit routing policy.

C:

This alternative proposes: Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP communities and selective transit routing policy.

D:

This alternative proposes: VPN topology is shaped by which prefixes are imported/exported between sites, and a shared service or Internet breakout must be explicitly engineered rather than assumed by one RT value. It concerns a different Junos engineering issue Layer 3 VPN hub spoke topology and controlled Internet breakout, not the directly tested provider-network issue BGP communities and selective transit routing policy.

Question 178

A Juniper service-provider engineer needs decisive verification evidence for this situation. A maintenance window requires limiting one customer's upstream export, and the technician proposes deleting all routes rather than honoring agreed community controls. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.

  1. Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state.
  2. Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
  3. Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
  4. Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.

Explanation

Correct Answer

D:

The direct discriminating observation is: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. In the stated situation (A maintenance window requires limiting one customer's upstream export, and the technician proposes deleting all routes rather than honoring agreed community controls.), the intended acceptance outcome is: Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer.

Incorrect Answers

A:

This alternative proposes: Inspect MAC tables per VPLS instance, flood counters, PE attachment circuits, pseudowire membership, MAC aging and loop-protection state. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue BGP communities and selective transit routing policy.

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 communities and selective transit routing policy.

C:

This alternative proposes: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue BGP communities and selective transit routing policy.

Question 179

A service-provider acceptance team reviews the result of a provider-service change. A maintenance window requires limiting one customer's upstream export, and the technician proposes deleting all routes rather than honoring agreed community controls. The intended verification is: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. Which outcome BEST demonstrates success? Select ONE best answer.

  1. Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer.
  2. The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
  3. The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
  4. Multicast subscribers continue receiving approved sources when one RP fails, with no duplicate or missing source registration state.

Explanation

Correct Answer

A:

The verified success outcome is: Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer. Confirm this by: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. The related controlled intervention is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Incorrect Answers

B:

That option concerns BGP external multihop and loopback peer reachability. The related controlled intervention is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

C:

That option concerns Multiprotocol BGP family negotiations and VPN routes. The related controlled intervention is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

D:

That option concerns Anycast RP resilient multicast service and routing policy. The related controlled intervention is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Question 180

A Junos service-provider routing engineer investigates this service-provider network scenario. A maintenance window requires limiting one customer's upstream export, and the technician proposes deleting all routes rather than honoring agreed community controls. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.

  1. Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.
  2. Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
  3. Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
  4. Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.
  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

A:

The direct discriminating observation is: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.

D:

The case-specific routing and services action is: Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.

Incorrect Answers

B:

This alternative proposes: Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings. It concerns a different Junos engineering issue BGP-signaled Layer 2 VPN NLRI and route target import, not the directly tested provider-network issue BGP communities and selective transit routing policy.

C:

This alternative proposes: Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue BGP communities and selective transit routing policy.

E:

This alternative proposes: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue BGP communities and selective transit routing policy.

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