Juniper JN0-664 Practice Test 19
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.
- Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.
- Validate BGP Layer 2 VPN service discovery through negotiated signaling families, route distinguishers/targets and customer connection mappings.
- Verify service MTU and any supported pseudowire encapsulation/control-word expectations when a pseudowire is signaled Up but customer frames fail.
- Use BGP communities as controlled signals for provider routing policies instead of confusing tagging with guaranteed remote traffic behavior.
- 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.
Question 181
A Junos service-provider routing engineer investigates the following routing and service incident: A provider connects to two equal-capacity transits but only one path appears in the forwarding table despite both peers being Established. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
- Choose a supported VPLS signaling model and verify peer discovery, service membership and MPLS forwarding transport independently.
- Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
- Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.
Explanation
Correct Answer
C:The case-specific routing and services action is: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops. The governing Junos routing/service principle is: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution.
Incorrect Answers
A:This alternative proposes: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
B:This alternative proposes: Choose a supported VPLS signaling model and verify peer discovery, service membership and MPLS forwarding transport independently. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
D: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 multipath equal cost and per-flow forwarding.
Question 182
A provider routing design review considers this situation. A provider connects to two equal-capacity transits but only one path appears in the forwarding table despite both peers being Established. A colleague proposes: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops. Which technical principle BEST supports that action? Select ONE best answer.
- Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements.
- OSPF Type 1 external metrics include internal cost toward the ASBR, whereas Type 2 external metrics primarily compare the advertised external metric with internal tie behavior.
- BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution.
- eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution. In the described provider-network case (A provider connects to two equal-capacity transits but only one path appears in the forwarding table despite both peers being Established.), it supports the planned action: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
Incorrect Answers
A: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 multipath equal cost and per-flow forwarding.
B:This alternative proposes: OSPF Type 1 external metrics include internal cost toward the ASBR, whereas Type 2 external metrics primarily compare the advertised external metric with internal tie behavior. It concerns a different Junos engineering issue OSPF external type E1 E2 route cost evaluation, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
D:This alternative proposes: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
Question 183
A Juniper service-provider engineer needs decisive verification evidence for this situation. A provider connects to two equal-capacity transits but only one path appears in the forwarding table despite both peers being Established. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.
- Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices.
- Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
- Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
Explanation
Correct Answer
A:In the stated situation (A provider connects to two equal-capacity transits but only one path appears in the forwarding table despite both peers being Established.), the intended acceptance outcome is: Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
Incorrect Answers
B:This alternative proposes: Review route-policy terms, L1 and L2 route databases, leaked prefix entries, interface scope and next-hop resolution from affected access devices. It concerns a different Junos engineering issue IS-IS Level 2 to Level 1 route leaking and summaries, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
C: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 multipath equal cost and per-flow forwarding.
D:This alternative proposes: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
Question 184
A service-provider acceptance team reviews the result of a provider-service change. A provider connects to two equal-capacity transits but only one path appears in the forwarding table despite both peers being Established. The intended verification is: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution. Which outcome BEST demonstrates success? Select ONE best answer.
- Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
- The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
- The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
- Access routers learn only authorized leaked routes, continue using their correct area exit and do not create interlevel routing loops.
Explanation
Correct Answer
A:The verified success outcome is: Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss. Confirm this by: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.
Incorrect Answers
B:This alternative proposes: The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
C:This alternative proposes: The session establishes over the intended transport and advertises only authorized routing information even across a link failure. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
D:That option concerns IS-IS Level 2 to Level 1 route leaking and summaries. The related controlled intervention is: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
Question 185
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A provider connects to two equal-capacity transits but only one path appears in the forwarding table despite both peers being Established. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Disable all split-horizon checks and bridge every pseudowire to every other pseudowire as a first response to one unknown MAC address.
- Assume an Established BGP session exchanging inet unicast automatically negotiates and transports labeled VPNv4, VPNv6 and EVPN NLRI with no additional family support.
- Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ.
- Advertise every route from a customer router to a global transit peer to repair a single missing /24 without inspecting export-policy conditions.
Explanation
Correct Answer
C:The directly relevant unsafe assumption is: Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ. That conflicts with the edge-to-cloud principle: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution.
Incorrect Answers
A:This alternative proposes: Disable all split-horizon checks and bridge every pseudowire to every other pseudowire as a first response to one unknown MAC address. It concerns a different Junos engineering issue VPLS MAC learning flooding and split-horizon safeguards, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
B:This alternative proposes: Assume an Established BGP session exchanging inet unicast automatically negotiates and transports labeled VPNv4, VPNv6 and EVPN NLRI with no additional family support. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
D:This alternative proposes: Advertise every route from a customer router to a global transit peer to repair a single missing /24 without inspecting export-policy conditions. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
Question 186
A Junos service-provider routing engineer investigates the following routing and service incident: A route migration configures multipath but a different local preference on one peer prevents both paths from becoming eligible. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
- Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.
- Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.
- Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
Explanation
Correct Answer
D:The case-specific routing and services action is: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops. The governing Junos routing/service principle is: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution. Verify the decision through: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.
Incorrect Answers
A: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 multipath equal cost and per-flow forwarding.
B: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 multipath equal cost and per-flow forwarding.
C:This alternative proposes: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP. It concerns a different Junos engineering issue IS-IS adjacency NET and interface mismatch troubleshooting, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
Question 187
A provider routing design review considers this situation. A route migration configures multipath but a different local preference on one peer prevents both paths from becoming eligible. A colleague proposes: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops. Which technical principle BEST supports that action? Select ONE best answer.
- Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
- ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees.
- BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution.
- Damping mechanisms can temporarily suppress repeatedly unstable prefixes and later reuse them as penalties decay; incorrect thresholds may prolong outages for legitimate destinations.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution. In the described provider-network case (A route migration configures multipath but a different local preference on one peer prevents both paths from becoming eligible.), it supports the planned action: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
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 multipath equal cost and per-flow forwarding.
B:This alternative proposes: ASM PIM-SM may use a rendezvous point for rendezvous and shared tree creation, after which routers can move eligible traffic onto source-based trees. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
D: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 multipath equal cost and per-flow forwarding.
Question 188
A Juniper service-provider engineer needs decisive verification evidence for this situation. A route migration configures multipath but a different local preference on one peer prevents both paths from becoming eligible. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
- Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
- Inspect SSM group range, IGMPv3 (S,G) membership, source unicast route, RPF state, PIM joins and actual packet counts.
- Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.
Explanation
Correct Answer
D:In the stated situation (A route migration configures multipath but a different local preference on one peer prevents both paths from becoming eligible.), the intended acceptance outcome is: Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
Incorrect Answers
A: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 multipath equal cost and per-flow forwarding.
B: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 multipath equal cost and per-flow forwarding.
C: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 multipath equal cost and per-flow forwarding.
Question 189
A service-provider acceptance team reviews the result of a provider-service change. A route migration configures multipath but a different local preference on one peer prevents both paths from becoming eligible. The intended verification is: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution. Which outcome BEST demonstrates success? Select ONE best answer.
- The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
- The neighbor reaches Full, both routers synchronize the relevant link-state database, and no unrelated adjacencies are disrupted.
- Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
- The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
Explanation
Correct Answer
C:The verified success outcome is: Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss. Confirm this by: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution. The related controlled intervention is: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
Incorrect Answers
A:This alternative proposes: The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
B:That option concerns OSPF adjacency MTU and hello compatibility diagnosis. The related controlled intervention is: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
D:This alternative proposes: The session establishes over the intended transport and advertises only authorized routing information even across a link failure. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
Question 190
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A route migration configures multipath but a different local preference on one peer prevents both paths from becoming eligible. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Configure aggressive route damping globally and assume any withdrawn customer prefix instantly becomes available after its neighbor comes back up.
- Install a summary for discontiguous customer access blocks and drop all component routes without verifying that the ABR actually forwards the entire aggregate.
- Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ.
- Assume an Established BGP session exchanging inet unicast automatically negotiates and transports labeled VPNv4, VPNv6 and EVPN NLRI with no additional family support.
Explanation
Correct Answer
C:The directly relevant unsafe assumption is: Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ. That conflicts with the edge-to-cloud principle: BGP multipath can select compatible equal-cost eligible paths according to policy and platform rules, but two neighbors advertising a prefix does not inherently mean equal load distribution. Apply instead: Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
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 multipath equal cost and per-flow forwarding.
B:This alternative proposes: Install a summary for discontiguous customer access blocks and drop all component routes without verifying that the ABR actually forwards the entire aggregate. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.
D:This alternative proposes: Assume an Established BGP session exchanging inet unicast automatically negotiates and transports labeled VPNv4, VPNv6 and EVPN NLRI with no additional family support. It concerns a different Junos engineering issue Multiprotocol BGP family negotiations and VPN routes, not the directly tested provider-network issue BGP multipath equal cost and per-flow forwarding.