Juniper JN0-664 Practice Test 10
Question 90
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. During link repair, a newly added higher-priority IS-IS router becomes DIS and technicians confuse the normal pseudonode update with a data-plane attack. 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.
- Treat an IS-IS DIS as permanently paired with a mandatory BDR and declare the broadcast domain broken when a backup election is not shown.
- Advertise the same RP anycast address from two routers without configuring or verifying required RP-state coordination and call the design fully resilient.
- Expect two pure Level 1 routers in different IS-IS areas to exchange routes directly across the core without an eligible Level 2 path.
Explanation
Correct Answer
B:Apply instead: Validate Designated Intermediate System behavior on a LAN segment rather than confusing it with the OSPF DR/BDR algorithm.
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 DIS pseudonode and broadcast circuit election.
C:This alternative proposes: Advertise the same RP anycast address from two routers without configuring or verifying required RP-state coordination and call the design fully resilient. It concerns a different Junos engineering issue Anycast RP resilient multicast service and routing policy, not the directly tested provider-network issue IS-IS DIS pseudonode and broadcast circuit election.
D: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 DIS pseudonode and broadcast circuit election.
Question 91
A Junos service-provider routing engineer investigates the following routing and service incident: Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Investigate an OSPF adjacency that remains in ExStart or Exchange by comparing interface MTU and protocol parameters before resetting every neighbor.
- Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior.
- Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
- Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP.
Explanation
Correct Answer
C:The case-specific routing and services action is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange. The governing Junos routing/service principle is: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths.
Incorrect Answers
A: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 IS-IS link-state packet flooding and database consistency.
B: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 IS-IS link-state packet flooding and database consistency.
D:This alternative proposes: Investigate rejected or down IS-IS adjacencies by verifying circuit levels, IS-IS NET identifiers, authentication and interface MTU before changing the full IGP. It concerns a different Junos engineering issue IS-IS adjacency NET and interface mismatch troubleshooting, not the directly tested provider-network issue IS-IS link-state packet flooding and database consistency.
Question 92
A provider routing design review considers this situation. Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment. A colleague proposes: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange. Which technical principle BEST supports that action? Select ONE best answer.
- IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths.
- 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.
- IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient.
- 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.
Explanation
Correct Answer
A:The relevant Junos service-provider networking principle is: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths. In the described provider-network case (Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment.), it supports the planned action: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
Incorrect Answers
B: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 IS-IS link-state packet flooding and database consistency.
C:This alternative proposes: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. It concerns a different Junos engineering issue IS-IS adjacency NET and interface mismatch troubleshooting, not the directly tested provider-network issue IS-IS link-state packet flooding and database consistency.
D: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 IS-IS link-state packet flooding and database consistency.
Question 93
A Juniper service-provider engineer needs decisive verification evidence for this situation. Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
- Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits.
- Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs.
- Inspect show bgp neighbor advertised/received family capabilities, relevant family statements, VPN/EVPN route tables, route-target policy and next-hop reachability.
Explanation
Correct Answer
A:The direct discriminating observation is: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. In the stated situation (Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment.), the intended acceptance outcome is: Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
Incorrect Answers
B:This alternative proposes: Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits. 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 link-state packet flooding and database consistency.
C:This alternative proposes: Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs. 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 link-state packet flooding and database consistency.
D: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 IS-IS link-state packet flooding and database consistency.
Question 94
A service-provider acceptance team reviews the result of a provider-service change. Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment. The intended verification is: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. Which outcome BEST demonstrates success? Select ONE best answer.
- Neighbor state reaches Up at the expected level and routing recovers without exposing a different operator's area or changing every circuit.
- Traffic prefers the engineered feasible lower-cost path and uses a documented alternate when a critical link fails.
- Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
- Subscribers receive the intended group from approved sources and traffic continues after a tested RP or upstream path change.
Explanation
Correct Answer
C:The verified success outcome is: Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations. Confirm this by: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
Incorrect Answers
A:That option concerns IS-IS adjacency NET and interface mismatch troubleshooting. The related controlled intervention is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
B:This alternative proposes: Traffic prefers the engineered feasible lower-cost path and uses a documented alternate when a critical link fails. 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 link-state packet flooding and database consistency.
D:That option concerns PIM sparse mode rendezvous point and shared tree operation. The related controlled intervention is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
Question 95
A Junos service-provider routing engineer investigates this service-provider network scenario. Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment. Which TWO complementary steps combine a suitable technical action and its direct verification? Select TWO answers.
- Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event.
- Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
- Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
- Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits.
- 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: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
C:The case-specific routing and services action is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange. The governing Junos routing/service principle is: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths. Verify the decision through: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
Incorrect Answers
A:This alternative proposes: Use BGP route damping conservatively and verify whether instability penalties suppress otherwise available paths during a customer route-flap event. It concerns a different Junos engineering issue BGP flap damping penalties and recovery, not the directly tested provider-network issue IS-IS link-state packet flooding and database consistency.
D:This alternative proposes: Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits. 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 link-state packet flooding and database consistency in the stated situation (Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment.). A better case-specific check is: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
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 IS-IS link-state packet flooding and database consistency in the stated situation (Two core routers have an IS-IS adjacency but one route remains absent after a burst of dropped control packets on a multiaccess segment.). A better case-specific check is: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. The more targeted action is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
Question 96
A Junos service-provider routing engineer investigates the following routing and service incident: A router receives an older LSP copy and the team treats the lower sequence record as the authoritative current network state without checking flooding. What is the MOST appropriate FIRST action based on the facts given? Select ONE best answer.
- Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
- Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability.
- Check whether the deployed IS-IS metric style and link costs support the provider's intended routing and traffic-engineering behavior.
- Apply explicit import and export routing-policy terms to control which customer or upstream prefixes enter the provider BGP routing domain.
Explanation
Correct Answer
A:The case-specific routing and services action is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
Incorrect Answers
B:This alternative proposes: Restrict interlevel IS-IS route advertisements to the intended prefixes with controlled L1/L2 policy and verify return reachability. 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 IS-IS link-state packet flooding and database consistency.
C: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 IS-IS link-state packet flooding and database consistency.
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 IS-IS link-state packet flooding and database consistency.
Question 97
A provider routing design review considers this situation. A router receives an older LSP copy and the team treats the lower sequence record as the authoritative current network state without checking flooding. A colleague proposes: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange. Which technical principle BEST supports that action? Select ONE best answer.
- IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient.
- Route reflectors relax the default prohibition against propagating iBGP-learned routes to other iBGP peers, with originator and cluster attributes limiting reflection loops.
- 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.
- IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths.
Explanation
Correct Answer
D:The relevant Junos service-provider networking principle is: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths. In the described provider-network case (A router receives an older LSP copy and the team treats the lower sequence record as the authoritative current network state without checking flooding.), it supports the planned action: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
Incorrect Answers
A:This alternative proposes: IS-IS hello compatibility requires suitable circuit level, area relation for Level 1, supported MTU/parameters and authentication; physical link Up alone is insufficient. It concerns a different Junos engineering issue IS-IS adjacency NET and interface mismatch troubleshooting, not the directly tested provider-network issue IS-IS link-state packet flooding and database consistency.
B: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 IS-IS link-state packet flooding and database consistency.
C: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 IS-IS link-state packet flooding and database consistency.
Question 98
A Juniper service-provider engineer needs decisive verification evidence for this situation. A router receives an older LSP copy and the team treats the lower sequence record as the authoritative current network state without checking flooding. Which observation MOST DIRECTLY distinguishes the relevant issue? Select ONE best answer.
- Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path.
- Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits.
- Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs.
- Check BGP flap statistics, suppression/reuse states, policy settings, hidden route reasons, alternative routes and customer incident history.
Explanation
Correct Answer
A:The direct discriminating observation is: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. In the stated situation (A router receives an older LSP copy and the team treats the lower sequence record as the authoritative current network state without checking flooding.), the intended acceptance outcome is: Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
Incorrect Answers
B:This alternative proposes: Compare NET area addresses, circuit levels, show isis adjacency detail, L1 versus L2 route tables and the attached bit on designated exits. 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 link-state packet flooding and database consistency.
C:This alternative proposes: Inspect IS-IS metric configuration on both ends, extended TLV capability, show isis route, and SPF results before changing costs. 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 link-state packet flooding and database consistency.
D: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 IS-IS link-state packet flooding and database consistency.
Question 99
A service-provider acceptance team reviews the result of a provider-service change. A router receives an older LSP copy and the team treats the lower sequence record as the authoritative current network state without checking flooding. The intended verification is: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. Which outcome BEST demonstrates success? Select ONE best answer.
- Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations.
- 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.
- Access routers learn only authorized leaked routes, continue using their correct area exit and do not create interlevel routing loops.
Explanation
Correct Answer
A:The verified success outcome is: Neighbor databases converge on consistent current LSPs and the intended network prefixes resolve through matching shortest-path computations. Confirm this by: Compare show isis database, LSP sequence numbers, CSNP/PSNP exchange, interface errors and per-level adjacency status for the affected path. The related controlled intervention is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
Incorrect Answers
B:This alternative proposes: Traffic prefers the engineered feasible lower-cost path and uses a documented alternate when a critical link fails. 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 link-state packet flooding and database consistency.
C:That option concerns BGP flap damping penalties and recovery. The related controlled intervention is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
D:That option concerns IS-IS Level 2 to Level 1 route leaking and summaries. The related controlled intervention is: Diagnose divergent IS-IS topology by tracing LSP sequences, database scope and complete sequence-number packet exchange.
Question 100
A Junos routing design reviewer evaluates an unsafe shortcut in this network customer scenario. A router receives an older LSP copy and the team treats the lower sequence record as the authoritative current network state without checking flooding. Which assumption is MOST DIRECTLY dangerous or unsupported? Select ONE best answer.
- Treat a customer's multi-site VPN backdoor link as automatically equivalent to an OSPF intra-area backbone path and disable all route-loop safeguards.
- 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 a core link with more bandwidth automatically has the lowest IS-IS metric when no operator metric policy has been configured.
- Assume an IS-IS adjacency shown as Up proves every Level 1 and Level 2 LSP is synchronized, without inspecting database content.
Explanation
Correct Answer
D:That conflicts with the edge-to-cloud principle: IS-IS uses LSPs to distribute link-state topology and SNP mechanisms to synchronize databases; incomplete flooding can leave routers computing different SPF paths.
Incorrect Answers
A:This alternative proposes: Treat a customer's multi-site VPN backdoor link as automatically equivalent to an OSPF intra-area backbone path and disable all route-loop safeguards. It concerns a different Junos engineering issue Site of Origin and OSPF sham-link loop control, not the directly tested provider-network issue IS-IS link-state packet flooding and database consistency.
B:This alternative proposes: 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. It concerns a different Junos engineering issue IS-IS adjacency NET and interface mismatch troubleshooting, not the directly tested provider-network issue IS-IS link-state packet flooding and database consistency.
C: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 link-state packet flooding and database consistency.