Juniper JN0-664 Practice Test 17
Question 160
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. Two route reflectors reuse a cluster configuration incorrectly and legitimate reflected prefixes are suppressed by cluster-loop safeguards. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Assume every route present in bgp.l3vpn.0 is automatically installed into every customer's instance.inet.0 regardless of import policies.
- Assume every BGP peer that sends the same prefix creates a data-plane ECMP entry even when their route attributes and policies differ.
- Assume ordinary iBGP peers will automatically pass their learned routes to every other iBGP peer without a route reflector or full mesh.
- Tell network operations that AS path length universally overrides local preference and ignore an explicit provider routing-policy preference.
Explanation
Correct Answer
C:That conflicts with the edge-to-cloud principle: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
Incorrect Answers
A:This alternative proposes: Assume every route present in bgp.l3vpn.0 is automatically installed into every customer's instance.inet.0 regardless of import policies. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue BGP route reflectors originator and cluster loop prevention.
B: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 route reflectors originator and cluster loop prevention.
D: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 route reflectors originator and cluster loop prevention.
Question 161
A Junos service-provider routing engineer investigates the following routing and service incident: A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact.
- 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 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
B:The case-specific routing and services action is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. The governing Junos routing/service principle is: Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements.
Incorrect Answers
A:This alternative proposes: Distinguish ingress policing from egress shaping and apply a documented committed-rate or burst policy with measured customer impact. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue BGP export import policy and prefix controls.
C:This alternative proposes: Validate candidate BGP FlowSpec rules against agreed DDoS filtering policy and propagation controls before applying them to production forwarding hardware. It concerns a different Junos engineering issue BGP FlowSpec validation and filtering boundaries, not the directly tested provider-network issue BGP export import policy and prefix controls.
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 export import policy and prefix controls.
Question 162
A provider routing design review considers this situation. A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers. A colleague proposes: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. Which technical principle BEST supports that action? Select ONE best answer.
- 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.
- 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.
- Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements.
- IS-IS elects a DIS on a broadcast segment to originate pseudonode information; it has no OSPF-style separately elected backup designated router, and election behavior differs.
Explanation
Correct Answer
C:The relevant Junos service-provider networking principle is: Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements. In the described provider-network case (A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers.), it supports the planned action: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
Incorrect Answers
A: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 export import policy and prefix controls.
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 export import policy and prefix controls.
D:This alternative proposes: IS-IS elects a DIS on a broadcast segment to originate pseudonode information; it has no OSPF-style separately elected backup designated router, and election behavior differs. It concerns a different Junos engineering issue IS-IS DIS pseudonode and broadcast circuit election, not the directly tested provider-network issue BGP export import policy and prefix controls.
Question 163
A Juniper service-provider engineer needs decisive verification evidence for this situation. A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover.
- 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 route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
Explanation
Correct Answer
C:In the stated situation (A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers.), the intended acceptance outcome is: Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
Incorrect Answers
A:This alternative proposes: Inspect RP node reachability, anycast route advertisement, appropriate state synchronization, peer status, group registration and service traffic during failover. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue BGP export import policy and prefix controls.
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 export import policy and prefix controls.
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 export import policy and prefix controls.
Question 164
A service-provider acceptance team reviews the result of a provider-service change. A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers. The intended verification is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. Which outcome BEST demonstrates success? Select ONE best answer.
- Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.
- Customer traffic follows learned remote PE paths and floods only where required without generating a provider-wide bridging loop.
- 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
D:The verified success outcome is: Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available. Confirm this by: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
Incorrect Answers
A:This alternative proposes: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP export import policy and prefix controls.
B:That option concerns VPLS MAC learning flooding and split-horizon safeguards. The related controlled intervention is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
C:That option concerns Multiprotocol BGP family negotiations and VPN routes. The related controlled intervention is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
Question 165
A Junos service-provider routing engineer investigates this service-provider network scenario. A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
- Use reverse-path forwarding checks to determine why an arriving multicast packet is accepted on one interface but discarded on another.
- Confirm appropriate PIM sparse-mode RP reachability and registration for any-source multicast groups before treating receiver membership as full service health.
- Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
- Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
Explanation
Correct Answers
A:The case-specific routing and services action is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. The governing Junos routing/service principle is: Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements. Verify the decision through: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
E:The direct discriminating observation is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. In the stated situation (A customer accidentally announces a default route to an ISP, and a misordered permissive export term propagates it toward peers.), the intended acceptance outcome is: Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
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 BGP export import policy and prefix controls.
C:This alternative proposes: Confirm appropriate PIM sparse-mode RP reachability and registration for any-source multicast groups before treating receiver membership as full service health. It concerns a different Junos engineering issue PIM sparse mode rendezvous point and shared tree operation, not the directly tested provider-network issue BGP export import policy and prefix controls.
D: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 export import policy and prefix controls.
Question 166
A Junos service-provider routing engineer investigates the following routing and service incident: A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
- Confirm the eligibility requirements for BGP multipath and distinguish multiple accepted routes from actual installed forwarding next hops.
- 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.
Explanation
Correct Answer
C:The case-specific routing and services action is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
Incorrect Answers
A:This alternative proposes: Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop. It concerns a different Junos engineering issue VPLS site identifiers multihoming and service convergence, not the directly tested provider-network issue BGP export import policy and prefix controls.
B: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 BGP export import policy and prefix controls.
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 export import policy and prefix controls.
Question 167
A provider routing design review considers this situation. A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet. A colleague proposes: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. 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.
- Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements.
- On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive.
- BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: Junos routing policies match routes and apply actions at protocol boundaries; match order, accept/reject and explicit default behavior determine effective advertisements. In the described provider-network case (A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet.), it supports the planned action: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
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 export import policy and prefix controls.
C:This alternative proposes: On an OSPF broadcast network a DR and BDR reduce full-adjacency fanout; elections depend on eligible interface priorities and router IDs, and are not always preemptive. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue BGP export import policy and prefix controls.
D:This alternative proposes: BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters. It concerns a different Junos engineering issue BGP best-path attributes and local preference, not the directly tested provider-network issue BGP export import policy and prefix controls.
Question 168
A Juniper service-provider engineer needs decisive verification evidence for this situation. A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
- Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
- Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
- Compare show ospf interface, election priorities, router IDs, two-way versus full neighbors, and current DR/BDR state after planned link transitions.
Explanation
Correct Answer
A:The direct discriminating observation is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. In the stated situation (A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet.), the intended acceptance outcome is: Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
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 BGP export import policy and prefix controls.
C: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 export import policy and prefix controls.
D:This alternative proposes: Compare show ospf interface, election priorities, router IDs, two-way versus full neighbors, and current DR/BDR state after planned link transitions. It concerns a different Junos engineering issue OSPF designated router election on a multiaccess segment, not the directly tested provider-network issue BGP export import policy and prefix controls.
Question 169
A service-provider acceptance team reviews the result of a provider-service change. A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet. The intended verification is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. Which outcome BEST demonstrates success? Select ONE best answer.
- Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available.
- Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop.
- The session establishes over the intended transport and advertises only authorized routing information even across a link failure.
- The customer transports frames within the agreed service MTU without unexplained fragmentation, truncation or interworking incompatibility.
Explanation
Correct Answer
A:The verified success outcome is: Only sanctioned customer prefixes are exported, bogons or overly broad aggregates are rejected, and legitimate upstream routes stay available. Confirm this by: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. The related controlled intervention is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
Incorrect Answers
B:This alternative proposes: Clients receive authorized routes without a full iBGP mesh and no reflected route loops or unreachable forwarding next hops develop. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP export import policy and prefix controls.
C:That option concerns BGP external multihop and loopback peer reachability. The related controlled intervention is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
D:That option concerns Layer 2 pseudowire MTU and control-word interworking. The related controlled intervention is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
Question 170
A Junos service-provider routing engineer investigates this service-provider network scenario. A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it.
- Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
- Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
- Trace a VPNv4 prefix from MP-BGP reception to a customer VRF routing table, distinguishing provider VPN control-plane storage and installed customer forwarding routes.
Explanation
Correct Answers
B:The direct discriminating observation is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
D:The case-specific routing and services action is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain. Verify the decision through: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state.
Incorrect Answers
A:This alternative proposes: Configure and verify source-specific multicast using a sender-and-group channel while ensuring receiver signaling and source reachability support it. It concerns a different Junos engineering issue Source-specific multicast and IGMPv3 source filtering, not the directly tested provider-network issue BGP export import policy and prefix controls.
C:This alternative proposes: Inspect TCP/179 reachability, peer address source, configured multihop behavior, next-hop routing, authentication and show bgp neighbor state transitions. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP export import policy and prefix controls.
E:This alternative proposes: Trace a VPNv4 prefix from MP-BGP reception to a customer VRF routing table, distinguishing provider VPN control-plane storage and installed customer forwarding routes. It concerns a different Junos engineering issue VPNv4 bgp.l3vpn.0 versus customer VRF route tables, not the directly tested provider-network issue BGP export import policy and prefix controls in the stated situation (A new customer /24 is present in inet.0 but missing from BGP advertisements because its policy prefix-list excludes the newly allocated subnet.). A better case-specific check is: Review show configuration policy-options, protocol group policy attachments, route advertisements, route receive output and active versus hidden state. The more targeted action is: Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.