Configure, Monitor, or Troubleshoot IS-IS Levels, Interfaces, and Adjacencies JN0-352 Practice Questions (Page 2)

Questions 6–10

1. 6application · easy

   A network engineer is configuring IS-IS on a Juniper router. The router has a loopback interface (lo0.0) and a physical interface (ge-0/0/0.0) connected to an IS-IS neighbor. The engineer wants to ensure that the loopback address is advertised into IS-IS but does not want to form any adjacencies over the loopback. What configuration should be applied to the loopback interface?

   • ASet the interface level to Level 2 only.
   • BDisable IS-IS on the loopback interface.
   • CSet the interface metric to a high value.
   • DSet the interface to passive.
   Reveal Solution Discussion Select an answer first
2. 7foundation · easy

   Which show command would you use to verify the state of IS-IS adjacencies on a router?

   • Ashow isis interface
   • Bshow isis adjacency
   • Cshow route protocol isis
   • Dshow isis database
   Reveal Solution Discussion Select an answer first
4. 8foundation · easy

   What is a common cause of IS-IS adjacency failure on a broadcast interface?

   • AThe interface is configured as passive.
   • BThe router's system ID is not unique.
   • CThe interface is not assigned an IP address.
   • DThe router's hostname is too long.
   Reveal Solution Discussion Select an answer first
5. 9foundation · easy

   Which statement correctly describes the relationship between IS-IS areas and Level 2 routing?

   • ALevel 2 routers are confined to a single area and cannot route between areas.
   • BLevel 2 routers form a contiguous backbone that interconnects areas, and Level 1-2 routers connect Level 1 areas to this backbone.
   • CLevel 2 routers are only used in multi-area OSPF networks, not in IS-IS.
   • DLevel 2 routing occurs within a single area, providing detailed routing information to Level 1 routers.
   Reveal Solution Discussion Select an answer first
6. 10expert · hard

   Two routers, R1 and R2, are connected via a point-to-point link. IS-IS is configured on both, and the adjacency is up. However, the network team notices that the adjacency is flapping every few minutes. The 'show log messages' on R1 shows the following message repeatedly: 'IS-IS LDP synchronization: neighbor 192.168.1.2 is down'. What is the MOST likely cause of this issue?

   • AThe IS-IS hold time is set too high on R2.
   • BThe IS-IS hello interval is set too low on R1.
   • CThe IS-IS interface is configured with a passive mode.
   • DThe LDP session between R1 and R2 is flapping, causing IS-IS to bring the adjacency down.
   Reveal Solution Discussion Select an answer first