In an IS-IS Network Entity Title (NET), which portion identifies the area?

The entire NET identifies the area.

You are troubleshooting a routing issue in an IS-IS network. A Level 2 router in the backbone is not able to reach a loopback address of a Level 2 router in a different area. Both routers are configured with the same area address. What is the most likely cause of this issue?

The Level 2 routers are in different areas, so they cannot form a Level 2 adjacency.

The Level 2 routers are using different SPF calculations for Level 1 and Level 2, causing a routing loop.

The Level 2 link-state database does not contain the loopback address because it is not advertised in a Level 2 LSP.

The Level 2 routers are not forming a Level 2 adjacency because their NETs are not unique.

How does a Level 1/Level 2 router handle routing information between the two levels?

It maintains separate link-state databases for Level 1 and Level 2 and uses them independently for routing decisions.

It merges the Level 1 and Level 2 databases into a single database to simplify routing.

It only uses the Level 2 database for all routing decisions.

It advertises all Level 1 routes into Level 2 and all Level 2 routes into Level 1.

In IS-IS, what is the fundamental purpose of the two-level hierarchy?

To separate routing information within an area from routing information between areas, improving scalability.

To allow different routing protocols to be used within different areas.

To provide redundancy by maintaining two identical copies of the link-state database on every router.

To enable routers to choose between OSPF and IS-IS based on area size.

A company has a large Level 1 area with multiple Level 1/Level 2 border routers connecting to the backbone. The network team wants to ensure that traffic from the Level 1 area to a specific destination in another area uses the optimal border router, rather than always using the nearest one. What should be configured?

Configure the Level 1 routers with static routes to the destination.

Configure the border routers to prefer the nearest Level 1 router.

Configure the Level 1 routers as Level 2 routers to get full visibility.

Configure route leaking from Level 2 to Level 1 on the border routers.

Juniper NetworksCertified Professional, Service Provider Routing and Switching (JNCIP-SP)

Domain 2Objective 2

Areas and Levels JN0-664 Practice Questions (Page 2)

Part of the IS-IS domain, which makes up ~18% of our current practice bank. Juniper Networks does not publish an official question count, but from its 90-minute exam (~35–60 total, ~6–11 in this domain), expect 1–1 from this objective — we provide 21 practice questions to prepare you well beyond it. (estimate)

21questions here

5free pages

10concepts

Questions 6–10

6foundation · easy
In an IS-IS Network Entity Title (NET), which portion identifies the area?
Select an answer first
7application · medium
You are troubleshooting a routing issue in an IS-IS network. A Level 2 router in the backbone is not able to reach a loopback address of a Level 2 router in a different area. Both routers are configured with the same area address. What is the most likely cause of this issue?
Select an answer first
8foundation · easy
How does a Level 1/Level 2 router handle routing information between the two levels?
Select an answer first
9foundation · easy
In IS-IS, what is the fundamental purpose of the two-level hierarchy?
Select an answer first
10application · medium
A company has a large Level 1 area with multiple Level 1/Level 2 border routers connecting to the backbone. The network team wants to ensure that traffic from the Level 1 area to a specific destination in another area uses the optimal border router, rather than always using the nearest one. What should be configured?
Select an answer first

Finished these 5 questions?

Review the revealed explanations, or continue through the curriculum.

Next 5 questions →Back to JN0-664

Free Basic Practice is a study aid with revealable answers — not a scored exam. Examers.io is independent and not affiliated with or endorsed by Juniper Networks. “JN0-664” is a trademark of its owner, used for identification only.