Juniper JN0-664 Practice Test 23
Question 220
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An edge router receives a provider FlowSpec route yet forwards attacks unchanged because the filter was neither accepted by policy nor installed in the supported forwarding stage. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Set an arbitrary unused BGP community and promise every transit operator will lower its preference without agreeing a corresponding community policy.
- Treat packet-loss priority as a guarantee that all high-priority traffic cannot be dropped even when the physical interface is fully oversubscribed.
- Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ.
- Import every FlowSpec announcement from any external neighbor with unrestricted discard actions and no authorization or validation.
Explanation
Correct Answer
D:The directly relevant unsafe assumption is: Import every FlowSpec announcement from any external neighbor with unrestricted discard actions and no authorization or validation. That conflicts with the edge-to-cloud principle: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. Apply instead: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
Incorrect Answers
A:This alternative proposes: Set an arbitrary unused BGP community and promise every transit operator will lower its preference without agreeing a corresponding community policy. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
B:This alternative proposes: Treat packet-loss priority as a guarantee that all high-priority traffic cannot be dropped even when the physical interface is fully oversubscribed. It concerns a different Junos engineering issue CoS forwarding classes packet-loss priority and egress queue binding, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
C: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 FlowSpec validation and filtering boundaries.
Question 221
A Junos service-provider routing engineer investigates the following routing and service incident: Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- 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.
- 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.
- Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
Explanation
Correct Answer
A:The case-specific routing and services action is: 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. The governing Junos routing/service principle is: 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.
Incorrect Answers
B: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 Multiprotocol BGP family negotiations and VPN routes.
C: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 Multiprotocol BGP family negotiations and VPN routes.
D: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 Multiprotocol BGP family negotiations and VPN routes.
Question 222
A provider routing design review considers this situation. Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing. A colleague 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. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
- A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions.
- 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
D:The relevant Junos service-provider networking principle is: 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. In the described provider-network case (Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing.), it supports the planned action: 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.
Incorrect Answers
A:This alternative proposes: 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. It concerns a different Junos engineering issue BGP communities and selective transit routing policy, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
B: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 Multiprotocol BGP family negotiations and VPN routes.
C:This alternative proposes: A stub area generally suppresses external Type 5 LSAs, while an NSSA can inject external prefixes as Type 7 LSAs for translation at an ABR under configured conditions. It concerns a different Junos engineering issue OSPF stub NSSA and external LSA handling, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
Question 223
A Juniper service-provider engineer needs decisive verification evidence for this situation. Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
- Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
- Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
- Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups.
Explanation
Correct Answer
A:The direct discriminating observation is: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability. In the stated situation (Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing.), the intended acceptance outcome is: The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
Incorrect Answers
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 Multiprotocol BGP family negotiations and VPN routes.
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 Multiprotocol BGP family negotiations and VPN routes.
D:This alternative proposes: Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
Question 224
A service-provider acceptance team reviews the result of a provider-service change. Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing. The intended verification is: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability. Which outcome BEST demonstrates success? Select ONE best answer.
- The configured mode serves actual receivers without uncontrolled multicast flood in sparsely subscribed provider regions.
- A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules.
- The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
- Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
Explanation
Correct Answer
C:The verified success outcome is: The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged. Confirm this by: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
Incorrect Answers
A:That option concerns PIM dense mode versus sparse mode interface deployment. The related controlled intervention is: 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.
B:That option concerns BGP FlowSpec validation and filtering boundaries. The related controlled intervention is: 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.
D:This alternative proposes: Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
Question 225
A Junos service-provider routing engineer investigates this service-provider network scenario. Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
- Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
- Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
- Validate EVPN multihoming Ethernet segment identifiers and designated-forwarder behavior before activating redundant customer links.
- 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 Answers
A:The direct discriminating observation is: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
E:The case-specific routing and services action is: 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. The governing Junos routing/service principle is: 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. Verify the decision through: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
Incorrect Answers
B:This alternative proposes: Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another. It concerns a different Junos engineering issue Multicast RPF validation and source reachability, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
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 Multiprotocol BGP family negotiations and VPN routes in the stated situation (Two PEs are BGP Established and exchange inet.0 unicast, but their VPNv4 routes never appear because the negotiated family is missing.). A better case-specific check is: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
D:This alternative proposes: Validate EVPN multihoming Ethernet segment identifiers and designated-forwarder behavior before activating redundant customer links. It concerns a different Junos engineering issue EVPN Ethernet segment multihoming and designated forwarder, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
Question 226
A Junos service-provider routing engineer investigates the following routing and service incident: A route reflector receives IPv4 VPN routes but a new PE expects IPv6 VPN prefixes despite its peer family configuration being IPv4-only. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Inspect broadcast-network DR and BDR election state and interface priority before attempting to control database exchange behavior on an Ethernet shared segment.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
- 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.
- Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
Explanation
Correct Answer
C:The case-specific routing and services action is: 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.
Incorrect Answers
A:This alternative proposes: Inspect broadcast-network DR and BDR election state and interface priority before attempting to control database exchange behavior on an Ethernet shared segment. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
B: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 Multiprotocol BGP family negotiations and VPN routes.
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 Multiprotocol BGP family negotiations and VPN routes.
Question 227
A provider routing design review considers this situation. A route reflector receives IPv4 VPN routes but a new PE expects IPv6 VPN prefixes despite its peer family configuration being IPv4-only. A colleague 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. Which technical principle BEST supports that action? Select ONE best answer.
- An L1 network may rely on attached/default routing toward L1/L2 routers; deliberate interlevel leaking or summarization can expose selected routes without making every area full Level 2.
- BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
- 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.
- 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
D:The relevant Junos service-provider networking principle is: 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. In the described provider-network case (A route reflector receives IPv4 VPN routes but a new PE expects IPv6 VPN prefixes despite its peer family configuration being IPv4-only.), it supports the planned action: 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.
Incorrect Answers
A:This alternative proposes: An L1 network may rely on attached/default routing toward L1/L2 routers; deliberate interlevel leaking or summarization can expose selected routes without making every area full Level 2. 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 Multiprotocol BGP family negotiations and VPN routes.
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 Multiprotocol BGP family negotiations and VPN routes.
C: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 Multiprotocol BGP family negotiations and VPN routes.
Question 228
A Juniper service-provider engineer needs decisive verification evidence for this situation. A route reflector receives IPv4 VPN routes but a new PE expects IPv6 VPN prefixes despite its peer family configuration being IPv4-only. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect VPLS instance configuration, signaling session state, remote PE discovery, VPLS route or LDP label distribution and actual MAC reachability.
- Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
- Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
- Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
Explanation
Correct Answer
B:The direct discriminating observation is: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability. In the stated situation (A route reflector receives IPv4 VPN routes but a new PE expects IPv6 VPN prefixes despite its peer family configuration being IPv4-only.), the intended acceptance outcome is: The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
Incorrect Answers
A:This alternative proposes: Inspect VPLS instance configuration, signaling session state, remote PE discovery, VPLS route or LDP label distribution and actual MAC reachability. It concerns a different Junos engineering issue VPLS service control plane LDP versus BGP distribution, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
C: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 Multiprotocol BGP family negotiations and VPN routes.
D: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 Multiprotocol BGP family negotiations and VPN routes.
Question 229
A service-provider acceptance team reviews the result of a provider-service change. A route reflector receives IPv4 VPN routes but a new PE expects IPv6 VPN prefixes despite its peer family configuration being IPv4-only. The intended verification is: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability. Which outcome BEST demonstrates success? Select ONE best answer.
- The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
- The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged.
- Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
- The expected DIS represents the shared LAN in the LSDB and routes converge when a controlled election change takes place.
Explanation
Correct Answer
B:The verified success outcome is: The intended family appears on both ends with the right permitted prefixes and labels, while unrelated BGP families remain unchanged. Confirm this by: Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability. The related controlled intervention is: 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.
Incorrect Answers
A:That option concerns BGP external multihop and loopback peer reachability. The related controlled intervention is: 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.
C:This alternative proposes: Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
D:That option concerns IS-IS DIS pseudonode and broadcast circuit election. The related controlled intervention is: 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.
Question 230
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A route reflector receives IPv4 VPN routes but a new PE expects IPv6 VPN prefixes despite its peer family configuration being IPv4-only. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- 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.
- Configure a 232/8 SSM channel for a receiver that only sends unspecified-source IGMPv2 joins and assume it identifies the desired video source.
- Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference.
- 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
D:That conflicts with the edge-to-cloud principle: 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.
Incorrect Answers
A:This alternative proposes: 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. It concerns a different Junos engineering issue BGP NEXT_HOP reachability and inet.3 recursion, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
B:This alternative proposes: Configure a 232/8 SSM channel for a receiver that only sends unspecified-source IGMPv2 joins and assume it identifies the desired video source. It concerns a different Junos engineering issue Source-specific multicast and IGMPv3 source filtering, not the directly tested provider-network issue Multiprotocol BGP family negotiations and VPN routes.
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 Multiprotocol BGP family negotiations and VPN routes.