4A0-104 Alcatel-Lucent Services Architecture Questions and Answers

sap 1/1/1

sap 1/1/1:*.0

sap 1/1/1:0.*

1/1/1:0

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.

MP-BGP in the provider network needs to support the VPN-IPv6 address family.

PE routers must be configured to run MP-BGP.

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

The provider network core must be configured to support IPv6.

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.

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.

IPCP

LDP

PPP

TLDP

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.

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

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.

VPRN is an IP service that connects multiple sites in a single routed domain over the provider-managed IP/MPLS network.

Each VPRN consists of a set of customer sites that must connect to the same PE router

In a VPRN service, each customer router becomes a routing peer to other customer routers

VPRN provides customer routers with transparent IP connectivity without knowledge of the MPLS core

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

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

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

The vc-id on the spoke-sdp can be configured to match the service id.

The vc-id on the mesh-sdp can be configured to match the service id.

The vc-id on the spoke-sdp does not have to be explicitly configured and will use the service id.

The vc-id on the mesh-sdp does not have to be explicitly configured and will use the service id.

TRUE

FALSE

TRUE

FALSE

L-LDP

T-LDP

RSVP-TE

MP-BGP

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.

A-pipe

C-pipe

E-pipe

F-pipe

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

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

Change the MTU of the SDP attached to the VPLS to match the service MTU of the VPLS.

Set the DNF flag on the IES service.

A VPLS service does not use a MAC FDB.

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

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

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

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

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

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

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.

1500

1508

1514

1522

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.

A route target is used to distinguish to which VRF table a prefix belongs.

A route target appended to an IPv4 prefix produces a VPN-IPv4 prefix.

Multiple route targets can be part of a single MP-BGP update.

Route targets must be configured for VPRNs.

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.

Tunnel Label

VC Label

Operational Control Word

UNI

NNI

"ping 192.168.20.1"

"oam vprn-ping 100 source 192.168.10.1 destination 192.168.20.1"

"oam vprn-ping 100 source 192.168.20.1 destination 192.168.10.1"

"ping 10.10.10.6" (router R6's system IP)

7958

7978

8022

8042

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.

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.

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.

The SDP must be a mesh

The SDP must be a spoke.

Once the SDP is configured on both PE routers, both the services will be operationally up without further configuration changes.

The Layer 2 MTUs must match between the IES and the VPLS

The Layer 2 MTU must be 14 bytes smaller on the VPLS than it is on the IES.

Dot1Q

Q-in-Q

ATM

NULL

Nil

config>service# epipe service-id shutdown

config>service# vpws service-id shutdown

config>service# service-id shutdown

config>port# port-id shutdown.

config>service# epipe service-id disable

Each router requires 1 VPLS service.

Each router requires 2 VPLS services.

Each router requires 1 SDP with 2 LSPs, one to each of the other 2 routers.

Each router requires 2 SDPs.

Each router requires 3 SDPs

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

sap 1/1/1

sap 1/1/1:*

sap 1/1/1:*.0

sap 1/1/1:0*

sap 1/1/1:0

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