Nokia 4A0-C01 Nokia NRS II Composite Exam Exam Practice Test

49.0012.1234

49.0012

12.1234

1234

49.1234

RIPv1 and RIPv2

OSPF

IS-IS

BGP

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

show router ospf area

show router ospf neighbor

show router ospf interface

show router ospf status

Router LSA

AS External LSA

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Network LSA

None of the statements are correct.

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

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

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

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

224.0.0.5

224.0.0.6

224.0.0.9

224.0.0.10

RIPv2 does not have support for multicast

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

No protocol extensions required

Only supported by OSPF and IS-IS

Transparent to routing neighbors

Uses Graceful Restart to inter-operate with other vendors

89

87

85

83

True

False

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.

1

2

3

4

6

7

L1 routers

L2 routers

L1/L2 routers

L1 and L2 routers

config>filter# default-action XXX

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

config>filter# default-mode XXX

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

Fast reroute capability

Control traffic prioritization

Route redistribution

Traffic engineering extensions

Cut through forwarding

Ping static 3.3.3.1

Ping static 0.0.0.0/0

Ping 3.3.3.1

Ping 0.0.0.0

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 DIS creates a logical node to represent a group of routers on the same non-broadcast network; this node is the pseudonode

The DIS creates a logical node to represent the topological database of the backbone network in an IS-IS network; this node is the pseudonode

The DIS creates a logical node to represent a broadcast sub-network; this node is the pseudonode

The DIS creates a logical node to represent the complete topology of an IS-IS area; this node is the pseudode

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

PDU authentication.

The ability to customize the link cost metric.

Use of Bellman-Ford routing algorithm.

Classless routing.

Updates sent as layer 3 multicast.

1

49

47

45

39

Use split horizon by default.

Send information about directly connected links to neighbors at periodic intervals.

Use holddown timers when topologies change to allow for convergence.

Maintain multiple databases: neighbor, topology and routing.

Area ID

Hello and Dead Intervals

Stub flag

DR and BDR addresses

The list of neighbors

Show isis neighbors

Show router isis neighbors

Show router isis adjacency

Show isis adjacency

Routers R1 and R2 are in different areas.

Routers R1 and R2 are in the same area.

Routers R1 and R2 will send a Level 1 Hello PDU and Level 2 Hello PDU, if the interface type between them is point-to-point.

Routers R1 and R2 will send a Level 1 Hello PDU and Level 2 Hello PDU, if the interface type between them is broadcast.

Routers R1 and R2 will send a Level 1/2 Hello PDU if the interface type between them is broadcast.

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

Hellos, CSNPs, PSNPs

LSPs. Hellos, CSNPs

LSPs, PSNPs, Hellos

LSPs, CSNPs, PSNPs

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.

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.

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

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

7958

7978

8022

8042

A mirror source with a defined source type.

A mirror source defined with an SDP destination.

A mirror destination with a SAP defined.

A mirror destination and a mirror source with the same service ID.

0

1

2

3

1514

1528

1536

1540

1560

SAPs can be defined on Ethernet, POS, Sonet/SDH, or TDM channels.

Only one SAP is required for a service that originates and terminates on the same Alcatel-Lucent 7750 SR.

SAPs can have QoS policies assigned to them.

Multiple SAPs can be defined on the same port.

6VPE is a tunneling technology that makes use of MPLS tunnels to transport IPv6 prefixes over an IPv4 infrastructure.

Customers connected to 6VPE can run IPv6 or IPv4.

On a PE router, if the MP-BGP next hop is an IPv4 address, a mapped IPv6-compliant address will be used.

6VPE implements its own VPN-IPv6 address family and is a replacement for MP-BGP.

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.

SDP

Network port

LSP

Service

RSVP

An Epipe service that has 1 SAP and 1 SDP configured.

An Epipe service that has 3 or more SAPs configured.

An Epipe service that has 2 SAPs on the same router and has no SDPs configured.

An Epipe service that is configured between two routers, each having 1 SAP and 1 SDP configured

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.

The service label is swapped for a transport label during transport.

The transport label is used to forward packets between PEs.

The service label is used to identify which VPRN a packet belongs to.

Labels are initially added at the ingress PE.

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.

show service id 100 base

show service vpls 100

show service vpls 100 summary

show service vpls 100 all

None of the above.

L-LDP

T-LDP

RSVP-TE

MP-BGP

An IES has a configurable VC MTU.

An IES interface has an IP address assigned to it.

IES supports QoS.

An IES requires a spoke SDP.

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.

2

12

30

44

100

The VC ID Cannot be determined from the output

The VPN-IPv4 address family.

The IPv4 address family.

Either IPv4 or VPN-IPv4 address families can be configured.

The same address family must be used for the provider network and the PE-CE.

The SDP to 10.10.10.1 on router R4 is shutdown.

Router R4 has not sent a label to router R1 (10.10.10.1) yet.

10.10.10.1 has a different service MTU set.

10.10.10.1 has not sent a label to router R4 yet.

A VPLS service does not use a MAC FDB.

The router reads the destination MAC address of frames passing through the service.

The router reads the source MAC address of frames passing through the service.

The router uses reverse ARP (RARP) to resolve the MAC addresses for unknown destinations.

The router is programmed with MAC addresses by the network administrator.

"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 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.

4078

4986

5014

5022

Customers must use the same routing protocol as the service provider.

Customers belonging to the same VPRN service must use the same subnet.

Service providers only need to perform configurations on the PEs to add additional VPRNs.

For each VPRN, only one customer can be connected at each PE.

3

4

6

8

The E-pipe can support a maximum MTU size of 1578.

The ports of the link PE2-PE3 have an MTU of 1578.

An svc-ping of the E-pipe will succeed.

If the step size was 2, the maximum response size would be the same.

When a PE router receives an IPv4 prefix from its local CE it creates a VPN-IPv4 prefix.

The route distinguisher (RD) is appended to the IPv4 prefix to form a 16 byte VPN-IPv4 prefix.

VPN-IPv4 allows BGP to distinguish multiple routes with the same prefixes originated from distinct customers

VPN-IPv4 addresses are only present within the service provider network.

In VPRN, data traffic is carried in VPN-IPv4 packets.

PE2 needs a mirror source with the remote source specified.

PE1 needs a mirror destination with the remote source specified.

PE1 needs a mirror source with the remote source specified.

PE1 and PE2 need a mirror source specified.

family ipv4 ipv6

family vpn-ipv4ipv6

family vpn-ipv4 vpn-ipv6

family ipv6 vpn-ipv6

TRUE

FALSE

Customer ID and SAP ID.

Customer ID and Service ID.

SAP ID and Service ID.

SDP ID and Service ID.

SDP ID and SAP ID.

SDP ID and VC ID.

vc-type ether

vc-type vlan

vc-type dotlq

vc-type null

TRUE

FALSE

All FECs with a prefix of 192.168.1.0/30.

Local FECs with a prefix of 192.168.1.0/30.

All FECs excluding 192.168.1.0/30.

Local FECs excluding 192.168.1.0/30.

R1, R2, and R4 can be PLRs; R6 is the MP.

R1, R2, and R4 can be PLRs; R2, R4, and R6 are MPs.

R1, R2, R3, R4, and R5 can be PLRs; R6 is the MP.

R1, R2, R3. R4, and R5 can be PLRs; R2, R4, and R6 is the MP.

A data packet will receive a service label at the CE and a transport label at the ingress PE.

A data packet intended for a remote CE will have its service label swapped at each P router along the path towards the egress PE.

At the egress PE, the transport label will be popped and the data packet forwarded with the service label.

The service label is popped by the remote CE. The unlabeled packet is forwarded based on the longest match lookup algorithm in the VRF.

All of the above statements are false.

All of the above statements are true.

RSVP LSPs must exist between each PE-ABR pair, or ABR-ABR pair in each area.

When LDP-over-RSVP is active, the LDP prefixes are resolved to a physical egress interface.

Targeted sessions must exist between all routers along the tunnel path.

Link LDP sessions must exist between each ABR-ABR pair in each area.

Traffic engineering information is carried in the extended TLVs.

Traffic engineering must be enabled on all IP/MPLS routers along the LSP path.

Traffic engineering information is stored in the opaque database,

Traffic engineering is required for constraint-based LSPs.

A path definition can have both loose and strict hops.

A path definition can be configured with loose hops only.

A path definition is configured on the head-end router only,

A path definition is not required if CSPF is enabled on an LSP.

Drop the frame.

Flood the frame to all PEs participating in the service.

Send a destination unreachable message back to the originating host.

Store the frame until the destination is known

Enable the Idp-over-rsvp feature on all PEs and ABRs along the LSP tunnel.

Configure Link-LDP sessions between each PE-ABR and ABR-ABR pair.

Configure RSVP-TE LSPs in each area between each PE-ABR and ABR-ABR pair.

Configure T-LDP sessions with the tunneling option.

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.

The MPLS label value may be carried in an ATM header.

The MPLS label value may be carried in a shim header.

The MPLS label value may be carried in an OSPF header.

The MPLS label value may be carried in a Frame Relay header.

The frame is dropped.

The service ID is added as the VLAN tag.

A VLAN tag of 0 is added as the provider VLAN tag

The frame is forwarded with no VLAN tag

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.

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.

Dot1Q

Q-in-Q

ATM

NULL

Nil

The Hello protocol can speed up convergence without reducing refresh time.

Hello messages are sent after at least one RSVP session is active on the interface.

An interface with multiple RSVP sessions sends Hello messages for each session.

An RSVP neighbor is declared down if Hello messages are not received within the Hello timeout.

1

2

3

4

Liberal label retention mode

Conservative label retention mode

Ordered control mode

Independent control mode

LSPs must always terminate on a system ID.

MPLS and RSVP must be enabled on all LSRs.

CSPF must be enabled.

Path definitions must include at least one hop entry.

To test the ability of reaching the far-end IP address of an SDP within the SDP encapsulation

To determine the path MTU to the far-end IP address over an SDP.

To determine the service MTU of the service using an SDP.

To determine the presence of hosts using the service

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 time router R4 takes to send a PATH Error message toward the head-end router.

The time router R4 takes to detect RSVP Hello message timeout from router R6.

The time router R4 takes to send a RESV Error message to the head-end router.

The time router R1 takes to signal an alternate path through router R3.

Provides a mechanism to determine the hops an SDP traverses.

Provides in-band uni-directional connectivity tests.

Provides in-band round-trip connectivity tests.

Tests ability of reaching the far-end IP address of an SDP ID within the SDP encapsulation.

Provides information regarding the exact MTU supported between service ingress and service termination.

Configure BGP with the IPv6 address family.

Configure BGP to add IPv6 Explicit Null labels.

Configure a route policy to export IPv6 routes into BGP.

Configure the nexthop core router as a BGP peer.

9000

9004

9008

9022

9036

Frame mode requires multiple sessions between peers.

The lower transport address initiates the session.

Established LDP sessions run over a TCP connection.

An LDP session is established immediately after Init messages are exchanged between peers.

The LSP will switchover to another path if a failure occurs.

The LSP will switchover to a better path as soon as it is available.

CSPF must be enabled for this LSP to attempt to find a better path.

The LSP will switchover to a better path in a MBB fashion.

The MPLS TTL values are incremented at each request.

The router uses MPLS Echo Request packets that are IP-routed.

The router collects hop information along the tunnel's path.

The router performs an unidirectional LSP test.

sdp-ping

Isp-ping

sap-ping

svc-ping

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.

6VPE is a tunneling technology that makes use of MPLS tunnels to transport IPv6 information over an IPv4 MPLS infrastructure.

Customers connected to 6VPE could run native IPv6 or IPv4.

On the PE router, the next hop for a VPN IPv6 address is an IPv6 address, regardless of the nature of the network between the PEs.

6VPE requires an IPv6-aware MPLS core.

Both C and D are false.

All of the above statements are true.

A mirror destination on the local and remote Alcatel-Lucent Service Router,

A mirror source on the local and remote Alcatel-Lucent Service Router.

A mirror source with the remote source specified on the remote Alcatel-Lucent Service Router.

A mirror source with the remote source specified on the local Alcatel-Lucent Service Router.

An SDP between the local and remote Alcatel-Lucent Service Routers.

Link

AS External

Router

Intra-Area Prefix

IOM

CPM

FIB

SPF

Enable LDP on the R2-R5 interface.

Configure T-LDP sessions between routers R2 and R5 and R3.

Configure LDP-over-RSVP support on router R2.

Enable MPLS and RSVP on the router R2 network interfaces.

Enable LDP on the R2-R5 and R2-R3 interfaces.

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Inter-Area Router LSA

AS External LSA

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.

1

10

100

1000

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.

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.

Neighbor, adjacency, routing.

Neighbor, topology, forwarding.

Topology, routing, forwarding.

Topology, forwarding, traffic classification.

Neighbor, adjacency, forwarding.

The PLR sends it downstream with the RRO.

The PLR sends it downstream with the ERO.

It associates all detours with the source PLR.

The MP sends it upstream with the RESV message.

Tunnel ID

Name

LSP ID

To

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 from router R3 directly to router R1.

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 up.

TRUE

FALSE

L1 and L2 routers elect separate DIS's.

DIS uses a specific Ethernet multicast address 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, one router is elected as the DIS and a second router as the backup DIS.

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

Path message

iLER message

Resv message

LSP setup call request

eLER message

Add "stub no summaries" to the area 1 configuration on router R1.

Add the "originate-default-route" option in the area 1 configuration on router R1.

Add a default static route on router R3.

Include the system interface in the area 1 configuration on router R3.

Add a static route on router R3 to 192.168.3.1.

The route policy should be applied as an import policy.

The route policy should say "from protocol isis" instead of "from protocol direct".

The ASBR configuration should be removed.

The interface between routers R1 and R3 must be in OSPF area 0.

IP routing protocols do not always select the best route to a destination.

IP routing protocols always select multiple routes to a destination.

IP routing protocols do not make use of all available network attributes to select a path

Improper network design results in limited network path redundancy.

10.10.10.2

10.10.10.3

10.10.10.4

10.10.10.6

There is no ASBR configured in the network.

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

A PUSH label stack operation must be performed.

The outgoing interface and next-hop address will be determined from the FIB.

The packet can be forwarded as a labeled or unlabeled packet.

A POP label stack operation may be performed.

Router R1 is the LSP originator and is also a PLR.

With one-to-one link or node protection, the detour LSP path is R1-R4-R5-R2-R3.

With one-to-one link or node protection, the detour LSP path is R1-R4-R5-R3.

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

None of the nodes can be protected with FRR.

A mechanism that implements opaque LSAs.

A mechanism that computes routes based on defined user requirements.

A mechanism that allows the IGP shortest path to be used.

A mechanism that allows RSVP or LDP signaling to use a route other than the IGP best route to establish a LSP.

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.

TE enabled OSPF routers

Backbone router only

ABR only

ASBR only

The link-state information is not populated in the database, but is forwarded to all neighbors.

The link-state information already in the database is overwritten and the age is reset.

The link-state information is not populated in the database and an acknowledgement is sent.

The link-state information is regarded as old and nothing is done.

A link-state request is performed to increase the sequence number.

The area addresses TLV

The intermediate system neighbors TLV

The IP interface address TLV

The authentication information TLV

0

1

2

3

4

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.

Normal

Stub

Totally stubby

Totally NSSA