Juniper JN0-664 Practice Test 20
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.
Question 191
A Junos service-provider routing engineer investigates the following routing and service incident: An ISP builds a loopback-to-loopback eBGP test session across an exchange fabric, but the session never establishes because the source address is wrong. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
- 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.
- Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
- 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.
Explanation
Correct Answer
C:The case-specific routing and services action is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. The governing Junos routing/service principle is: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
Incorrect Answers
A:This alternative proposes: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
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 external multihop and loopback peer reachability.
D: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 external multihop and loopback peer reachability.
Question 192
A provider routing design review considers this situation. An ISP builds a loopback-to-loopback eBGP test session across an exchange fabric, but the session never establishes because the source address is wrong. A colleague proposes: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. Which technical principle BEST supports that action? Select ONE best answer.
- A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates.
- BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
- eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
- 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.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability. In the described provider-network case (An ISP builds a loopback-to-loopback eBGP test session across an exchange fabric, but the session never establishes because the source address is wrong.), it supports the planned action: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
Incorrect Answers
A:This alternative proposes: A BGP-signaled Layer 2 VPN advertises service-related NLRI and label reachability; route-target and instance-policy behavior determine which remote service participates. 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 external multihop and loopback peer reachability.
B: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 external multihop and loopback peer reachability.
D: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 external multihop and loopback peer reachability.
Question 193
A Juniper service-provider engineer needs decisive verification evidence for this situation. An ISP builds a loopback-to-loopback eBGP test session across an exchange fabric, but the session never establishes because the source address is wrong. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect Ethernet segment configuration, ESI values, DF election or relevant designated-forwarder state, ES routes, BGP reachability and measured failover forwarding.
- Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
- Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.
- Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
Explanation
Correct Answer
D:The direct discriminating observation is: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. In the stated situation (An ISP builds a loopback-to-loopback eBGP test session across an exchange fabric, but the session never establishes because the source address is wrong.), the intended acceptance outcome is: The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
Incorrect Answers
A:This alternative proposes: Inspect Ethernet segment configuration, ESI values, DF election or relevant designated-forwarder state, ES routes, BGP reachability and measured failover forwarding. It concerns a different Junos engineering issue EVPN Ethernet segment multihoming and designated forwarder, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
B: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 external multihop and loopback peer reachability.
C:This alternative proposes: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
Question 194
A service-provider acceptance team reviews the result of a provider-service change. An ISP builds a loopback-to-loopback eBGP test session across an exchange fabric, but the session never establishes because the source address is wrong. The intended verification is: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. 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 approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
- The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
- The chosen exit aligns to the operator's end-to-end cost policy, and failover to another valid ASBR meets the documented path objective.
Explanation
Correct Answer
C:The verified success outcome is: The session establishes over the intended transport and advertises only authorized routing information even across a link failure. Confirm this by: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
Incorrect Answers
A:That option concerns Multiprotocol BGP family negotiations and VPN routes. The related controlled intervention is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
B:That option concerns BGP best-path attributes and local preference. The related controlled intervention is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
D:That option concerns OSPF external type E1 E2 route cost evaluation. The related controlled intervention is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
Question 195
A Junos service-provider routing engineer investigates this service-provider network scenario. An ISP builds a loopback-to-loopback eBGP test session across an exchange fabric, but the session never establishes because the source address is wrong. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
- Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable.
- Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol.
- Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
- Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
Explanation
Correct Answers
A:The direct discriminating observation is: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
D:The case-specific routing and services action is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. The governing Junos routing/service principle is: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability. Verify the decision through: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
Incorrect Answers
B:This alternative proposes: Apply summarization or import/export controls at the appropriate OSPF area boundary after proving which access prefixes should be reachable. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
C:This alternative proposes: Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol. It concerns a different Junos engineering issue MPLS VPN transport label stack and next hop, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
E: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 external multihop and loopback peer reachability.
Question 196
A Junos service-provider routing engineer investigates the following routing and service incident: A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails. 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.
- Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
- Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
- Choose a supported VPLS signaling model and verify peer discovery, service membership and MPLS forwarding transport independently.
Explanation
Correct Answer
B:The case-specific routing and services action is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
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 external multihop and loopback peer reachability.
C:This alternative proposes: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
D: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 external multihop and loopback peer reachability.
Question 197
A provider routing design review considers this situation. A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails. A colleague proposes: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used. Which technical principle BEST supports that action? Select ONE best answer.
- eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
- 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.
- A policer can discard or remark excess traffic according to a configured rate and burst; shaping usually buffers and schedules departure under a bandwidth constraint, with different latency effects.
- 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
A:The relevant Junos service-provider networking principle is: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability. In the described provider-network case (A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails.), it supports the planned action: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
Incorrect Answers
B:This alternative proposes: 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. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
C:This alternative proposes: A policer can discard or remark excess traffic according to a configured rate and burst; shaping usually buffers and schedules departure under a bandwidth constraint, with different latency effects. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
D:This alternative proposes: 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. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
Question 198
A Juniper service-provider engineer needs decisive verification evidence for this situation. A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails. 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.
- Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
- Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.
- Inspect source route lookup, multicast RPF information, arrival interface, show multicast route details and topology symmetry.
Explanation
Correct Answer
A:The direct discriminating observation is: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. In the stated situation (A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails.), the intended acceptance outcome is: The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
Incorrect Answers
B: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 external multihop and loopback peer reachability.
C:This alternative proposes: Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
D:This alternative proposes: Inspect source route lookup, multicast RPF information, arrival interface, show multicast route details and topology symmetry. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.
Question 199
A service-provider acceptance team reviews the result of a provider-service change. A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails. The intended verification is: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. Which outcome BEST demonstrates success? Select ONE best answer.
- The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.
- The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
- Customer multicast subscribers receive their authorized streams through the VPN without flooding other tenants or depending on unavailable default multicast underlay features.
- Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
Explanation
Correct Answer
B:The verified success outcome is: The session establishes over the intended transport and advertises only authorized routing information even across a link failure. Confirm this by: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. The related controlled intervention is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
Incorrect Answers
A:This alternative proposes: The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue BGP external multihop and loopback peer reachability in the stated situation (A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails.). A better case-specific check is: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. The more targeted action is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
C:That option concerns Multicast VPN provider and customer traffic separation. The related controlled intervention is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
D:That option concerns BGP multipath equal cost and per-flow forwarding. The related controlled intervention is: Design an eBGP multihop session with explicit remote loopback reachability and appropriate TTL/session transport settings when directly connected peering is not used.
Question 200
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A provider attempts to improve session resilience by moving BGP peering to loopbacks but forgets to verify reachability when its only transport circuit fails. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Advertise every route from a customer router to a global transit peer to repair a single missing /24 without inspecting export-policy conditions.
- Point a BGP neighbor at a remote loopback across three routers without supporting multihop or an IGP/static route and call the repeated Connect state a BGP software defect.
- Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference.
- Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU.
Explanation
Correct Answer
B:That conflicts with the edge-to-cloud principle: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
Incorrect Answers
A: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 external multihop and loopback peer reachability.
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 external multihop and loopback peer reachability.
D:This alternative proposes: Declare a pseudowire healthy based only on an Up connection flag despite large tagged frames being dropped on a transport link with insufficient payload MTU. It concerns a different Junos engineering issue Layer 2 pseudowire MTU and control-word interworking, not the directly tested provider-network issue BGP external multihop and loopback peer reachability.