Juniper JN0-664 Practice Test 22
Question 210
A Junos service-provider routing engineer investigates this service-provider network scenario. A provider considers applying one extremely low damping threshold to all Internet peers to reduce route-table churn despite risks to service availability. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress.
- Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
- Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
- Verify the transport and service label roles in an MPLS Layer 3 VPN before attributing a forwarding failure to the customer routing protocol.
- 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.
Explanation
Correct Answers
B:The case-specific routing and services action is: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
C:The direct discriminating observation is: Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
Incorrect Answers
A:This alternative proposes: Classify subscriber traffic with an appropriate behavior-aggregate or multifield classifier and confirm forwarding-class assignments at ingress. It concerns a different Junos engineering issue Junos CoS behavior aggregate versus multifield classifiers, not the directly tested provider-network issue BGP flap damping penalties and recovery.
D: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 flap damping penalties and recovery.
E: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 flap damping penalties and recovery.
Question 211
A Junos service-provider routing engineer investigates the following routing and service incident: A mitigation controller proposes a FlowSpec discard rule that inadvertently matches all DNS requests to a customer, not just the abusive source range. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
- Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
- Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
- Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.
Explanation
Correct Answer
B:The case-specific routing and services action is: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware. The governing Junos routing/service principle is: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
Incorrect Answers
A:This alternative proposes: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
C: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 FlowSpec validation and filtering boundaries.
D:This alternative proposes: Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor. It concerns a different Junos engineering issue OSPF adjacency MTU and hello compatibility diagnosis, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
Question 212
A provider routing design review considers this situation. A mitigation controller proposes a FlowSpec discard rule that inadvertently matches all DNS requests to a customer, not just the abusive source range. A colleague proposes: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware. 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.
- BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
- 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.
- 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.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. In the described provider-network case (A mitigation controller proposes a FlowSpec discard rule that inadvertently matches all DNS requests to a customer, not just the abusive source range.), it supports the planned action: 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: 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 FlowSpec validation and filtering boundaries.
C: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 FlowSpec validation and filtering boundaries.
D: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 BGP FlowSpec validation and filtering boundaries.
Question 213
A Juniper service-provider engineer needs decisive verification evidence for this situation. A mitigation controller proposes a FlowSpec discard rule that inadvertently matches all DNS requests to a customer, not just the abusive source range. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load.
- Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.
- Inspect BGP peer group roles, route-reflector client policy, originator ID, cluster list, accepted routes and reflectors' own next-hop reachability.
- Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
Explanation
Correct Answer
D:The direct discriminating observation is: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. In the stated situation (A mitigation controller proposes a FlowSpec discard rule that inadvertently matches all DNS requests to a customer, not just the abusive source range.), the intended acceptance outcome is: A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules.
Incorrect Answers
A:This alternative proposes: Examine scheduler-map bindings, allocated rates, interface queue statistics, high-priority activity and low-priority drain rate under load. It concerns a different Junos engineering issue CoS schedulers scheduler-maps and bandwidth sharing, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
B: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 FlowSpec validation and filtering boundaries.
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 FlowSpec validation and filtering boundaries.
Question 214
A service-provider acceptance team reviews the result of a provider-service change. A mitigation controller proposes a FlowSpec discard rule that inadvertently matches all DNS requests to a customer, not just the abusive source range. The intended verification is: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. 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 remote VPN site can reach its authorized peer across the AS boundary without transferring unrelated tenants' routes or losing required label resolution.
- A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules.
- The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
Explanation
Correct Answer
C:The verified success outcome is: A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules. Confirm this by: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
Incorrect Answers
A:This alternative proposes: Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss. 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.
B:That option concerns Interprovider Layer 3 VPN options and carrier of carriers. The related controlled intervention is: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
D:This alternative proposes: The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
Question 215
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A mitigation controller proposes a FlowSpec discard rule that inadvertently matches all DNS requests to a customer, not just the abusive source range. 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.
- Assume an Established BGP session exchanging inet unicast automatically negotiates and transports labeled VPNv4, VPNv6 and EVPN NLRI with no additional family support.
- Import every FlowSpec announcement from any external neighbor with unrestricted discard actions and no authorization or validation.
- 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.
Explanation
Correct Answer
C: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.
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 BGP FlowSpec validation and filtering boundaries.
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 FlowSpec validation and filtering boundaries.
D: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 FlowSpec validation and filtering boundaries.
Question 216
A Junos service-provider routing engineer investigates the following routing and service incident: 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. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Deploy BGP route reflection to scale iBGP while monitoring originator-id and cluster-list loop prevention and correct client membership.
- Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
- 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.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
Explanation
Correct Answer
B:The case-specific routing and services action is: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware. The governing Junos routing/service principle is: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. Verify the decision through: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
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 FlowSpec validation and filtering boundaries.
C: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 FlowSpec validation and filtering boundaries.
D:This alternative proposes: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. It concerns a different Junos engineering issue BGP export import policy and prefix controls, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
Question 217
A provider routing design review considers this situation. 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. A colleague proposes: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
- ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage.
- 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
B:The relevant Junos service-provider networking principle is: BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled. In the described provider-network case (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.), it supports the planned action: 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: 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 FlowSpec validation and filtering boundaries.
C:This alternative proposes: ABRs can advertise summary information between areas while routing policy and area ranges alter which routes are visible; overly broad aggregation can blackhole traffic if specifics lack coverage. It concerns a different Junos engineering issue OSPF interarea route summarization and route restrictions, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
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 FlowSpec validation and filtering boundaries.
Question 218
A Juniper service-provider engineer needs decisive verification evidence for this situation. 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 observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect community definitions, policy term matching, routes with communities, advertised attributes and bilateral traffic-engineering agreements.
- Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries.
- Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
- 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
C:The direct discriminating observation is: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. In the stated situation (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.), the intended acceptance outcome is: A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules.
Incorrect Answers
A: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 FlowSpec validation and filtering boundaries.
B:This alternative proposes: Inspect hub and spoke import/export communities, default-route presence, return routes, firewall/NAT policy and VPN-specific forwarding table entries. 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 FlowSpec validation and filtering boundaries.
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 BGP FlowSpec validation and filtering boundaries.
Question 219
A service-provider acceptance team reviews the result of a provider-service change. 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. The intended verification is: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. Which outcome BEST demonstrates success? Select ONE best answer.
- Traffic prefers the engineered feasible lower-cost path and uses a documented alternate when a critical link fails.
- After the underlying instability is corrected, legitimate reachability recovers according to documented damping rules without needlessly suppressing unrelated stable prefixes.
- A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules.
- The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
Explanation
Correct Answer
C:The verified success outcome is: A narrowly scoped malicious traffic pattern is mitigated without dropping normal customer services or importing unauthorized traffic rules. Confirm this by: Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters. The related controlled intervention is: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
Incorrect Answers
A:That option concerns IS-IS wide metrics traffic engineering and cost selection. The related controlled intervention is: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
B:That option concerns BGP flap damping penalties and recovery. The related controlled intervention is: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware.
D:This alternative proposes: The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue BGP FlowSpec validation and filtering boundaries.
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.