Juniper JN0-664 Practice Test 14
Question 130
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. An IS-IS Level 2 adjacency enters Rejected after a key change, and the operator wants to clear all forwarding tables rather than review authentication. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured.
- Expect two pure Level 1 routers in different IS-IS areas to exchange routes directly across the core without an eligible Level 2 path.
- Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability.
- Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0.
Explanation
Correct Answer
C:The directly relevant unsafe assumption is: Copy a Level 1 area address from a different region onto a shared border router solely to force adjacency without understanding L1 versus L2 reachability. That conflicts with the edge-to-cloud principle: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. Apply instead: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.
Incorrect Answers
A:This alternative proposes: Assume a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.
B:This alternative proposes: Expect two pure Level 1 routers in different IS-IS areas to exchange routes directly across the core without an eligible Level 2 path. It concerns a different Junos engineering issue IS-IS level one level two hierarchy and area boundaries, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.
D:This alternative proposes: Assume an established VPNv4 BGP session automatically advertises the IPv6 prefix 2001:db8:50::/48 into every remote instance.inet6.0. It concerns a different Junos engineering issue IPv6 Layer 3 VPN VPNv6 route families and forwarding, not the directly tested provider-network issue IS-IS adjacency NET and interface mismatch troubleshooting.
Question 131
A Junos service-provider routing engineer investigates the following routing and service incident: An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
- Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
- Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
Explanation
Correct Answer
D:The case-specific routing and services action is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. The governing Junos routing/service principle is: BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters.
Incorrect Answers
A:This alternative proposes: Map traffic into the intended forwarding classes and packet-loss priority settings before assigning egress queue resources. 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 best-path attributes and local preference.
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 BGP best-path attributes and local preference.
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 best-path attributes and local preference.
Question 132
A provider routing design review considers this situation. An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied. A colleague proposes: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. Which technical principle BEST supports that action? Select ONE best answer.
- Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
- BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters.
- eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability.
- 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.
Explanation
Correct Answer
B:The relevant Junos service-provider networking principle is: BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters. In the described provider-network case (An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied.), it supports the planned action: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
Incorrect Answers
A:This alternative proposes: Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops. It concerns a different Junos engineering issue BGP route reflectors originator and cluster loop prevention, not the directly tested provider-network issue BGP best-path attributes and local preference.
C:This alternative proposes: eBGP commonly uses directly connected peer addresses; a multihop or loopback design requires supported session configuration and independent underlying route reachability. It concerns a different Junos engineering issue BGP external multihop and loopback peer reachability, not the directly tested provider-network issue BGP best-path attributes and local preference.
D: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 best-path attributes and local preference.
Question 133
A Juniper service-provider engineer needs decisive verification evidence for this situation. An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
- Review show pim neighbors, RP mapping, IGMP membership, PIM joins, source registration and multicast forwarding entries for affected groups.
- 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
A:The direct discriminating observation is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. In the stated situation (An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied.), the intended acceptance outcome is: The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
Incorrect Answers
B: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 BGP best-path attributes and local preference.
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 best-path attributes and local preference.
D: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 best-path attributes and local preference.
Question 134
A service-provider acceptance team reviews the result of a provider-service change. An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied. The intended verification is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. Which outcome BEST demonstrates success? Select ONE best answer.
- The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
- Prefixes carry the intended tagged policy signal and any permitted local preference or propagation change is confirmed at the correct peer.
- Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
- The expected eligible BGP route installs with a resolved forwarding next hop, and the data-plane path survives a controlled underlay failure.
Explanation
Correct Answer
A:The verified success outcome is: The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails. Confirm this by: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
Incorrect Answers
B:That option concerns BGP communities and selective transit routing policy. The related controlled intervention is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
C:That option concerns IS-IS link-state packet flooding and database consistency. The related controlled intervention is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
D: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 best-path attributes and local preference in the stated situation (An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied.). A better case-specific check is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. The more targeted action is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
Question 135
A provider change-review board examines this Junos service case. An ISP receives a customer prefix from two upstreams, but the path with more AS hops wins because a high local preference was applied. Which THREE statements together give an appropriate corrective action, supporting diagnostic check and success outcome? Select THREE answers.
- Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior.
- The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
- Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
- Inspect advertised FlowSpec NLRI, traffic selectors, redirect or rate-limit actions, receiving policy, route validation and actual filter counters.
- Validate EVPN multihoming Ethernet segment identifiers and designated-forwarder behavior before activating redundant customer links.
- Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
Explanation
Correct Answers
B:The verified success outcome is: The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails. Confirm this by: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. The related controlled intervention is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
C:The case-specific routing and services action is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. The governing Junos routing/service principle is: BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters. Verify the decision through: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
F:The direct discriminating observation is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
Incorrect Answers
A:This alternative proposes: Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior. It concerns a different Junos engineering issue IS-IS wide metrics traffic engineering and cost selection, not the directly tested provider-network issue BGP best-path attributes and local preference.
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 best-path attributes and local preference.
E: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 BGP best-path attributes and local preference.
Question 136
A Junos service-provider routing engineer investigates the following routing and service incident: After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
- Verify the recursive resolution of a BGP NEXT_HOP before changing route selection preferences or assuming a received prefix is usable.
- 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.
- Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
Explanation
Correct Answer
A:The case-specific routing and services action is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
Incorrect Answers
B: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 best-path attributes and local preference.
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 best-path attributes and local preference.
D: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 best-path attributes and local preference.
Question 137
A provider routing design review considers this situation. After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower. A colleague proposes: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. Which technical principle BEST supports that action? Select ONE best answer.
- BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters.
- An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state.
- 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.
- BGP FlowSpec conveys traffic match and action rules through BGP signaling, but their enforcement, validation, supported match fields and authorization must be controlled.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: BGP selects eligible routes according to an ordered decision process; provider-assigned local preference can override a shorter AS path and operational policy matters. In the described provider-network case (After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower.), it supports the planned action: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
Incorrect Answers
B:This alternative proposes: An LDP-signaled pseudowire uses locally and remotely agreed circuit identifiers, transport paths and VC labels; mismatched endpoints or identifiers can prevent service Up state. It concerns a different Junos engineering issue LDP signaled Layer 2 circuit pseudowire status and VC identifiers, not the directly tested provider-network issue BGP best-path attributes and local preference.
C: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 best-path attributes and local preference.
D: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 best-path attributes and local preference.
Question 138
A Juniper service-provider engineer needs decisive verification evidence for this situation. After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
- Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution.
- 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.
- Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic.
Explanation
Correct Answer
A:The direct discriminating observation is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. In the stated situation (After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower.), the intended acceptance outcome is: The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
Incorrect Answers
B:This alternative proposes: Compare selected BGP attributes, multipath configuration, show route next-hop entries, route preferences and forwarding table resolution. It concerns a different Junos engineering issue BGP multipath equal cost and per-flow forwarding, not the directly tested provider-network issue BGP best-path attributes and local preference.
C: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 best-path attributes and local preference in the stated situation (After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower.). A better case-specific check is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. The more targeted action is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
D:This alternative proposes: Inspect input and output policing bindings, configured CIR and burst allowance, drop counters, queue depth and throughput of representative traffic. It concerns a different Junos engineering issue CoS policers traffic-shaping and committed-rate contracts, not the directly tested provider-network issue BGP best-path attributes and local preference.
Question 139
A service-provider acceptance team reviews the result of a provider-service change. After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower. The intended verification is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution. 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.
- Subscribers receive the intended group from approved sources and traffic continues after a tested RP or upstream path change.
- The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
- Traffic shares suitable eligible next hops according to supported hashing behavior and fails over without blackholing during neighbor loss.
Explanation
Correct Answer
C:The verified success outcome is: The approved egress wins for the expected prefix for documented policy reasons, with a valid alternate when the preferred transit fails.
Incorrect Answers
A:That option concerns BGP export import policy and prefix controls. The related controlled intervention is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
B:That option concerns PIM sparse mode rendezvous point and shared tree operation. The related controlled intervention is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
D:That option concerns BGP multipath equal cost and per-flow forwarding. The related controlled intervention is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
Question 140
A Junos service-provider routing engineer investigates this service-provider network scenario. After a transit migration an engineer expects the neighbor with the smallest MED to win even though its local-preference policy is deliberately lower. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Plan VPLS multihoming with supported service site identifiers, redundancy roles and failover controls to avoid a duplicate active attachment loop.
- 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.
- Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins.
- Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
Explanation
Correct Answers
D:The case-specific routing and services action is: Evaluate competing BGP paths with local preference, AS path, origin, MED and next-hop reachability rather than assume shortest AS path always wins. Verify the decision through: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
E:The direct discriminating observation is: Review show route protocol bgp extensive, route hidden reasons, local preference, AS paths, origin, MED comparison context and BGP next-hop resolution.
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 best-path attributes and local preference.
B: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 best-path attributes and local preference.
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 BGP best-path attributes and local preference.