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

A transport tunnel can carry many service tunnels.

The transport label is unchanged throughout the transport network.

A single network port can carry more than one transport tunnel.

Both MPLS and GRE transport tunnels use a service label.

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.

mac-trace

svc-ping

Isp-trace

traceroute

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

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 for transport over the network.

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

DLC Header

Control Word

Transport Label

Service Label

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.

TRUE

FALSE

They are signaled between PE devices using MP-BGP.

They are swapped at each P router as a packet crosses the service provider network.

They are also known as the inner label or service label.

They indicate to the egress PE the VPRN to which a packet belongs.

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.

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.

A CE router.

A P router.

A PE router.

Both P and PE routers.

1

5

10

20

4078

4986

5014

5022

The labels are of local significance only, so other routers can use the same value.

10.10.10.1 has yet to send its own unique label.

Router R4 is using the same tunnel to send and receive to 10.10.10.1.

The service on 10.10.10.1 is down, so it is rejecting packets.

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.

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.

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.

They are used to identify the VRF table for a prefix at the receiving PE.

They are used by VPRNs to control the distribution of VPN routing information.

They are distributed to all PEs and CEs that are part of the VPRN.

They are distributed to PEs to identify the VRF table that a VPN-IPv4 prefix is associated with.

BGP

MP-BGP

LDP

MPLS

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

MP-BGP will advertise routes to other BGP sessions on the same PE without the need of policies.

The multi-protocol nature of MP-BGP allows VPRN routes to be converted into IPv4 routes in the provider core network.

MP-BGP is an enhanced version of BGP that can carry customer route prefixes for multiple VPRNs.

TRUE

FALSE

A mirror source listing port 1/1/4.

A mirror destination listing port 1/1/4.

A remote source command indicating the IP address of the service router he is configuring a local mirror on.

Verification that his IP/MPLS infrastructure is in place

None of the above.

No protocol extensions required

Only supported by OSPF and IS-IS

Transparent to routing neighbors

Uses Graceful Restart to inter-operate with other vendors

The system interface is configured with IPv6 address 2001DB8 1:100:1/128

All interfaces are configured for IPv4 and IPv6.

Interface " toR2 " is configured with a globally routed IPv6 address.

Interface " toR3 " is not configured for IPv6 with a global IPv6 address.

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

IP packets sent to an IP multicast address.

TCP packets sent to an IP multicast address.

IP packets sent to an IP unicast address.

UDP packets sent to an IP multicast address.

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.

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

Neighbor, adjacency, route table

Neighbor, topology, forwarding

Topology, routing, forwarding

There are only two databases: adjacency and topology

To support classful routing protocols.

To allow IP routes to be defined using any number of bits for the network portion of the address.

To allow interdomain routing between an IGP and EGP such as OSPF and BGP.

To simplify the allocation of IP address space by defining a fixed size for the network portion of the address for each of the address classes.

One.

One for each of the routers in area 0

One for each of the external routes exported by router R1.

Type 4 LSAs are not generated in this network topology.

L1 routers

L2 routers

L1/L2 routers

L1 and L2 routers

The OSPF internal preference

The IS-IS Level 1 internal preference

The IS-IS Level 2 internal preference

The OSPF external preference

The IS-IS Level 2 external preference

The IS-IS Level 1 external preference

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

Not So Stubby Area

Stub Area

Backbone Area

Standard Area

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.

An L1 adjacency will be formed.

An L1/L2 adjacency will formed

L2 adjacency will be formed

No adjacency will be formed

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.

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.

config > filter# default-action XXX

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

config > filter# default-mode XXX

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

89

87

85

83

Level 0

Level 1

Level 2

Level 0/1

Level 1/2

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.

The router is an ABR.

The router is an ASBR.

The router is at the end of a virtual link.

The router ' s interface is in a stub area.

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.

From the last 32 bits of the chassis MAC address

From the first 32 bits of the chassis MAC address

The loopback IP address

By using the command " config router ospf rid X.X.X.X "

From the system IP address

From the highest interface IP address

Show route-table

Show router routing-table

Show router route-table

Show static

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

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

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

1

49

47

45

39

Router R1

Router R2

Routers R1 and R2

Router R4

Router R2 does not have a route to the system address of router R1 and therefore cannot respond to the ping.

There is no default route configured on the PC.

Router R2 does not have a route configured to the PC.

Router R1 needs to be configured with a default route.

Not So Stubby Areas

Level 1 Areas

Stub Areas

Partially Stubby Areas

Area Border Router

Autonomous System Boundary Router

Designated Router

All routers within an OSPF area.

RIPv1, RIPv2, and BGP are distance vector protocols.

OSPF and IS-IS are distance vector protocols.

Routing tables are exchanged between neighbors; however, no routing table is transmitted beyond the immediate neighbor.

Distance vector protocols use the Dijkstra SPF algorithm.

Routers that participate in distance vector routing protocols maintain full knowledge of distant routers and how they interconnect

Metric is cost based

Slow convergence

Automatic summarization

Support CIDR

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

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

224.0.0.5

224.0.0.6

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

The system address of the router

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

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.

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.

RSVP-TE supports Connection Admission Control (CAC).

RSVP-TE enables simplified configuration of LSPs.

RSVP-TE supports path calculations that do not use IGP cost.

RSVP-TE provides support for traffic protection features.

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.

Router R1 updates its FIB after a new SPF calculation.

Router R1 switches to a secondary path.

Router R4 switches to a FRR path.

Router R4 switches to a standby secondary path.

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.

iocal-sdp ' and ' remote-sdp ' indicate that all services using these SDPs are pinged.

' Iocal-sdp ' and remote-sdp ' indicate that pings are initiated from both local and remote routers.

Both ' Iocal-sdp ' and ' remote-sdp ' take parameters to specify which SDPs are used for the test.

' Iocal-sdp ' indicates that the ping is sent in-band, and remote-sdp ' indicates the return ping is in-band.

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.

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.

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.

Configuring an autonomous system number in the global context.

Configuring a BGP group and peer parameters.

Configuring a VPN-IPv4 address family.

Configuring an export policy to advertise routes between PEs.

ping

Isp-ping

traceroute

Isp-trace

Option A

Option B

Option C

Option D

A-pipe

F-pipe

C-pipe

E-pipe

Black hole

Default gateway

Gateway path

Proxy ARP

The system ID

The loopback address

The sequence number of the hello packet

The device that first initiated communication becomes the DIS

configure router static-route 139.120.121.0/24 next-hop 138.120.199.2

configure router static-route 139.120.121.0/24 next-hop 138.120.199.1

configure router static-route 138.120.199.2/24 next-hop 138.120.199.1

configure router static-route 139.120.121.0/24 next-hop 139.120.121.2

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

193.45 32 0/20

193.45.0.0/21

192.45.32.0/21

192.45.0.0/20

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

Route distinguishes are used to ensure that VPRN IP prefixes are globally unique.

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

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

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

An IES requires a spoke SDP.

A virtual route table must be configured for an IES service.

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

An IES must have at least one SAP defined.

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 SAP can only be used by one service on a router.

A dedicated SDP needs to be created for each service.

A service is created on each site before the customer is created.

SAPs must be created before a service is created.

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.

5000

5004

5008

5014

The CE must be an IGP peer of the IES.

The CE must be on the same subnet as the IES.

The CE must use an E-pipe to connect to the IES.

The CE must fragment any frames that are too large for the IES.

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.

They both function as a Layer 2 switch from the service provider ' s perspective.

They both support SAP encapsulations of null, dot1Q and Q-in-Q.

They both use SAPs as the demarcation point between the customer and the provider.

MAC addresses are learned by VPLSes, but not by E-pipes.

The default service MTU on a VPLS service is 1514 bytes.

The default IP MTU of an IES is set based on the network port MTU.

During VC label signaling, the VC MTU is verified and must match.

All of the above.

The traceroute will only show one hop: R5-R6.

The traceroute will only show 2 hops; R5-R1 and R4-R6.

The traceroute will only show 3 hops: R5-R1, R1-R4 and R4-R6.

The traceroute will show one hop for each router in the provider core and one for each CE-PE hop.

MTU must match on both services,

Mesh-SDP with matching vc-id configured,

Spoke-SDP with matching vc-id configured.

Spoke-SDP.

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.

Router R1

Router R2

Router R3

Router R4

Router R5

Notification

Session

Discovery

Advertisement

Dot1Q

Q-in-Q

ATM

NULL

Nil

Incoming label

Outgoing label

Incoming interface

Outgoing interface

The router 10.10.10.1 is a PLR providing node protection for the router 10.10.10.3.

One-to-one fast reroute protection is requested by an LSP.

The bypass-link tunnel is used to avoid the link with the egress interface address 10.3.4.4.

The bypass-node tunnel is used to avoid the next-hop downstream router 10.10.10.3.

0

2

3

4

Layer 3 direct Internet access service.

Layer 2 point-to-point service.

Layer 2 multipoint-to-multipoint service.

Layer 3 IP multipoint-to-multipoint VPN service.

The router performs a unidirectional LSP test.

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

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

The MPLS TTL values are incremented at each request.

SDPs are a logical way to direct traffic from one router to another.

SDPs are a logical way to direct traffic between services.

SDP IDs are locally unique.

SDP IDs must be unique across the network.

SDPs are specific to one service type

SDPs must use MPLS for their encapsulation

With a Router LSA originated by router R1.

With a Router LSA originated by router R5.

With a Router LSA originated by router R4.

With an Inter-Area Prefix LSA originated by router R1.

With an Inter-Area Prefix LSA originated by router R5.

With an Inter-Area Prefix LSA originated by router R4.

It discards packets based on the source address.

It discards packets that match the destination prefix.

It returns ICMP unreachable messages.

It discards packets based on the egress port.

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.

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.

The packet is flooded out all router interfaces.

The packet is dropped and an ICMP unreachable message is sent back to the source.

The packet is silently discarded.

The packet is flooded out all interfaces and an ICMP unreachable message is sent.

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.

Routers broadcast the entire route table to all neighbors.

Information about directly connected links is sent to all neighbors.

An adjacency database is maintained by each router.

The sequence number for an update is incremented as it is flooded from router to router.

The topological database is the same for all routers in a single area.

Not so stubby area

Stub area

Backbone area

Normal area

Option A

Option B

Option C

Option D

configure router static-route 139.120.121.0/24 next-hop 138.120.199.2

configure router static-route 139.120.121.0/24 next-hop 138.120.199.1

configure router static-route 138.120.199.2/24 next-hop 138.120.199.1

configure router static-route 139.120.121.0/24 next-hop 139.120.121.2

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

Ping static 3.3.3.1

Ping static 0.0.0.0/0

Ping 3.3.3.1

Ping 0.0.0.0

30 second network updates

Classless routing

Broadcast advertisement

Poison Reverse

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.

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

PDU authentication.

The ability to customize the link cost metric.

Use of Bellman-Ford routing algorithm.

Classless routing.

Updates sent as layer 3 multicast.

Area ID W B.

Hello and Dead intervals PC.

Stub flag

Checksum values

The list of neighbors

MP-BGP sessions need to be configured in the service provider network to support a VPN-IPv6 address family.

PE routers must be configured to run MP-BGP and IPv6

PE-to-CE BGP sessions need to be configured to support IPv6.

The provider core must be configured to support IPv6

None of the above statements are false.

All of the above statements are false

1

4096

None. This encapsulation is not supported.

The number is limited only by the capacity of the router

An OSPF adjacency can be established on an IES interface.

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

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

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

Send a PathTear message towards router R6.

Send a PathTear message towards router R1.

Send a ResvTear message toward router R6.

Send a ResvTear message toward router R1.

The vc-id on the mesh-sdp must be explicitly configured.

The vc-id on the mesh-sdp is automatically assigned by a PE using the service id.

The VPLS service id, on all PE routers, does not have to match.

The VPLS service id, on all PE routers, must match.

If dynamic signaling is required, the signaling on all PE routers must be set to TLDP in the configuration of the SDPs.

The signaling on all PE routers will default to TLDP in the configuration of the SDPs; therefore, no configuration change is required for dynamic signaling.

config > router#

config > qos#

config > port#

config > service#

TRUE

FALSE

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.

TRUE

FALSE

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.

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.

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.

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.

A route target is a BGP extended community used to identify the VRF table for a prefix at the receiving PE

A route target is a mechanism from which VPRN controls the distribution of VPN routing information.

Route target attributes are earned in a MP-BGP as attributes of the route.

A route target is used by the PE router to identify the VRF that a VPN-lPv4 prefix is associated with.

All of the above statements describe a route target

None of the above statements describe a route target

The LSP must be enabled with CSPF on the head-end router.

Fast reroute must be enabled on the downstream routers.

A mixture of strict and loose hops must be defined in the primary path.

CSPF and fast reroute must be enabled on all downstream routers.

When the reserved bandwidth goes above 80M.

When the reserved bandwidth goes above 40M.

When an additional 80M bandwidth is reserved.

When an additional 40M bandwidth is reserved.

Epipe

Apipe

Fpipe

Ipipe

Cpipe

They are multicast to the All Hosts address.

They are broadcast to the subnet broadcast address.

They are multicast to the All Routers address.

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

The VPN label is signaled between PE devices using MP-BGP.

The VPN label is swapped at each P router as a packet crosses the service provider network.

The VPN label is also known as the inner label or service label.

The VPN label indicates which VPRN a packet should be sent to once it reaches the egress PE.

All of the above

Only C and D.

TRUE

FALSE

IES

VPWS

VPLS

VPRN

L2TP

P routers run IPv4 only. PE routers run IPv4 only and exchange IPv6 routes using MP-BGP.

P routers run IPv4 only. PE routers run both IPv4 and IPv6 and exchange IPv6 routes using MP-BGP.

P routers run IPv6 only. PE routers run both IPv4 and IPv6 and exchange IPv4 routes using MP-BGP.

P routers run IPv6 only. PE routers run IPv6 only and exchange IPv4 routes using MP-BGP.

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.

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.

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.

Tunnel Label

VC Label

Operational Control Word

VPI

VCI

Label swapping

Pushing a label on an unlabeled packet

Label allocation

Routing lookups

2

3

4

5

6

10

Hello message

Init message

Keepalive message

Label Mapping message

ACK message

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

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

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

The penultimate router will always receive unlabeled packets.

The penultimate router performs a double lookup on the packet.

The router is not configured as an asbr.

The router is not configured as an NSSA.

The export policy is not applied to OSPFv3.

The prefix list should be 2001:DB8:8::/46

The adjacency forms with the lower timeout value

The " show router Idp session " command output displays the adjacency in state " init "

The adjacency forms with the higher timeout value

The adjacency times out after 30 seconds

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.

Type 1 Router LSA

Type 2 Network LS A

Type 3 Summary LSA

Type 5 External LSA

Each PLR will signal a bypass tunnel that avoids the next-hop node or link.

When a failure occurs, the PLR will push an additional label onto the label stack and start forwarding traffic onto its bypass tunnel.

The ingress router will include a RRO object in the path message to indicate the routers that should be PLRs and MPs along the protected path.

The ingress router will set the local protection desired flag in the session attribute object of the path message to inform all routers along the protected LSP path to establish bypass tunnels.

When the bypass tunnel is in use, the MP will include the RRO object in its PathErr message, with the local protection in use flag set to notify the ingress router that it is using the bypass tunnel.

Type 1

Type 2

Type 3

Type 4

Type 5

The Maximum Allocation Model (MAM) provides the most efficient bandwidth utilization model

In the Maximum Allocation Model (MAM), each CT receives dedicated bandwidth constraints.

In the Russian Doll Model (RDM), a CT2 LSP automatically preempts a CT1 LSP.

Using the Russian Doll Mode! (RDM), a CT1 LSP may use unreserved CTO bandwidth.

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

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 CE routers run only IPv6.

The PE routers must run IPv4 and IPv6.

The P routers must run IPv4 and IPv6.

IPv6 routes on the PE routers may have an IPv4 address as the next hop.

The use of Broadcast messages in combination with Neighbor Advertisement messages.

The use of Anycast addresses in combination with Neighbor Advertisement messages.

The use of Solicited-node multicast addresses in combination with Neighbor Advertisement messages.

The use of Anycast addresses in combination with Link-Local Advertisement messages.

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.

2001:0da8:::0024:0000:4ab9:03

2001:0da8::0024::4ab9:0300

2001:da8::24::4ab9:300

2001:da8::24:0:4ab9:300

configure router mpls retry-timer 30

configure router mpls resignal-timer 30

configure router mpls retry-attempts 30

configure router mpls global-revertive 30

A Type 3 LSA is generated by an ASBR only when route summarization is configured.

A Type 3 LSA is generated by an ABR only when route summarization is configured.

A Type 3 LSA is generated by an ASBR to describe routes to routers outside the area.

A Type 3 LSA is generated by an ABR to describe routes to routers outside the area.

Router R4 will have a route to router R6 ' s system address with router R2 as the next-hop.

Router R4 will have a default route with router R2 as the next-hop.

Router R4 will have a default route with router R3 as the next-hop.

Router R4 will not have a route that can be used to reach the system address of router R6.

On the CEs only.

On the PEs only.

On only the branch office CE.

On both the CEs and PEs.

The neighbor ' s link-state database has newer information than what it received in the update.

The neighbor sends the update as an acknowledgement.

The neighbor ' s update indicates that it has run out of space in its LSDB.

The neighbor ' s update indicates that the sequence number received is the same as the one already in its link-state database.

The frame is dropped.

The VLAN tag is removed, and the frame is transported over the network.

The VLAN tag is kept, and the frame is transported over the network.

The VLAN tag is kept, a VLAN of 0 is added, and the frame is transported over the network.

vc-type ether

vc-type vlan

vc-type dotlq

vc-type null

It tests the IGP reachability of the far-end IP address of an SDP.

It tests that the MTU settings of a service are correct.

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

It tests the reachability of hosts connected to an SDP.

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

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

1

2

3

4

It results in forwarding based on the next packet header.

It indicates that the label is the bottom of the MPLS label stack.

It indicates that the label is the top of the MPLS label stack.

Any LSR that receives an S bit set to 1 must discard the 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.

AFI

IDI

HO-DSP

NSEL

Fixed total of 128 bits, where 64 bits are used for routing and 64 bits are used as an interface identifier.

Fixed total of 128 bits, where 32 bits are used for the global prefix, 32 bits are used for the subnet and 64 bits are used as an interface identifier.

Variable total length, where at least 48 bits are used for the global prefix, 48 bits are used for the subnet and 64 bits are used as an interface identifier.

Variable total length, where at least 64 bits are used for routing and 64 bits are used as an interface identifier

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.

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 1Gbps bandwidth unreserved.

0

2

3

6

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.

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

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.

RSVP

IPCP

TLDP

PPP

Either RSVP or LDP

M-BGP

TRUE

FALSE

sap 1/1/1

sap 1/1/1:*.0

sap 1/1/1:0.*

1/1/1:0

vc-type ether

vc-type vlan

vc-type dot1q

vc-type null

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.

vc-type ether

vc-type vlan

vc-type dot1q

vc-type null

2

12

30

44

100

The VC ID Cannot be determined from the output

Service providers can apply QoS, ingress/egress traffic shaping and policing on a per service basis.

Different customers with overlapping address space can be accommodated.

There is a clear demarcation of customer and service provider networks.

Customers can connect to the same service using different subnets.

3

4

6

12

It will show the hops taken between service endpoints.

It will test the delay across the service.

It will test the SDPs of a service in both directions.

It will test the round-trip connectivity of the service.

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.

2

3

4

5

6

7

Stub must be configured on Area 1 of router R1, and removed from Area 1 on router R3.

Stub must be configured on Area 1 of router R1 and Area 1 of router R3.

Stub must be configured on Area 0 of router R1 and Area 1 of router R3.

Area 1 of router R3 should be Area 0, in order to connect via stub to router R1.

Admin groups can be configured using the command " configure > router > mpls > admin-group " .

CSPF uses the information defined by admin groups when paths are computed for constraint-based LSPs.

By default, interfaces for which MPLS has been enabled are in the default admin group.

A LSP can make use of admin groups for constraint-based path calculations by including or excluding the admin group

There are five broadcast links and there are no point-to-point links.

There are five broadcast links and there are five point-to-point links.

There are five broadcast links. It ' s not possible to say how many point-to-point links there are.

It ' s not possible to say how many broadcast or point-to-point links there are.

Link

AS External

Router

Intra-Area Prefix

Isp retry-timer

Isp retry-limit

mpls resignal-timer

rsvp refresh-time

router rsvp keep-multiplier

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

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

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

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

10.32.1.2

10.1.478

1048.1.1

Cannot tell from this configuration

10.1.2.2

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.

1

2

3

4

6

7

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.

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.

Link

Intra-Area Prefix

Inter-Area Prefix

Inter-Area Router

Hello

Link-state request

Link-state acknowledgment

Link-state update

Database description

2001::FF:FE:14:6CAE

2001::1:FF:14:6CAE

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

FF02::1:FF14:6CAE

from prefix-list direct

match local

from protocol direct

match protocol direct

from protocol local

Router R1

Router R2

Router R3

Router R4

Router R5

Router R2 needs a static route to the PC.

Router R2 needs a default to router R1.

Router R1 needs a default route to router R2.

The static route should use a next-hop of 172.31.1.2

It can reduce the topological database size.

It can reduce the size of the route table.

It can reduce the number of Summary LSAs.

It can reduce the number of Router LSAs.

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.

Fixed filter

Shared explicit

Standby explicit LSP

Preemptive filter

Link capacity filter

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.

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.

It identifies the FEC.

It specifies the packet ' s header length

It identifies the origin of the packet.

It specifies the type of data contained in the packet

Label request message

Notification message

Address message

Keepalive message

Initialization message

Hello message

A POP label stack operation may 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 PUSH label stack operation may be performed.

The routing information base (RIB).

The routing table manager (RTM).

The equal cost multipath configuration (ECMP).

The forwarding information base (FIB).

The link state database (LSDB).

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.

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.

IGP-based LSPs are established solely from information contained in routing tables.

The constraint-based routed LSP is calculated at the ingress of the network, based on the router database and user defined constraints.

The constraint-based routed LSP is calculated at each hop of the LSP, based on the route table and user defined constraints.

IGP-based LSPs must use LDP signaling.

0

1

2

3

4

Router R2 needs a static route to the PC.

Router R2 needs a default to router R1.

Router R1 needs a default route to router R2.

The static route should use a next-hop of 172.31.1.2

The router sends a copy of the LSP from its database to its neighbor.

The router sends a PSNP to its neighbor describing the LSP in its database.

The router updates its database with the LSP and floods a copy to its other neighbors.

The router sends a PSNP to its neighbor to request the LSP.

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

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

Router R4 swaps both the RSVP-TE LSP label and LDP transport label received with new labels,

Router R4 swaps the VPN service label received with a new label.

Router R4 uses the same RSVP-TE LSP label as the one received from router R3.

Router R4 uses the same LDP transport label as the one received from router R3.

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.

Independent control mode, downstream on demand

Independent control mode, downstream unsolicited

Ordered control mode, downstream on demand

Ordered control mode, downstream unsolicited

The VRF is a virtual router on the PE router that contains the customer ' s routes for the VPRN

Each PE maintains multiple VRFs based on the number of PE peers it connects to.

Each PE has a VRF for each VPRN service provisioned on the router.

All of the above.

Only A and C.

Only A and B

The mirror destination configuration on PE5 is missing the " remote-source " command,

The mirror destination on PE3 needs a " remote-source " command.

The mirror service IDs on the local and remote destinations must match.

The mirror source on PE3 needs a " remote-source " command.

The mirror source command on the remote PE3 needs a command that tells it to monitor port 1/1/2.

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.

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

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

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

Enable link-protection only on router R4.

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.

It supports traffic protection using IGP equal cost paths.

It supports CAC to prevent resource overbooking.

It supports LSPs with traffic engineering constraints.

It supports LSPs that follow the IGP best path.

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.

Configure service sap sap-id access

Configure port port-id Ethernet mode access

Configure port port-id Ethernet mode network

Configure port port-id mode access

Configure port port-id mode network

Each PLR signals a protection tunnel that avoids the downstream node.

A single protection tunnel can protect all LSPs that go through the same hop.

A link protection tunnel is signaled if a node protection tunnel cannot be established.

Protection tunnels used in this LSP are also detour tunnels.

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 PLR issues an RSVP PATH message to the tail-end requesting the address of the MP.

The PLR learns the address of the MP from the ERO.

The PLR learns the address of the MP from the RRO.

The PLR learns the address of the MP from the targeted RSVP Hello message.

The PLR knows the address of the MP is the same as the tail-end router.

Send a RESV Tear message toward router R6.

Send a RESV Tear message toward router R1.

Send a RESV Error message toward router R6.

Send a RESV Error message toward router R1.

sap 1/1/1:0.*

sap 1/1/1

sap 1/1/1:*.4

sap 1/1/1:4.*

Multiple MP-BGP sessions are required to carry VPN-IPv4 and VPN-IPv6 routes.

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

In 6VPE, MP-BGP is used to advertise IPv6 prefixes and the associated VPRN label.

In 6VPE, the provider core routers are IPv6-unaware.

All of the above statements are true.

All of the above statements are false.

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

The secondary path will take R1-R2-R4-R6.

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

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