4A0-C04 Nokia NRS II Composite Exam: OSPF version Questions and Answers

Option A

Option B

Option C

Option D

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.

config > router- confederation 65200 members 65202

config > router > bgp= confederation 65200 members 65202

config > router= confederation 65202 members 65200

config > router > bgp= confederation 65202 members 65200

The time router R2 takes to receive a PATH Error message from router R4.

The time router R2 takes to find out a number of RSVP Hello messages have been missed.

The time router R2 takes to send a PATH Tear message to the head-end router.

The time router R2 takes to receive a PATH message from router R4 after a PATH refresh interval.

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 path must include at least one hop.

The path may be used for multiple LSPs.

The path may be used multiple times in a single LSP.

The path must define a tunnel destination IP address.

show router ospf area < area-id >

show router ospf neighbor

show router ospf interface

show router ospf status

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

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.

An OSPF Hello has not been received from the neighbor.

The interfaces are configured as point-to-point on one side and broadcast on the other.

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

The original VLAN tag is removed.

The original VLAN tag is kept.

The VLAN tag is replaced by a provider tag.

The VLAN tag is kept and a provider tag is added.

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

Make a static route on router R1 to 192.168.3.1

Make a default route on router R2

Assign an admin group to a MPLS interface.

Configure CSPF on the LSP.

Configure at least one strict hop on the LSP path.

Configure an "include" or "exclude" statement on the LSP path.

Tunnel Label

VC Label

Operational Control Word

UNI

NNI

A PE uses the same VRF table for all the VPRN services on it.

A PE uses a VRF to maintain forwarding information.

Information for VRFs can be advertised between PEs by MP-BGP.

A PE uses a VRF to route traffic to CEs.

family ipv4 ipv6

family vpn-ipv4ipv6

family vpn-ipv4 vpn-ipv6

family ipv6 vpn-ipv6

Router R1 generates a type 5 LSA that is flooded through all OSPF areas.

Router R1 generates a type 7 LSA that is flooded through all OSPF areas.

Router R1 generates a type 5 LSA that is flooded through area 1. Router R2 generates a type 7 LSA that is flooded through areas 0 and 2.

Router R1 generates a type 7 LSA that is flooded through area 1. Router R3 generates a type 5 LSA that is flooded through areas 0 and 2.

IP packets sent to an IP multicast address.

TCP packets sent to an IP multicast address.

IP packets sent to an IP unicast address.

UDP packets sent to an IP multicast address.

Isp-trace

Idp-trace

Sdp-ping

Svc-ping

Ping

1

2

3

None

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

"ping 192.168.20.1"

"oam vprn-ping 100 source 192.168.10.1 destination 192.168.20.1"

"oam vprn-ping 100 source 192.168.20.1 destination 192.168.10.1"

"ping 10.10.10.6" (router R6's system IP)

The TC field is set based on the value of the DSCP field inside the customer packet.

The TC field is set to a specific value via explicit administrative configuration.

The TC field is set to a system generated random number.

The TC field is set by the eLER.

Conservative label retention

Liberal label retention

Downstream on demand

Downstream unsolicited

A new LDP session is established on R1-R3-R6 as soon as the FIB is updated.

The LDP session remains unchanged until the existing path R1-R2-R4-R6 goes down.

A new LDP session is established on R1-R3-R6 as soon as router R1 receives a new label for router R6.

The LDP session remains unchanged until router R3 stops advertising the maximum metric for the link to router R6.

The customer's Layer 3 header is removed at the iLER.

The customer's Layer 2 header is removed at the iLER.

The customer's Layer 3 header is removed at the eLER.

The customer's Layer 2 header is removed at the eLER.

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.

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.

True

False

They provide both peering and transit services.

They provide services only to Tier 1 service providers.

They can be either public or private.

They provide services at the local, regional and continental levels.

Tunnel Label

VC Label

Operational Control Word

VPI

VCI

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.

Enable fast-reroute on all routers along the path. R1, R2, R4, and R6.

Enable both link-protection and node-protection on router R1.

Enable fast-reroute with either one-to-one or facility mode on this LSP.

Enable link-protection only on router R4.

224.0.0.5

224.0.0.6

224.0.0.9

224.0.0.10

RIPv2 does not have support for multicast

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.

BGP Fast Reroute is triggered by IGP events.

The backup path is pre-computed and installed in the FIB.

BGP Fast Reroute is independent of number of affected prefixes.

BGP Fast Reroute uses the optimal path to the destination.

The inner label is the IPv4 Explicit Null. The outer label is the MPLS transport label,

The inner label is an MPLS transport label. The outer label is the IPv4 Explicit Null.

The inner label is the IPv6 Explicit Null. The outer label is an MPLS transport label.

The inner label is an MPLS transport label. The outer label is the IPv6 Explicit Null.

Priority of 0

Priority of 1

Priority of 64

Priority of 255

An OSPF adjacency can be established on an IES interface.

IES allows provider MP-BGP sessions to be extended to customers.

An IES service must use static routes in order to communicate with customer networks.

An IES interface supports OSPF and IS-IS in passive mode only.

The router with the lowest priority is the DR.

The router with the highest priority is the DR.

If priorities are the same, the DR is chosen based on the lowest RID.

If priorities are the same, the DR is chosen based on the highest RID.

Area 1 of router R1 should not be configured as a stub.

Router R3 has the incorrect authentication key type.

Router R1 has the incorrect authentication key type.

There is not enough information to tell.

It modifies the BGP advertisement logic.

It improves convergence times and allows for better load sharing.

It allows a router to advertise multiple external paths for a single prefix.

It supports both IPv4 and IPv6.

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.

Label

Frame check sequence

Traffic Class (previously called Experimental)

Time To live

Bottom of stack bit

iLER

LER

LSR

PE

eLER

Send a PathTear message towards router R6.

Send a PathTear message towards router R1.

Send a ResvTear message toward router R6.

Send a ResvTear message toward router R1.

Selected labels from the FIB are populated to the LFIB.

Selected labels from the RIB are populated to the FIB.

Selected labels from the LIB are populated to the FIB.

Selected labels from the LIB are populated to the LFIB.

Convergence is triggered when the adjacency between routers R1 and R2 drops as a result of Hello timeouts. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged.

Convergence is triggered when the physical interfaces between routers R1 and R2 go down. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged.

Convergence will not be triggered because switches cannot run routing protocols between them.

Convergence is triggered when the switches notify the routers about the link state information. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged

Convergence is triggered when an LSA is sent from router R1 to router R2 to indicate that the link is down. At this point, both routers R1 and R2 re-compute their link state database and send updates to their adjacent routers. Once the process is complete for all routers, the networks have converged.

Manual route summarization can only be done on autonomous system border routers.

Manual route summarization must be done on all the backbone routers to be effective. Manual route summarization is optional on the routers in non-backbone areas.

Manual route summarization is done on the ABRs. By default, automatic summarization is done; however, it may not be optimal for all networks.

Manual route summarization is done on the ABRs. By default, no route summarization is done and all routes are advertised to all areas.

No protocol extensions required

Only supported by OSPF and IS-IS

Transparent to routing neighbors

Uses Graceful Restart to inter-operate with other vendors

A separate label is used for each interface on which the FEC is advertised.

A single label is assigned to a FEC for all interfaces on the same router,

It is typically used when the device has ATM or Frame Relay interfaces.

It uses more label resources than a per-interface label space.

Each PLR signals a bypass tunnel that avoids the next-hop downstream router.

When a failure occurs, the PLR pushs an additional label onto the label stack.

No bypass tunnel is established if the PLR cannot provide node protection.

The head-end router sets the local protection desired flag in the session attribute object.

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

Enable traffic engineering on all routers along the LSP path.

Enable CSPF on the head-end router.

Configure a path definition on all routers along the LSP path.

Enable MPLS and RSVP on all routers along the LSP path.

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

Only the mirror source must be re-configured.

Only the mirror destination must be re-configured.

Both the mirror destination and mirror source must be re-configured.

Neither the mirror destination nor the mirror source must be re-configured.

".+ 65100"

"65100.+"

".* 65100.*"

"65100"

The IPv6 link-local address of the router D interface towards router A.

The IPv6 link-local address of the router A interface towards router D.

The IPv6 global address of router A.

The IPv6 global address of router D.

The router can reach prefix 192.10.1.2/32 through a RSVP-TE tunnel.

The router can reach prefix 192.10.1.2/32 through an LDP tunnel.

The router 10.10.10.2 is the egress router of the prefix 192.10.1.2/32.

The Isp-ping tool is used to perform a unidirectional LSP test.

A route target is used to distinguish to which VRF table a prefix belongs.

A route target appended to an IPv4 prefix produces a VPN-IPv4 prefix.

Multiple route targets can be part of a single MP-BGP update.

Route targets must be configured for VPRNs.

MPLS data traffic will be discarded until the IGP finds a new next-hop to router R3.

MPLS data traffic will be discarded unless the LDP tunnel has a standby secondary path.

MPLS data traffic will not be discarded because router R1 received labels from both next-hops, routers R2 and R3.

MPLS data traffic will not be discarded because of fast reroute capability on router R2.

An update message is used. Only a single prefix can be withdrawn at a time.

An update message is used. Multiple prefixes can be withdrawn at a time.

A withdraw message is used. Only a single prefix can be withdrawn at a time.

A withdraw message is used. Multiple prefixes can be withdrawn at a time.

10.32.1.2

10.1.4.78

10.48.1.1

10.1.2.2

Label values may be dynamically assigned by LDP.

Label values may be dynamically assigned by RSVP-TE.

Label values may be reserved for special uses.

Label values may be dynamically assigned by IGP.

Type 10 opaque LSAs are supported by IS-IS.

Type 10 opaque LSAs are flooded to all areas of the routing domain.

Type 10 opaque LSAs are stored in an LSDB.

Type 10 opaque LSAs are used for traffic engineering support.

Router LSA

AS External LSA

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Network LSA

None of the statements are correct.

The prefix list reject should be "192.168.3.0/16 exact".

Router R1 should be configured as an OSPF "asbr".

The policy "reject" should be set for import rather than export.

The policy was likely not "committed" after creation.

This is not possible because OSPF cannot use import policies.

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.

140000 137000

137000 140000

23456 23456

200 140000 137000

They are multicast to the All Hosts address.

They are broadcast to the subnet broadcast address.

They are multicast to the All Routers address.

They are broadcast or multicast, depending on the physical media.

It provides the ability to establish connection oriented paths over a connectionless IP network.

It provides a mechanism to engineer network traffic patterns independently of IP routing tables.

It will work over most physical layer protocols.

It can use GRE tunnels to transport data from many different protocols over an IP network.

0

2

3

6

Ping static 3.3.3.1

Ping static 0.0.0.0/0

Ping 3.3.3.1

Ping 0.0.0.0

Advertising external networks into IGP.

Using system addresses for setting up iBGP sessions.

Exporting the networks associated with the external links of eBGP peers into BGP.

Optimizing BGP route table by exporting IGP routes into BGP.

1

3

6

12

traceroute 2.3.4.1

traceroute 2.3.4.0/24 next-hop 1.2.3.4

traceroute next-hop 1.2.3.4

traceroute does not work on the Nokia 7750 SR

OSPF uses TCP, so the protocol number is 6.

OSPF uses UDP, so the protocol number is 17.

OSPF does not use IP.

OSPF has its own protocol number of 89.

To protect external networks from instability.

To communicate the architecture of an AS to external ASs.

To protect the local AS and other external ASs from bad NLRI.

To optimize ingress and egress traffic patterns to best serve the users of the AS.

Prefix 172.16.0.0/12 longer.

Prefix 172.31.0.0/22 longer.

Prefix 172.31.0.0/23 longer.

Prefix 172.31.0.0/24 exact.

1586

1596

1600

1614

All routers along the path, R1, R2, and R3 can be PLRs.

If the R1-R2 link fails, router R4 becomes an MP.

If the R2-R3 link fails, router R3 becomes a PLR.

Router R1 is the LSP head-end and can be a PLR.

Not So Stubby Areas

Level 1 Areas

Stub Areas

Partially Stubby Areas

0

5

10

15

R4 (10.10.10.4) has established a link protection tunnel.

R6 (10.10.10.6) has established a link protection tunnel.

R2 (10.10.10.2) has established a node protection tunnel.

R1 (10.10.10.1) has not established a node protection tunnel.

Neighbor, adjacency, route table

Neighbor, topology, forwarding

Topology, routing, forwarding

There are only two databases: adjacency and topology

The first BGP route.

The second BGP route.

Both routes are used.

It is impossible to determine without the value of the origin code for both routes.