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

Next Header

Traffic Class

Flow Label

Payload Length

Options

Challenge handshake authentication protocol (CHAP)

Two factor authentication

MD5 authentication

Extensible authentication protocol (EAP)

A packet with a destination anycast address is sent to all nodes on the local link.

A packet with a destination anycast address is sent to all nodes on the local network.

A packet with a destination anycast address is sent to all nodes that have joined the anycast group.

A packet with a destination anycast address is sent to the nearest node that is assigned the anycast address

A packet with a destination anycast address is sent to all nodes that are assigned the anycast address.

RSVP uses downstream on demand label distribution mode.

LDP uses conservative label retention mode.

LDP advertises label mappings to all peers for which it might be a next-hop for a given FEC.

RSVP distributes a label mapping for a FEC when it has been requested to do so.

The LSP can use facility and one-to-one FRR simultaneously.

The LSP is limited to node protection.

A single protection tunnel is used for all LSPs with the same path.

A detour protection tunnel is created for the LSP.

Disable route summarization on router R3.

Enable LDP aggregate prefix match.

Create an import policy to accept 10.10.10.2/32 and 10.10.10.4/32.

Disable LDP exact match on 10.10.10.2/32 and 10.10.10.4/32.

Node protection tunnels detour around a failed next downstream router.

Node protection tunnels can only be requested for a primary LSP path.

Node protection tunnels are only used by one-to-one Fast Reroute.

Link protection tunnels are established if a router is unable to establish node protection tunnels.

Each implementation can use it as they see fit.

It is used to carry the Ether type value.

It is used to carry the TTL value.

It is used to carry QoS classification.

It is used to carry fragmentation flag information.

Hello message

Init message

Keepalive message

Label Mapping message

ACK message

The outer label TTL will be 249 and the inner label TTL will be 250.

The outer label TTL will be 249 and the inner label TTL will be 251.

The outer label TTL will be 251 and the inner label TTL will be 251.

The outer label TTL will be 251 and the inner label TTL will be 252.

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.

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.

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.

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.

TRUE

FALSE

Fast reroute capability

Control traffic prioritization

Route redistribution

Traffic engineering extensions

Cut through forwarding

The LSP will go through the path R1-R2-R4-R6.

The LSP will go through the path R1-R3-R5-R6.

The LSP is down because router R1 detects that no path can meet its constraints.

The LSP is down because router R4 detects that no path can meet its constraints.

The LSP can use protection tunnels used by other LSPs.

The LSP can use facility and one-to-one FRR simultaneously.

The LSP is limited to link protection.

A detour protection tunnel is created for this LSP.

Configure an autonomous system number in the global context.

Configure a BGP group and peer parameters.

Configure a VPN-IPv4 address family.

All of the above steps are mandatory.

None of the above steps are mandatory.

Mesh SDPs assist MAC learning by flooding traffic to other mesh SDPs.

A PE keeps a single FDB for all VPLSes it has.

Frames received on a SAP that are broadcast, multicast or unknown are flooded.

The FDB only stores the MAC addresses of remote sites.

TRUE

FALSE

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.

Both routers will generate OSPF Hello packets.

The system interface is missing in one configuration so OSPF will not operate correctly.

The interface type settings differ, but OSPF will still operate correctly.

Metric values differ, but this does not prevent OSPF operation.

Ping static 3.3.3.1

Ping static 0.0.0.0/0

Ping 3.3.3.1

Ping 0.0.0.0

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

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

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

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

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

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

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.

ping

Isp-ping

traceroute

Isp-trace

Option A

Option B

Option C

Option D

A default route on router R2 to router R1.

A default route on the PC to router R2.

A static route on the PC to router R2 and a static route on router R2 to the PC.

A default route on router R1 to router R2.

TRUE

FALSE

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.

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.

Convergence is triggered when the adjacency between routers R1 and R2 drops as a result of hello timeouts.

Convergence is triggered when the physical interfaces between routers R1 and R2 go down.

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

Convergence is triggered when an LSA is sent from router R1 to router R2 to indicate that the link is down.

show router mpls Isp "LSP 1" originate

show router mpls Isp "LSP 1" path detail

show router rsvp session originate

show router rsvp session "LSP 1"

2001::FF:FE:14:6CAE

2001::1:FF:14:6CAE

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

FF02::1:FF14:6CAE

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

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

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

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

P router

LSR

eLER

iLER

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.

Router R1 generates a Type 5 LSA that is flooded to area 1 only.

Router R1 generates a Type 5 LSA that is flooded to areas 1 and 0. Router R6 generates a Type 5 LSA that is flooded to area 2.

Router R1 generates a Type 5 LSA that is flooded to areas 0.1, and 2.

Router R3 generates a Type 5 LSA that is flooded to areas 0 and 2

Type 5 LSAs are not generated in this network topology.

The router is correctly configured.

A reference-bandwidth is not configured on the router.

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

The interface metric must be manually configured to 100.

Down

Initializing

2-way

Full

The packet can only be forwarded as an unlabeled packet.

The packet can be forwarded as a labeled or unlabeled packet, depending on the received label value.

The packet can be forwarded as a labeled or unlabeled packet, depending on the destination IP address in the payload

The packet can only be forwarded as a labeled packet.

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.

Disable route summarization on router R3

Enable LDP aggregate prefix match

Create an import policy to accept these FECs

Disable LDP exact match on the specified FECs

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.

Label request message

Notification message

Address message

Keepalive message

Initialization message

Hello message

Exchange

Up

Down

2-Way

CSPF looks for the delta bandwidth, taking down the first path if necessary.

CSPF looks for the delta bandwidth, implementing make-before-break.

After 5 failed attempts to find the bandwidth requested, the head end disables the LSP.

CSPF looks for the entire bandwidth requested, implementing MBB.

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.

Router LSA

Network LSA

Intra-Area Prefix LSA

Link LSA

Router LSA

Network LSA

Intra-Area Prefix LSA

Link LSA

Administrative Groups

Shared Risk Link Groups

Strict hop LSP paths

Fast reroute

Label space mode

Label retention

Control mode

Keepalive factor

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

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)

LSA flooding mechanism.

Totally stubby areas.

MD5 authentication.

DR and BDR election.

Router R1

Router R4

Router R2

Router R3

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

IS-IS routers exchange updates by sending UDP packets to a multicast address.

IS-IS routers exchange updates using IP multicast packets.

IS-IS routers exchange updates using Ethernet multicast packets.

IS-IS routers exchange updates by sending packets to the subnet broadcast address.

Hello, link state update, link state packet, link State acknowledgement, database description.

Link state update, link state refresh, link state acknowledgement, database description, notification.

Hello, link state refresh, link state update, link state acknowledgement, link state authentication.

Hello, link state update, link state request, link state acknowledgement, database description.

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.

mac-trace

svc-ping

Isp-trace

traceroute

BGP

MP-BGP

LDP

MPLS

The VC-IDs used between the E-pipe and VPLS must match.

The E-pipe must maintain a MAC FDB in order to connect to the VPLS.

The service ID of the E-pipe can be different from that of the VPLS.

The service MTU of the VPLS and E-pipe must match.

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.

All services bound to the same SDP must be the same service type.

All services bound to the same SDP will have the same transport encapsulation.

Any operation on an SDP will affect all services bound to that SDP.

An SDP is used to direct traffic for a service from one router to another.

5000

5004

5008

5018

The SDP itself (outside of the epipe context).

The SAP in the E-pipe.

The mesh SDP in the E-pipe.

The spoke SDP in the E-pipe.

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.

An export policy is required on PE1 to advertise routes to CE1.

An export policy is required on CE1 to advertise local routes to PEL

An export policy is required to advertise routes between the PE routers.

No export policy is required on PE2 or CE2 due to the static routes.

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

VPN-IPv4 allows BGP to distinguish between duplicate prefixes originating from different customers.

In a VPRN, data traffic is carried in packets that have VPN-IPv4 addresses.

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

sap 1/1/1

sap 1/1/1:*

sap 1/1/1:0

sap 1/1/1:1

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.

1512

1522

1536

1542

Different authentication types are not possible because IS-IS only supports password authentication.

An adjacency will not be formed.

The two routers negotiate the authentication type and then reach the up state.

Only an L2 adjacency will form, as long as both routers are L2 capable.

AS External

Intra-Area Prefix

Inter-Area Router

Inter-Area Prefix

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

ping static 10.5.5.5

ping static 0.0.0.0/0

ping 10.5.5.5

ping 0.0.0.0

1

2

3

4

6

7

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.

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

Router LSA

Network LSA

C Summary network LSA

Summary router LSA

Type 5 (AS external) LSAs

4 bytes

6 bytes

8 bytes

Variably between 4 and 8 bytes

Default path

Default gateway

Gateway path

Proxy ARP

Not So Stubby Area

Stub Area

Backbone Area

Standard Area

Acts as a logical way to direct traffic from one SAP to another on a single node.

Acts as a logical way to direct traffic from one service to another on a single node.

Acts as a logical way to direct traffic from one access port to another.

Acts as a logical way to direct traffic from services on one router to services on another.

VPN-IPv4 address families are required in order for routes to be exchanged with the PE.

Only default IPv4 address families are required since the CE is not aware of the VPRN service

Either IPv4 or VPN-IPv4 address families can be configured on the PE-CE BGP session

An IPv4 address family configuration is required for the PE-PE configuration.

family ipv4 ipv6

family vpn-ipv4ipv6

family vpn-ipv4 vpn-ipv6

family ipv6 vpn-ipv6

It tests uni-directional or round-trip in-band connectivity.

It tests the reachability of hosts that are using an SDP.

It tests the reachability of the far-end IP address of an SDP through its tunnel.

It can be used by specifying only an SDP ID.

TRUE

FALSE

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

Independent control mode, downstream on demand

Independent control mode, downstream unsolicited

Ordered control mode, downstream on demand

Ordered control mode, downstream unsolicited

3

4

6

12

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.

More than one SAP can be configured on a physical port that is configured for null encapsulation.

Dot1Q Ethernet encapsulated access ports can support multiple SAPs and services.

SAPs can be created on ports designated as "Network".

SAPs can only be created on Ethernet ports.

The service takes a route determined by the IGP.

The tunnel does not use a service label.

The service label is swapped at each hop in the transport network.

The tunnel is bidirectional and only requires configuration at one end of the service.

ping

sdp-ping

svc-ping

Isp-ping

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.

To mirror service requirements of a customer with a single branch office and multiple remote sites

To utilize unused ports of a service router until they are required for a service.

To replicate traffic from a service port to another port for debugging or monitoring functions

To ease the configuration burden of services that support a large number of subscribers

All of the above

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.

The frame egresses from 1/1/1:6 with no VLAN tag.

The frame egresses from 1/1/1:6 with VLAN tag 5.

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

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

Independent control mode

Ordered control mode

Liberal label retention mode

Conservative label retention mode

Downstream on demand label distribution mode

2

3

4

5

6

10

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.

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

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.

Link-based and T-LDP sessions may be configured on the same LSR.

T-LDP supports sessions between non-directly connected devices.

T-LDP can be configured between directly connected devices.

T-LDP Hello messages are sent to a multicast address.

distributed/virtual

local/sub

routed/Layer 3

distributed/routed

Layer 2/loopback

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.

Admin groups

Hop-limit

Strict hops

TE-Metric

TRUE

FALSE

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.

configure epipe service-id customer customer-id create

configure service epipe service-id customer customer-id create

configure epipe service-id create

configure epipe service-id customer customer-id create

configure epipe service service-id customer customer-id create

SDP ID

Service ID

Customer ID

SAP ID

Label swapping

Pushing a label on an unlabeled packet

Label allocation

Routing lookups

Hop count and 16

Hop count and 15

Link cost and 15

Link cost and 16

Broadcast

Non-broadcast multi-access

Point-to-point

Point-to-multipoint

Show ospf neighbors

Show router ospf neighbors

Show router ospf adjacency

Show ospf adjacency

Option A

Option B

Option C

Option D

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.

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