4A0-101 Alcatel-Lucent Interior Routing Protocols and High Availability Questions and Answers

True

False

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

The MTU does not match on both interfaces

OSPF is not enabled on one of the routers

The Router ID is the same on both routers

A OSPF Hello has not been received from the neighbor

Metric is cost based

Slow convergence

Automatic summarization

Support CIDR

config > filter# default-action XXX

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

config > filter# default-mode XXX

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

Full; both routers are exchanging Helios to maintain the adjacency.

The adjacency is down.

The adjacency is in exstart state.

The adjacency is in the exchange state.

A policy statement within the router identifying what is to be advertised

Access-lists denoting what is to be advertised

Default metrics for each link

A group and neighbor statement for each peer

224.0.0.5

224.0.0.6

The unicast IP address of the interface the update is being sent on.

The system address of the router

0

5

10

15

In multi-access networks, a DR and BDR are elected only if there are more than two routers connected to the network segment.

In multi-access networks, a DR and BDR are elected only if the subnet masks on the router interfaces are less than /30

In multi-access networks, a DR and BDR are elected. To ensure resiliency, both the DR and BDR send link-state advertisements describing the network.

In multi-access networks, a DR and BDR are elected. The DR sends link-state advertisements describing the network.

Broadcast

Non-Broadcast Multi-Access

Point-to-Point

Point-to-Multipoint

IP packets sent to an IP multicast address.

Ethernet frames sent to an Ethernet multicast address.

IP packets sent to an IP unicast address.

UDP packets sent to an IP multicast address.

89

87

85

83

The system ID

The loopback address

The sequence number of the hello packet

The device that first initiated communication becomes the DIS

L1/L2 adjacency with router R2.

L1 adjacency with router R3

L2 adjacency with router R2

L1 adjacency with router R3

L1/L2 adjacency with router R2

L1/L2 adjacency with router R3

L1/L2 adjacency with router R2.

L1 adjacency with router R4

L1 adjacency with router R3

The protocol field of the transport layer header.

The port field of the transport layer header.

The protocol field of the network layer header.

The port field of the network layer address.

show router ospf area < area-id >

show router ospf neighbor

show router ospf interface

show router ospf status

An OSPF type 3 LSA is an intra-area LSA, generated by the ABR only when route summarization is configured.

An OSPF type 3 LSA is an inter-area LSA, generated by the ABR only when route summarization is configured.

An OSPF type 3 LSA is an inter-area LSA, generated by an ASBR to describe external routes.

An OSPF type 3 LSA is an inter-area LSA, generated by the ABR to describe a route to neighbors outside the area.

The adjacency state is two way because both routers have received a database description packet.

The adjacency is in the exchange state. The next step is to exchange link state request and link state update packets.

The adjacency is in the ex start state. The routers have exchanged database description packets, but still have to negotiate the starting sequence number.

The adjacency state is full. The routers are exchanging database description packets to notify each other that all link state advertisements have been received.

Routers broadcast the entire route table to all neighbors.

Information about directly connected links is sent to all neighbors.

An adjacency database is maintained by each router.

The sequence number for an update is incremented as it is flooded from router to router.

The topological database is the same for all routers in a single area.

The OSPF internal preference

The IS-IS Level 1 internal preference

The IS-IS Level 2 internal preference

The OSPF external preference

The IS-IS Level 2 external preference

The IS-IS Level 1 external preference

As soon as the LSP is transmitted.

When an acknowledgment is received in the form of PSNP.

When an older LSP is received.

When a newer or same aged LSP is received.

Only when a newer LSP is received

Initializing

Up

Down

2-Way

Fast reroute capability

Control traffic prioritization

Route redistribution

Traffic engineering extensions

Cut through forwarding

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.

When a link state update is received in response to a link state request.

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

When a router receives a database description packet from a neighbor.

When a link state acknowledgement is received in response to a link state update.

CSNPs are used to maintain consistency in the link state database.

CSNPs are advertised before an adjacency is formed with another router.

There are two types of CSNPs: Level 1 and Level 2.

CSNPs are advertised after an adjacency is formed with another router.

Router R3 ' s routing table can only contain one of the routes, which will result in route flapping.

Router R3 ' s routing table will have one entry for 10.1.1.0/24 and one entry for 10.1.2.0/24.

The networks will be represented with one entry of 10.0.0.0/8 in router R3 ' s routing table.

The networks will be represented with one entry of 10.0.0.0/24 in router R3 ' s route table.

The system ID.

The loopback address.

The sequence number of the Hello packet.

The device that first initiated communication becomes the DIS

The highest interface MAC address.

traceroute 10.2.3.1

traceroute 10.2.3.1 next-hop 10.1.2.1

traceroute next-hop 10.1.2.1

traceroute does not work on the Alcatel-Lucent 7750 SR.

traceroute 10.1.2.1

The term backbone router has the same definition as the term area border router.

An OSPF network needs at least one area border router to function.

Area border routers connect the backbone area to other areas in an OSPF network.

By definition, an area border router must perform route summarization between areas.

The router R6 interface is in a multi-access segment. It is neither the DR nor the BDR for the segment. The DR for this segment would be the router with router ID 10.10.10.5.

The router R6 interface is in a multi-access segment. It is neither the DR nor the BDR for the segment; however, this command does not indicate whether 10.10.10.3 or 10.10.10.5 is the DR or BDR.

The router R6 interface is in a multi-access segment. It is the BDR, which is why it is not adjacent to the other routers.

The router R6 interface is in a multi-access segment. It is neither the DR nor the BDR for the segment. The DR for this segment would be the router with router ID 10.10.10.3.

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

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.

' asbr ' is missing from router R1 ' s configuration.

Router R1 needs to have an export policy added to it.

Router R5 does not have an export policy for these prefixes.

Router R1 needs to have an import policy added to it.

There is no route leaking configured on router R1 or router R2.

Route leaking is configured on router R1 but not on router R2.

Route leaking is configured on router R2 but not on router R1.

Route leaking is configured on both router R1 and router R2.

0

1

2

3

4

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 R3 will install the OSPF route in its routing table.

Router R3 will install the IS-IS route in its routing table

Router R3 will install an OSPF route and an IS-IS route in its routing table.

There is not enough information to answer the question.

Stub must be configured on Area 1 of router R1, and removed from Area 1 on router R3.

Stub must be configured on Area 1 of router R1 and Area 1 of router R3.

Stub must be configured on Area 0 of router R1 and Area 1 of router R3.

Area 1 of router R3 should be Area 0, in order to connect via stub to router R1.

Type 1 Router LSA

Type 2 Network LS A

Type 3 Summary LSA

Type 5 External LSA

Backbone

NSSA

Stub

Totally stubby

The IPv6 header has a header checksum field, header length field and no fragmentation offset field.

The IPv6 header has no header checksum field, no header length field and does have a fragmentation offset field.

The IPv6 header has a header checksum field, no header length field and no fragmentation offset field.

The IPv6 header has no header checksum field, no header length field and no fragmentation offset field.

2

3

4

5

6

7

Link

Intra-Area Prefix

Inter-Area Prefix

Inter-Area Router

On the CEs only.

On the PEs only.

On only the branch office CE.

On both the CEs and PEs.

Router R2 to router R8 will follow (R2-R3-R5-R7-R8). Router R8 to R2 will follow (R8-R7-R5-R3-R2)

Router R2 to router R8 will follow (R2-R3-R4-R6-R7-R8). Router R8 to R2 will follow (R8-R7-R6-R4-R3-R2)

Router R2 to router R8 will follow (R2-R3-R5-R7-R8). Router R8 to R2 will follow (R8-R7-R6-R4-R3-R2)

Router R2 to router R8 will follow (R2-R3-R4-R6-R7-R8) Router R8 to R2 will follow (R8-R7-R5-R3-R2)

The router with the least number of links.

The router with the lowest router ID.

The router ' s closest neighbor.

The router doing the calculation.

OSPFv3 uses MD5 Authentication.

Router LSAs carry IPv6 prefix information.

NSSA is supported in OSPFv3.

OSPFv3 uses a 64-bit router ID.

10.10.10.2

10.10.10.3

10.10.10.6

There is not enough information given to determine the designated router.

The router has a system interface, two point-to-point interfaces and one broadcast interface.

The router has a system interface, two passive interfaces, two point-to-point interfaces and one broadcast interface.

The router has a system interface, two point-to-point interfaces and one virtual link.

The router has a system interface, two passive interfaces, two point-to-point interfaces and one virtual link.

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.

Router LSA

Network LSA

Inter-Area Prefix LSA

Link LSA

PSNPs are used on point-to-point links to acknowledge the receipt of an LSP.

There are three types of PSNPs: Level 1, Level 2, and Level 1/2.

A PSNP lists some of the LSPs in the router ' s database.

PSNPs are used by an IS-IS router to request LSP information from a neighboring router.

Router R4 will have a route to router R6 ' s system address with router R2 as the next-hop.

Router R4 will have a default route with router R2 as the next-hop.

Router R4 will have a default route with router R3 as the next-hop.

Router R4 will not have a route to router R6 ' s system address, nor will it have a default route.

The router ' s system address.

The next-hop prefix.

The interface ' s global prefix.

The next-hop system address.

A route from IS-IS.

A route from OSPF.

A floating static route.

A static route.

Fast reroute capability.

Control traffic prioritization.

Route redistribution.

Traffic engineering extensions.

Cut through forwarding.

Link

Intra-Area Prefix

Inter-Area Prefix

Inter-Area Router

Next Header

Traffic Class

Hop Limit

Fragment Offset

Flow Label

There are five broadcast links and there are no point-to-point links.

There are five broadcast links and there are five point-to-point links.

There are five broadcast links. It ' s not possible to say how many point-to-point links there are.

It ' s not possible to say how many broadcast or point-to-point links there are.

The current DR is selected, if there is one. Otherwise, the router with the lowest priority is the DR. If priorities are the same, the DR is chosen based on the lowest RID.

The current DR is selected, if there is one. Otherwise, the router with the highest priority is the DR. If priorities are the same, the DR is chosen based on the highest RID.

The router with the lowest priority is the DR. If priorities are the same, the current DR is selected. Otherwise the DR is chosen based on the lowest RID.

The router with the highest priority is the DR. If priorities are the same, the current DR is selected. Otherwise the DR is chosen based on the highest RID.

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.

LSA flooding mechanism.

Totally stubby areas.

MD5 authentication.

DR and BDR election.

Router R2 needs a static route to the PC.

Router R2 needs a default to router R1.

Router R1 needs a default route to router R2.

The static route should use a next-hop of 172.31.1.2

configure router static-route 0.0.0.0/0 indirect 10.10.10.2

configure router static-route 0.0.0.0/0 indirect 2001:DB8:1:100::1

configure router static-route ::/0 indirect 10.10.10.2

configure router static-route::/0indirect2001:DB8:1:100::1

configure outer static-route::/0indirect2001:DB8:1:101::1

2001::FF:FE:14:6CAE

2001::1:FF:14:6CAE

FF02.DB8::30A:216:4DFF:FE14.6CAE

FF02::1:FF14:6CAE

They are Type 7 within the area and are not modified at the ABR.

They are Type 5 within the area and converted to Type 3 at the ABR.

They are Type 5 within the area and are not modified at the ABR.

They are Type 7 within the area and converted to Type 5 at the ABR.

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.

Router R3 will install the IS-IS route in it ' s routing table.

Router R3 will install the OSPF route in it ' s routing table.

Router R3 will install an OSPF route and an IS-IS route in it ' s route table.

There is not enough information to answer the question.

The destination IP address will be the system IP address of router R1 and the destination MAC address will be the MAC address of the router R1 port connected to the PC.

The destination IP address will be the IP address of the router R1 port connected to the PC and the destination MAC address will be the MAC address of the router R1 port connected to the PC.

The destination IP address will be the IP address of the server and the destination MAC address will be the MAC address of the server.

The destination IP address will be the IP address of the server and the destination MAC address will be the MAC address of the router R1 port connected to the PC.

Level 0

Level 1

Level 2

Level 0/1

Level 1/2

The system ID

The loopback address

The sequence number of the Hello packet

The device that first initiated communication becomes the DIS

The highest interface MAC address

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

The router is an ABR.

The router is an ASBR.

The router is at the end of a virtual link.

The router ' s interface is in a stub area.

config > static-route 0.0.0.0/0 next-hop 10.1.2.2

config > router > static-route 0.0.0.0 255.255.255.255 next-hop 10.1.2.1

config > router > static-route 0.0.0.0/0 next-hop 10.1.2.2

config > router > static-route 0 0.0 0/0 next-hop 10.1.2.1

With a Router LSA originated by R1

With a Router LSA originated by R5

With a Router LSA originated by R4

With an Inter-Area Prefix LSA originated by R1

With an Inter-Area Prefix LSA originated by R5

With an Inter-Area Prefix LSA originated by R4

The corporate head office router should have a default route and the branch site should have a more specific static route

The corporate head office router and the branch office router should both have specific static routes.

The corporate head office router and the branch router should both have default routes.

The corporate head office router should have a specific static route and the branch office router should have a default route.

The router with router ID 10.10.10.5 is an ASBR.

The router with router ID 10.10.10.3 is an ASBR.

The router with router ID 10.10.10.5 originated the AS summary LSA in its own area.

The router with router ID 10.10.10.4 is in the same area as the router with router ID 10.10.10.5.

Route redistribution is only needed if Internet access is a requirement.

Route filtering is the process of attaching data path filters to router interfaces.

Route filtering involves deciding whether to permit or deny certain routing updates from being accepted into, or distributed out of, the route-selection process.

Redistribution is needed for exchanging routes from one routing protocol to another.

OSPF routers that are redistributing routes must be configured as ABRs.

Configuring IS-IS interfaces

Enabling IS-IS

Configuring level capabilities

Specifying an area address

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.

The router sends a link-state update to its neighbor.

The router sends a link-state acknowledgement to its neighbor.

The router updates the information in its LSDB with the information received from its neighbor.

The router sends a link-state request to its neighbor.

The router takes no action.

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 OSPF internal preference

The IS-IS Level 1 internal preference

The IS-IS Level 2 internal preference

The OSPF external preference

The IS-IS Level 2 external preference

The IS-IS Level 1 external preference

Hellos, CSNPs, PSNPs

LSPs. Hellos, CSNPs

LSPs, PSNPs, Hellos

LSPs, CSNPs, PSNPs

The system interface is configured with IPv6 address 2001DB8 1:100:1/128

All interfaces are configured for IPv4 and IPv6.

Interface " toR2 " is configured with a globally routed IPv6 address.

Interface " toR3 " is not configured for IPv6 with a global IPv6 address.

IPv6 uses the Address Resolution Protocol to resolve the address to a MAC address.

A Neighbor Discovery message is sent to the broadcast MAC address. The host with the IPv6 address responds with a Neighbor Advertisement message.

A Neighbor Discovery message is sent to the solicited-node multicast address. The host with the IPv6 address responds with a Neighbor Advertisement message.

A Neighbor Discovery message is sent to the anycast address for the LAN. The host with the IPv6 address responds with a Neighbor Advertisement message.

IPv6 addresses do not need to be resolved to a MAC address.

1

2

3

4

6

7