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

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.

After a new path for LSP-1 is established on R1-R3-R5-R6, the old path is torn down.

After the old path for LSP-1 is torn down, the new path is established on R1-R3-R5-R6.

LSP-1 will stay on R1-R2-R4-R6 because there is enough bandwidth on the existing path.

LSP-1 will be torn down because CSPF fails to find a new path.

Liberal label retention mode

Conservative label retention mode

Ordered control mode

Independent control mode

CPM

MDA

Switch Fabric

IOM

Path message

iLER message

Resv message

LSP setup call request

eLER message

Each implementation can use them as they see fit.

They are used to carry the Ethertype value.

They are used to carry the TTL value.

They are used to carry QoS classification.

They are used to carry fragmentation flag information

Fixed filter

Shared explicit

Standby explicit LSP

Preemptive filter

Link capacity filter

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

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

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

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

A single label may be assigned to an FEC and used across all interfaces of the same router.

It is only valid when the LDP peers are directly connected over an interface, and the label is only going to be used for traffic sent over that interface.

fe80::2416:4dff:fe16:b53d

fe80::2616:4dff:fe16:b53d

ff80::2416:4dff:fe 16:b53d

ff80::2616:4dff:fe 16:b53d

fd80::2416:4dff:fe16:b53d

The egress RSVP interface has 80 percent bandwidth unreserved.

LSPs can reserve an additional 9.9 Gbps bandwidth on this RSVP interface.

The head end reserves 100Mbps for the LSP

The egress RSVP interface has 1 Gbps bandwidth unreserved.

Type 1 Router LSA

Type 2 Network LSA

Type 3 Summary LSA

Type 4 ASBR LSA

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

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.

The IGP FIB.

The Reservation State Block (RSB)

The Path State Block (PSB)

The opaque database.

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.

Intra-Area Prefix LSA

Inter-Area Prefix LSA

Inter-Area Router LSA

AS External LSA

The route learned from IS-IS will be installed.

The route learned from OSPF will be installed.

Both routes will be installed.

There is not enough information to answer the question

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.

The router cannot do a SWAP of this label.

The label does not match the egress label for the same FEC.

The label is for a FEC for which the next-hop is the peer router

The label was signaled in error.

The router's system address.

The next-hop prefix.

The interface's global prefix.

The next-hop system address.

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.

A virtual routing/forwarding table is created per IES service.

Only one IES service can be created for a single customer ID.

More than one IP interface can be created within a single IES service.

All IP interfaces created within the same IES service belong to the same customer

No primary path is established. The secondary path will take R1-R2-R4-R6.

The primary path will take R1-R3-R5-R6. The secondary path will take R1-R2-R4-R6.

The primary path will take R1-R2-R4-R6. No secondary path is established.

The primary path will take R1-R2-R4-R6. The secondary path will take R1-R3-R5-R6.

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.

Configuring IS-IS interfaces

Enabling IS-IS

Configuring level capabilities

Specifying an area address

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

L1 routers

L2 routers

L1/L2 routers

L1 and L2 routers

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.

At the bottom

In the middle

At the top

It does not matter where they are placed.

Configure IS-IS interfaces

Enable IS-IS

Configure level capabilities

Specify an area address

config>filter# default-action XXX

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

config>filter# default-mode XXX

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

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.

An L1/L2 router can have neighbors 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 its L1 neighbors.

An L1/L2 router sets the ATT bit in L1 LSPs to identify itself as an L1 router.

Broadcast

Non-broadcast multi-access

Point-to-point

Point-to-multipoint

Level 0

Level 1

Level 2

Level 0/1

Level 1/2

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

No protocol extensions required

Only supported by OSPF and IS-IS

Transparent to routing neighbors

Uses Graceful Restart to inter-operate with other vendors

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.

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

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

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

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

The route policy should be applied as in import policy

The no-redistribute-external command is used on router R1

The route policy is incorrect. It should say "from protocol ISIS" rather than "from protocol direct".

It is not possible to be an ASBR and an NSSA. The ASBR configuration should be removed.

The interface between routers R1 and R3 needs to be in OSPF area 0 rather than OSPF area 1 because a backbone area must always exist.

224.0.0.5

224.0.0.6

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

The system address of the router.

There is no such calculation in IS-IS

Show router isis database

Show router isis dijykstra

Show router isis spf

Ping static 3.3.3.1

Ping static 0.0.0.0/0

Ping 3.3.3.1

Ping 0.0.0.0

Metric is cost based

Slow convergence

Automatic summarization

Support CIDR

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.

Use an import policy and a prefix list on router R1 to reject this route.

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

Use an export policy and prefix list on router R1 to reject this route.

This is not possible because RIP cannot use import policies.

5 and 15 seconds

10 and 30 seconds

5 and 20 seconds

10 and 40 seconds

89

87

85

83

Link Local LSA

Router LSA

Network LSA

Inter-Area Router LSA

Intra-Area Prefix LSA

None of the above LSAs have an AS scope.

Neighbor, adjacency, route table

Neighbor, topology, forwarding

Topology, routing, forwarding

There are only two databases: adjacency and topology

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.

Not So Stubby Area

Stub Area

Backbone Area

Standard Area

Non-broadcast

Broadcast

Point-to-multipoint

Point-to-point

They are sent using multicast MAC addresses 0180:0200:0014.

They are sent using multicast MAC addresses 0180:c200:0015.

They are sent using a unicast address.

None of the above.

1

4

6

8

12

24

config>service# epipe service-id enable

config>service# vpws service-id enable

config>service# service-id no shutdown

config>port# port-id no shutdown

config>service# epipe service-id no shutdown

RSVP-TE is a routing protocol.

RSVP-TE requests end-to-end resources for unidirectional data flow.

RSVP-TE consults the local RSVP database to determine the path from source to destination.

RSVP-TE generates a TED for storing traffic engineering information.

An LSR may answer requests for label mappings immediately, without waiting for a label mapping from the next-hop.

An LSR may advertise label mappings to all peers for which it might be a next-hop for a given FEC.

An LSR propagates a label mapping downstream for a FEC, only if it has a label mapping for the FEC next-hop.

An LSR will only distribute a label for a FEC when it has been requested to do so.

Shut down all SAPs associated with the service.

Shut down all SDPs associated with the service.

Delete all SAPs and SDPs associated with the service.

Shut down all physical ports that are bound to a SAP.

Delete the Customer ID.

Shut down the service.

LDP is not configured on R2.

R2 does not have a route to 10.10.10.3.

LDP is not configured on R3's interface to R2.

The targeted session is not configured on R2.

VPLS supports point-to-point connections.

VPLS supports multipoint-to-multipoint connections

VPLS supports a distributed service

VPLS supports a local service on a single node.

iLER

LER

LSR

PE

eLER

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

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.

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

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.

configure ies 5 customer 1000 create

configure router ies 5 customer 1000 create

configure service ies 5 customer 1000 create

configure router ies 5 customer 1000

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.

Label space mode

Label retention

Control mode

Keepalive factor

The LSP will stay on the current path indefinitely unless another failure occurs.

The LSP will stay on the current path until the resignal timer expires.

The LSP will switchover to R1-R2-R3-R5-R6 after the resignal timer expires.

The LSP will switchover to R1-R3-R5-R6 after the retry timer expires.

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.

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.

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.

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

The same label can be used to forward a packet on an LSR regardless of which egress port is used.

It uses fewer label resources than a per-platform label space.

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

MTU must match on both services,

Mesh-SDP with matching vc-id configured,

Spoke-SDP with matching vc-id configured.

Spoke-SDP.

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

4

Incoming label

Outgoing label

Incoming interface

Outgoing interface

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 frame is dropped.

The service ID is added as the provider VLAN tag.

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

The frame is forwarded with no provider VLAN tag.

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.

They allow a VPLS to scale more easily.

They use mesh SDPs to connect smaller VPLSes together.

They allow a service to span multiple metro networks.

They simplify the configuration required when adding new PEs.

mac-trace

svc-ping

Isp-trace

traceroute

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.

Dot1q

Null

QinQ

ATM

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.

ADSPEC sets an SDP's MTU to the smallest MTU value found along the LSP path.

RSVP must be enabled on all MPLS routers of a path to use ADSPEC.

ADSPEC can automatically adjust the service MTU.

ADSPEC can be enabled on individual LSPs.

TRUE

FALSE

1520

1540

1548

1556

An IES provides a Layer 3 interface to a customer.

A virtual routing/forwarding table is created per IES service.

An IES supports QoS.

An IES interface's IP address, if bound to a port, will appear in the routing table.

configure service vpls 4 customer 4 vc-id 5 create

configure service vpls 5 customer 4 create

configure service vpls 100 customer 4 vc-id 4 create

configure service vpls vc-id 5 customer4 create

All routes in the VRF are advertised to the PEs and CEs.

No routes in the VRF are advertised to the PEs or to the CEs.

All routes in the VRF are advertised to the PEs, but not to the CEs.

All routes in the VRF are advertised to the CEs, but not to the PEs.

1514

1528

1536

1540

1560

Service tunnels are unidirectional.

Transport tunnels are unidirectional.

A service will use the same service label for every hop.

A local service requires a transport tunnel.

config>service>ies# interface "to-CE" customer customer-id create

config>service>ies# interface to CE create

config>service>ies# interface to CE

config>service>ies# interface "to-CE" create

DLC Header

Control Word

Transport Label

Service Label

Both PE1 and PE2 need a mirror source.

PE2 needs a mirror source with the remote source specified.

PE1 needs a mirror source with the remote source specified.

Both PE1 and PE2 need a mirror destination.

PE2 needs a mirror destination that specifies a SAP.

sap 1/1/1:0

requires both sap 1/1/1:0 and sap 1/1/1:*

sap 1/1/1:0-4096

sap 1/1/1:*

dot1q

null

qinq

atm

ipcp

bcp-null

7958

7978

8022

8042

A mirror destination to indicate which ports to monitor.

A mirror source to indicate which ports to monitor.

A mirror destination to indicate on which sap or sdp traffic should be replicated.

A mirror source to indicate on which sap or sdp traffic should be replicated

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.

The service is a local service.

The service requires a second spoke SDP on this router.

The service's VC ID is 44.

The service will accept VLAN tag 100.

By default, a VPLS signals an MTU based on the network port.

By default, an IES sets its ip-mtu to the VC MTU of the VPLS.

By default, an IES uses an MTU value based on its SAP.

By default, an IES uses an MTU based on the network port.

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.

1500

1508

1514

1522

TRUE

FALSE

IPCP

LDP

PPP

TLDP

1

5

10

20

Router LSA

Network LSA

Summary Network LSA

Summary Router LSA

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.

SDP

Network port

LSP

Service

RSVP

1

2

3

4

6

7

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.

Exchange

Up

Down

2-Way

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

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

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

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

Router R1 summarizes the prefixes from router R3 as 192.168.0.0/16 and router R2 does not summarize the prefixes.

Router R1 does not summarize the prefixes from routers R3 and R2 summarizes them as 192.168.0.0/16.

Router R1 summarizes the prefixes from router R3 as 192.168.0.0/20 and router R2 does not summarize the prefixes.

Router R1 does not summarize the prefixes from routers R3 and R2 summarizes them as 192.168.0.0/20.

Both routers R1 and R2 summarize the prefixes from R3 as 192.168.0.0/20.

Neither router R1 nor router R2 summarizes the prefixes from router R3.

Operationally down interfaces in OSPF

Fully adjacent virtual links

Waiting state broadcast links

Fully adjacent point-to-point links

Loopback Interfaces in OSPF

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

configure router mpls retry-timer 30

configure router mpls resignal-timer 30

configure router mpls retry-attempts 30

configure router mpls global-revertive 30

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.

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

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

The policy was not "committed" after creation.

Router R1 cannot reject the route because OSPF does not support import policies

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)