4A0-C01 Nokia NRS II Composite Exam Questions and Answers

Automatic summarization and the use of IP addresses that use any number of bits for the network portion of the address.

Manual summarization and the use of IP addresses that use any number of bits for the network portion of the address.

Automatic summarization and the use of IP addresses that use a fixed number of bits for the network portion of the address.

Manual summarization and the use of IP addresses that use a fixed number of bits for the network portion of the address.

OSPF internal preference and IS-IS Level 1 internal preference.

OSPF internal preference and IS-IS Level 1 external preference.

OSPF external preference and IS-IS Level 1 internal preference.

OSPF external preference and IS-IS Level 2 internal preference.

OSPF external preference and IS-IS Level 1 external preference.

10.10.10.2

10.10.10.3

10.10.10.6

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

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

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

The path may comprise loose hop entries only.

The path must define the LSP's tail end.

The path may be used for multiple LSPs.

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.

This configuration already is configured for FRR.

fast-reroute facility

fast-reroute one-to-one

secondary

standby

LSPs must always terminate on a system ID.

MPLS and RSVP must be enabled on all routers.

Interfaces must be individually created in RSVP.

Path definitions must include at least one hop entry.

Fixed filter

Shared explicit

Standby explicit LSP

Preemptive filter

Link capacity filter

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.

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.

Next Header

Traffic Class

Flow Label

Payload Length

Options

Router LSA

AS External LSA

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Network LSA

Router LSA

Network LSA

Inter-Area Prefix LSA

Link LSA

Normal

Stub

Totally stubby

Totally NSSA

Operationally down interfaces in OSPF

Fully adjacent virtual links

Waiting state broadcast links

Fully adjacent point-to-point links

Loopback Interfaces in OSPF

By defining new LSAs for the IS-IS protocol.

By utilizing the OSPF opaque LSAs to maintain interoperability with OSPF routing domains

By defining new TE extension TLVs to the IS-IS protocol.

By enabling CSPF algorithm extensions that allow link state TE to be implemented.

The ARP functionality has been replaced by the Neighbor Discovery protocol.

The ARP functionality is not needed due to the increased IPv6 address space.

ICMPv6 reduced its role to connectivity checking and auto-configuration only.

ICMFV6 replaced the ARP functionality with Multicast Listener Discovery (MLD).

Router LSA

Network LSA

Intra-Area Prefix LSA

Link LSA

It is unidirectional.

It is bidirectional.

It must always have a secondary path.

It provides a specific tunnel for a FEC through the network.

It always follows the IGP best path.

TRUE

FALSE

On a point-to-point link, there is no need for a DR and BDR election; all routing updates are sent to 224.0.0.5.

On a point-to-point link, a DR and BDR are elected. The DR sends link-state advertisements describing the network.

On a point-to-point link, a DR and BDR are elected. To ensure resiliency, both the DR and BDR send link-state advertisements describing the network.

On a point-to-point link, there is no need for a DR and BDR election. All routing updates are sent to the unicast address of the neighbor's interface.

Exchange

Up

Down

2-Way

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.

The LSP is in the administrative down state.

The router's router ID overlaps another.

The router's interfaces do not have LDP running.

The router's system interface requires an IP address

Isp retry-timer

Isp retry-limit

mpls resignal-timer

rsvp refresh-time

router rsvp keep-multiplier

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.

The CSNP lists the LSPs in the router's database

The router is correctly configured.

Neither a reference-bandwidth nor wide-metrics is configured on the router.

A reference-bandwidth is configured on the router but wide-metrics is not.

Wide-metrics is configured on the router but a reference-bandwidth is not.

config>router#

config>qos#

config>port#

config>service#

T-LDP is used to provide an end-to-end session between two PE routers.

T-LDP is used to signal service labels for Layer 2 services.

T-LDP is used to establish transport tunnels for Layer 2 services.

T-LDP is used in LDP over RSVP solution.

The Standby with the highest next-hop IP.

The first Standby in the list.

The Standby with the longest uptime.

The Standby with the lowest next-hop IP.

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.

Routes from different customers with the same IPv4 address prefix are treated as equivalents by MP-BGP.

Alcatel-Lucent 7750 SR routers support MP-BGP for VPN label signaling in a VPRN service only if LDP is used for LSP signaling.

The multi-protocol nature of MP-BGP allows VPRN routes to be distributed within the provider core network as IPv4 routes.

MP-BGP is an enhanced version of BGP that can carry a service label, a tranpot label, and customer route prefixes.

None of the above statements describe the use of an MP-BGP in a VPRN.

All of the above statements describe the use of an MP-BGP in a VPRN.

TRUE

FALSE

The PLR attempts to provide link protection.

The PLR disregards the request after three failed attempts.

The PLR changes the PATH message to request link protection.

The PLR brings down the primary LSP-path.

The LSR regenerates and forwards a new PATH message.

The LSR stores the PATH message in the PSB.

The LSR forwards the PATH message based on the HOP object in the RSB.

The LSR looks up the PATH message's destination IP address in the FIB.

The penultimate router will forward packets to the eLER, based on the IP header.

The eLER will receive packets with a top label value of 0.

The eLER will receive packets with a top label value of 3.

The penultimate router will pop the top label from the packets.

0

2

3

4

OSPF

RIP

BGP

IS-IS

9000

9004

9008

9022

9036

LSP 1 will follow R1-R3-R4-R5. LSP 2 will follow R1-R2-R5.

LSP1 will follow R1-R2-R5. LSP 2 will follow R1-R3-R4-R5.

Both LSP 1 and LSP 2 will follow R1-R2-R5.

Both LSP 1 and LSP 2 will follow R1-R3-R4-R5.

The number of VPRN routes can become very large. MP-BGP can support a very large number of routes.

MP-BGP can carry routing information for a number of different address families.

MP-BGP is designed to exchange information between routers that are not directly connected. This feature keeps VPRN routing information out of P-routers.

MP-BGP can carry additional information attached to a route as an optional BGP attribute.

All of the above statements are valid reasons for using MP-BGP as a VPRN routing protocol.

Router R3 starts the LDP-Sync timer after recovering the LDP session on R3-R6.

Router R1 continues to use R1-R2-R4-R6 until the LDP-Sync feature is disabled.

Router R3 advertises the maximum metric for the link to router R6.

Router R1 receives a label from router R3 after the LDP session is established on R3-R6.

The SAP 1/1/1 will forward all traffic transparently.

The SAP 1/1/1:0.* will forward all untagged traffic and traffic tagged with VLAN 0.

The SAP 1/1/1:* will forward untagged traffic but not tagged traffic.

TheSAP1/1/1:400 will forward customer traffic tagged with VLAN 400

The SAP 1/1/1:0 will forward untagged traffic and traffic tagged with VLAN 0

If Shared Explicit reservation style is used, 400Mbps is reserved.

If Shared Explicit reservation style is used, 700Mbps is reserved.

If Fixed Filter reservation style is used, 400Mbps is reserved.

If Fixed Filter reservation style is used, 300Mbps is reserved.

The FCS is verified and the customer frame is transported intact over the service provider network.

The FCS is verified and kept in the customer frame. The VLAN tag is removed for transport over the network.

The FCS is verified and removed from the frame. The VLAN tag is kept for transport over the network.

The FCS is verified and removed from the frame. The VLAN tag is removed for transport over the network.

LDP must be enabled on both PE routers.

RSVP must be enabled on both PE routers.

Traffic engineering must be enabled in the IGP.

The VC-ID must match between the two PE routers in both directions.

The transport tunnel must be operationally up between the two PE routers in both directions.

The SDP ID must match between the two PE routers in both directions.

iLER

LER

LSR

PE

eLER

LDP Hello messages are sent over TCP.

LDP Hello messages are sent to the All Routers address 224.0.0.2.

LDP Hello messages are exchanged between all directly connected LDP enabled routers.

Each LDP enabled router must have its own unique system IP address.

The router will switch to Path-2 because it is the first secondary path configured in the list.

The router will not switch to Path-2 because the current path has the longest uptime.

The router will switch to Path-2 because it is a more preferred path.

The router will not switch to Path-2 because the router will not revert to another secondary path.

vc-type null

vc-type ether

vc-type vlan

vc-type none

An IGP route takes priority over a transport tunnel.

Both LDP and RSVP-TE based tunnels can be used.

MPLS tunnels can be used to resolve the prefixes learned via IGP.

Multiple MPLS tunnels can be installed in the FIB.

RRO is used to report the protection tunnel status to the head-end router.

RRO contains the MP information that is required by a PLR for facility protection.

RRO contains the label information that is expected by an MP for facility protection.

RRO is used to inform downstream routers about the protection type requested.

configure service sdp sdp-id gre create

configure service sdp sdp-id create

Idp

Isp Isp-name

IGP-based LSPs are calculated based on information contained in routing tables.

Constraint-based LSPs are calculated using the head-end router's TED.

Constraint-based LSPs must use RSVP-TE signaling.

IGP-based LSPs must use LDP signaling.

A physical port.

ASAP.

Ingress MPLS frames with a specific label.

Entries that match an IP filter.

Entries that match a MAC filter.

All of the above can be used as a mirror source.

10 Gbps

7 Gbps

3 Gbps

2 Gbps

Send a PATH Tear message toward router R6.

Send a PATH Tear message toward router R1.

Send a PATH Error message toward router R6.

Send a PATH Error message toward router R1.

ATM to Frame Relay translation.

Frame Relay to Ethernet translation.

ATM tunneling over a Frame Relay core network.

Frame Relay tunneling over an ATM core network.

Frame Relay tunneling over an MPLS/IP core network

configure router tunnel

configure router gre

configure router rsvp-te

configure router transport-tunnel

configure router mpls

SDP

Network port

LSP

Service

RSVP

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.

An echo request is sent based on the LSP's label stack.

Echo reply packets may not take the same path as the LSP.

The IP destination address is used to initiate echo requests,

The test fails if the LSP is not operationally up.

The FCS is verified and kept in the customer frame. The VLAN tag is kept and transported over the network.

The FCS is verified and kept in the customer frame. The VLAN tag is removed for transport over the network.

The FCS is verified and removed from the frame. The VLAN tag is kept and transported over the network.

The FCS is verified and removed from the frame. The VLAN tag is removed for transport over the network.

7958

7978

8022

8042

An IES can only have one interface.

An IES interface can have an SDP or a SAP.

An IES can perform fragmentation.

An IES must have an IP address assigned to it.

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.

A packet receives a service label and a transport label at the ingress PE.

A packet has its service label swapped at each P router.

The egress PE pops the service label, and the transport label is forwarded.

The service label is popped by the remote CE.

The dot1Q default SAP (port: *) can be used to pass VLAN tags transparently through a network.

The dot1Q null SAP (port: 0) accepts all tagged frames and untagged frames.

The dot1Q default SAP (port: *) accepts all untagged frames and any frames with tag values that are not used as a service-delimiting value on another SAP.

A dot1q null SAP (port: 0) and a dot1q default SAP (port: *) cannot both be defined on the same port.

IP filter

MAC filter

Egress label

Ingress label

ping

sdp-ping

svc-ping

Isp-ping

L-LDP

T-LDP

RSVP-TE

MP-BGP

1514

1528

1536

1540

1560

The Ethernet port must be set to network mode, and the service must have a spoke SDP.

The Ethernet port must be set to network mode.

The Ethernet port must be set to access mode.

The Ethernet port must be set to access mode, and the service must have a spoke SDP.

To advertise VPN-IPv4 and VPN-IFV6 routes, two MP-BGP sessions are required.

PE routers must support both IPv4 and IPv6 addresses; customer routers can use either one.

MP-BGP is used to advertise IPv6 prefixes and the associated VPRN labels.

The provider core routers are IPv6-unaware.

1

3

6

12

By default, the VC ID on the mesh SDPs of a VPLS are set to the service ID.

A VPLS appears to the customer as a direct Ethernet connection.

Mesh SDPs are used for VPLSes to avoid loops.

By default, T-LDP is used for signaling service labels.

LDP

BGP

MP-BGP

MPLS

ADSPEC

CSPF

Service ping

LSP trace

Dedicates a separate port for each customer.

Performs ARP look-ups for each service.

Maintains a different IP routing table for each service.

Maintains a different MAC Forwarding Database for each service.

Route distinguishes are appended to IPv4 prefixes to form IPv6 prefixes.

CE routers use a route distinguisher to indicate which VPRN they are associated to.

A route distinguisher combined with an IPv4 prefix produces a VPN-IPv4 prefix.

Route distinguishes are used to determine which routes a VPRN should import.

2

12

30

44

100

The VC ID Cannot be determined from the output

5000

5004

5008

5014

The frame egresses 1/1/1:6.7 with an outer VLAN tag of 6 and inner tag of 7.

The frame is dropped at the egress SAP 1/1/1:6.7.

The frame egresses 1/1/1:6.7 with VLAN tag 5.

The frame egresses 1/1/1:6.7 with VLAN tag 6.

RSVP

IPCP

TLDP

PPP

Either RSVP or LDP

M-BGP

Set the service MTU of the VPLS to match the IES MTU.

Set the ip-mtu of the IES to match the service MTU of the VPLS.

Set the SDP MTU of the IES to match the SDP MTU of the VPLS.

Set the MTU of the IES's network port to match the service MTU of the VPLS.

Option A

Option B

Option C

Option D

F-pipes use SAPs in the form of port: DLCI (e.g. 1/2/3:65).

To the customer, the PE appears as a native Frame Relay UNI (User Network Interface).

Multiple Frame Relay circuits can be mapped to a single F-pipe service on the Alcatel-Lucent 7750 SR.

The MPLS control word is required because the Frame Relay header is not encapsulated in the frame.

vc-type ether

vc-type vlan

vc-type dotlq

vc-type null

1520

1540

1548

1556

Traffic is flooded to all SAPs in the service.

Traffic is flooded to all SAPs and spoke SDPs in the service.

Traffic is flooded to all SAPs and mesh SDPs in the service.

Traffic is flooded to all SAPs, spoke SDPs, and mesh SDPs in the service.

The traffic is not flooded.

Area Border Router

Autonomous System Boundary Router

Designated Router

All routers within an OSPF area.

sap 1/1/1

sap 1/1/1:*.0

sap 1/1/1:0.*

1/1/1:0

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

Not so stubby areas

Level1 area WC

Stub areas

Partially stubby areas

Level 2 areas

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

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

Router R1

Router R2

Routers R1 and R2

Router R4

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.

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.

DSCP marking

Class of Service Marking

DSAP marking

ICMP type

When two areas need to communicate and there is no area 0.

When an area needs to traverse another area to reach area 0.

When two areas are connected to area 0, but there is no direct path between them.

When an area needs to connect directly to another area without using area 0.

Initializing

Up

Down

2-Way

1

2

3

4

6

7

Use a prefix list on router R1 to discard all ingress IS-IS routes.

Use an export policy and prefix list on router R1.

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

This is not possible because IS-IS cannot use import policies.

Area addresses TLV

Intermediate system neighbors

TLV Authentication information TLV

Intermediate system neighbors

TLV Area addresses

TLV LSP entries TLV

The IP internal reachability information

TLV Area Addresses

TLV Authentication Information TLV

The IP external reachability information

TLV Area addresses

TLV Intermediate system neighbors TLV

ff00::1:2

fe80::216:4dff:fe13:5cae

::ffff:0:0.240.0.0.1

2001:db8::30a:216:4dff:fe13:5cae

fd01:2234:5678::1

Priority of 0

Priority of 1

Priority of 64

Priority of 255

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.

L1 and L2 routers elect separate DIS's.

DIS uses multicast address 0180x200:0015 to communicate with other routers on the broadcast network.

If a new router starts up in a LAN and has a higher interface priority, the new router preempts the original DIS and becomes the DIS.

In broadcast multi-access networks, such as Ethernet, a single router is elected as the DIS. There is no backup DIS

49.0012.1234

49.0012

12.1234

1234

49.1234

The LSP is acknowledged by sending a PSNP PDU.

The LSP is acknowledged by sending an LSP PDU.

The LSP is acknowledged by sending a Hello PDU.

LSP are not acknowledged on broadcast links. The DIS sends periodic CSNPs to maintain database synchronization

5 and 15 seconds

10 and 30 seconds

5 and 20 seconds

10 and 40 seconds

Not so stubby area

Stub area

Backbone area

Normal area

Not So Stubby Areas

Level 1 Areas

Stub Areas

Partially Stubby Areas

At the bottom

In the middle

At the top

It does not matter where they are placed.

Routers R1 and R2 are L2 routers. Routers R3 and R4 are L1/L2 routers

Routers R1, R2, and R4 are L1/L2 routers. Router R3 is an L1 router,

Routers R1, R2, and R3 are L2 routers. Router R4 is an L1 router,

Routers R1 and R2 are L1/L2 routers. Routers R3 and R4 are L1 routers

Metric is cost based

Slow convergence

Automatic summarization

Support CIDR

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.

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 router installs two routes for the destination with two different next hops. A hashing algorithm is used to distribute traffic over the two paths.

The router installs two routes for the destination with two different next hops. Traffic is evenly distributed over the two paths.

The router installs four routes for the destination with four different next hops. A hashing algorithm is used to distribute traffic over the four paths.

The router installs four routes for the destination with four different next hops. Traffic is evenly distributed over the four paths.

The router installs one route for the destination. Traffic is evenly distributed over the two paths.

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

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.

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