4A0-101 Nokia Interior Routing Protocols Questions and Answers

The router sends a copy of the LSP from its database to its neighbor

The router sends a PSNP to its neighbor describing the LSP in its database.

The router updates its database with the LSP and floods a copy to its other neighbors.

The router sends a PSNP to its neighbor to request the LSP.

Exchange

Up

Down

2-Way

L1 routers

L2 routers

L1/L2 routers

L1 and L2 routers

A Type 4 LSA is originated by an ABR to describe a route to an ASBR to routers outside the area.

A Type 4 LSA is originated by an ASBR to describe a route to itself to routers outside the area.

A Type 4 LSA is originated by an ABR that is connected to a stub area. The LSA is injected into the backbone area to provide routing information.

A Type 4 LSA is originated by an ABR that is connected to a stub area. The LSA is injected into the stub area to provide routing information.

The routing information base (RIB).

The routing table manager (RTM).

The equal cost multipath configuration (ECMP).

The forwarding information base (FIB).

The link state database (LSDB).

The router sends a copy of the LSP from its database to its neighbor

The router updates its database with the LSP and floods a copy to its other neighbors.

The router updates its database with the LSP, acknowledges the LSP with a PSNP and floods a copy to its other neighbors.

The router updates its database with the LSP and acknowledges it with a PSNP.

IS-IS supports VLSM and CIDR.

IS-IS uses OSI addressing.

IS-IS supports manual summarization

IS-IS uses periodic Hello messages.

The router with the highest system ID.

The router with the highest loopback address.

The Hello packet with the highest sequence number.

The existing DIS remains the DIS.

The router with the highest interface MAC address.

Type 1 Router LSA

Type 2 Network LS A

Type 3 Summary LSA

Type 5 External LSA

A Type 4 LSA is originated by an ABR to describe a route to an ASBR to routers outside the area.

A Type 4 LSA is originated by an ASBR to describe a route to itself to routers outside the area.

A Type 4 LSA is originated by an ABR that is connected to a stub area. The LSA is injected into the backbone area to provide routing information.

A Type 4 LSA is originated by an ABR that is connected to a stub area. The LSA is injected into the stub area to provide routing information.

The area ID does not have to match.

The value of the E bit in the options field does not have to match.

The value of the Hello interval does not have to match.

The value of the network mask does not have to match.

The area ID, the E bit value, the Hello interval and network mask must all match.

Router R6 will have a single Router LSA that describes the summary prefix.

Router R6 will have three Router LSAs - one to describe each loopback prefix.

Router R6 will have a single Inter-Area Prefix LSA to describe the summary prefix.

Router R6 will have three Inter-Area Prefix LSAs - one to describe each loopback prefix.

Router R6 will not have any LSAs to describe the loopback prefix or the summarized prefix.

Router R2 has two IS-IS adjacencies and two LSPs

Router R2 has two IS-IS adjacencies and three LSPs

Router R2 has two IS-IS adjacencies and four LSPs

Router R2 has three IS-IS adjacencies and three LSPs

Router R2 has three IS-IS adjacencies and four LSPs

Router R2 has three IS-IS adjacencies and six LSPs

The primary and backup routes are to the same destination.

The primary and backup routes appear in the routing table.

The backup route is configured with a higher preference value.

The next-hop of the primary and backup routes are different.

Default path

Default gateway

Gateway path

Proxy ARP

The age for newly created link state information is set to 0 for OSPF and 1200 for IS-IS

The age for newly created link state information is set to 1200 for OSPF and 0 for IS-IS

The age is incremented or decremented as it is flooded from router to router and as it is held in the topological database.

The age is incremented or decremented only as it is held in the topological database and not as it is flooded router to router.

There is nothing wrong with this filter

The filter should be applied to the ingress and not the egress.

The mask cannot be a "/" value, it must be in dotted decimal.

All traffic is being blocked

Show route-table

Show router routing-table

Show router route-table

Show static

config>filter# default-action XXX

config>filter>ip-filter# default-action XXX

config>filter# default-mode XXX

config>filter>ip-filter# default-mode XXX

DSCP marking

Class of Service Marking

DSAP marking

ICMP type

None

1

2

3

4

Area Border Router

Autonomous System Boundary Router

Designated Router

All routers within an OSPF area.

Hello, link state update, link state packet, link State acknowledgement, database description.

Link state update, link state refresh, link state acknowledgement, database description, notification.

Hello, link state refresh, link state update, link state acknowledgement, link state authentication.

Hello, link state update, link state request, link state acknowledgement, database description.

Metric is based on hop count.

Slow convergence after link failures.

Support hierarchy through the use of areas.

Support for CIDR.

Link state updates sent using layer 3 multicast.

49.0012.1234

49.0012

12.1234

1234

49.1234

There are three types of LSPs: L1, L2 and L1/L2.

An LSP packet contains the ATT bits and the IS-type bits.

The lower the LSP sequence number, the more current the update.

Separate databases are maintained for L1 „ L2, and L1/L2 LSPs.

Not so stubby areas

Level1 area WC

Stub areas

Partially stubby areas

Level 2 areas

Area ID W B.

Hello and Dead intervals PC.

Stub flag

Checksum values

The list of neighbors

Router R1 generates a type 4 LSA that is flooded to areas 0, 1, and 2.

Router R3 generates a type 4 LSA that is flooded to areas 0, 1, and 2.

Router R3 generates a type 4 LSA that is flooded to areas 0 and 2.

Router R3 generates a type 4 LSA that is flooded to area 0, and router R6 generates a type 4 LSA that is flooded to area 2.

Option A

Option B

Option C

Option D

MTU mismatch

Incorrect subnet mask

System interface not included in OSPF

Area ID not the same

Different metric set on each end of the link

Router ID not defined

Use an import policy and a prefix list on router R2.

Use an export policy and a prefix list on router R1.

Use an import policy and a prefix list on router R1.

Router R1 cannot discard the route because IS-IS does not support import policies.

An L1/L2 router can have adjacencies with routers in different areas.

An L1/L2 router calculates separate SPF trees for the Level 1 and Level 2 topology.

An L1/L2 router advertises its L2 routes to other L1 routers in the same area.

An L1/L2 router sets the ATT bit in L1 LSPs to indicate that it has routes to other areas.

Add the "originate-default-route" option in the NSSA area configuration on router R3.

Add the "summaries" option to the NSSA area configuration on router R1.

Configure a static route on router R1 to 192.168.3.1.

Configure a default route on router R2.

It discards packets based on the source address.

It discards packets that match the destination prefix.

It returns ICMP unreachable messages.

It discards packets based on the egress port.

The router receives a link-state update in response to a link-state request.

The router receives a Hello packet from its neighbor that contains its own router ID in the neighbor list.

The router receives a database description packet from its neighbor.

The router receives a link-state acknowledgement in response to a link-state update

With a Router LSA originated by router R1.

With a Router LSA originated by router R5.

With a Router LSA originated by router R4.

With an Inter-Area Prefix LSA originated by router R1.

With an Inter-Area Prefix LSA originated by router R5.

With an Inter-Area Prefix LSA originated by router R4.

Hello

Link-state request

Link-state acknowledgment

Link-state update

Database description

Type 1

Type 2

Type 3

Type 4

Type 5

1

10

100

1000

When link-state information reaches the maximum age on a router, the router will flood that information to its neighbors.

When a router detects that any of its link-state information has reached the maximum age, it will request a new update from the source router.

Aging helps ensure that links, which are no longer part of the topology, will eventually get removed from the LSDB.

The age value is updated as the information is flooded throughout the network and when it is in the LSDB.

When a router receives updates from its neighbors, it adds them to its link state database, performs an SPF computation, and sends the results to its neighbors.

An SPF computation is done by each router to determine the best path to destination networks. All the best paths determined by the SPF calculation will be seen in the route table.

Each router constructs its own link state database with updates received from neighbors.

An SPF computation is done by each router to determine the best path to destination networks. All the best paths determined by the SPF calculation will be offered to the route table manager.

Next Header

Traffic Class

Flow Label

Payload Length

Options

Data traffic from network 192.168.1.0/24 to 192.168.3.0/24 will be forwarded through router R2.

Data traffic from network 192.168.3.0/24 to 192.168.1.0/24 will be forwarded through router R2.

The system interface of routers R1 and R3 must be included into OSPF for traffic to flow between the 192.168.1.0/24 and 192.168.3.0/24 networks.

The OSPF adjacency between router R1 and router R3 is operationally down.