4A0-104 Practice Exam Questions with Answers Alcatel-Lucent Services Architecture Certification

sap 1/1/1

sap 1/1/1:*

sap 1/1/1:0

sap 1/1/1:1

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.

9000

9004

9008

9022

9036

Route distinguishes are 12 bytes in length

Route distinguishes are appended to IPv4 prefixes to form 16 byte VPN-IFV1 prefixes.

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

CE routes must be configured with the proper route distinguishes for the VPRN they are associated to

All of the above statements are true.

All of the above statements are false.

0

2

3

6

PE1>config>router>bgp#info

--------------------------------------------

group "multi-bgp"

family vpn-ipv6

neighbor 10.10.10.2/32

local-address 10.10.10.1

peer-as 64496

exit

exit

PE1>config>router>bgp#info

-------------------------------------------

group "multi-bgp"

family ipv6 vpn-ipv4

neighbor 10.10.10.2

local-address 10.10.10.1

peer-as 64496

exit

exit

PE1>config>router>bgp#info

--------------------------------------------

group "multi-bgp"

family vpn-ipv6

neighbor 10.10.10 2

local-address 10.10.10.1

peer-as 64496

exit

exit

PE1>config>router>bgp#info

--------------------------------------------

group "multi-bgp"

family ipv6 vpn-ipv6

neighbor 10.10.10.2/32

local-address 10.10.10.1

peer-as 64496

exit

exit

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

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

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

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

Traffic is flooded to all SAPs in the service.

Traffic is flooded to all SAPs and spoke SDPs in the service.

Traffic is flooded to all SAPs and mesh SDPs in the service.

Traffic is flooded to all SAPs, spoke SDPs, and mesh SDPs in the service.

The traffic is not flooded.

1500

1508

1514

1522

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.

Traffic is flooded to all SAPs in the service.

Traffic is flooded to all SAPs and spoke SDPs in the service.

Traffic is flooded to all SAPs and mesh SDPs in the service.

Traffic is flooded to all SAPs, spoke SDPs. and mesh SDPs in the service.

The traffic is not flooded.

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.

The mesh SDP on router R4 has been shutdown.

The mesh SDP on 10.10.10.1 has been shutdown.

The service MTU on 10.10.10.1 has been set to a different value.

The IngLbl and EgrLbl that router R4 has for 10.10.10.1 are identical.

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.

A packet receives a service label and a transport label at the ingress PE.

A packet has its servicelabel 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.

An Ipipe is a point-to-point Layer 2 VPN capable of only carrying Ethernet payloads. An Epipe interworking refers to the transportation of ATM/FR traffic over an Epipe.

An Ipipe is used for performing Ethernet interworking with ATM/FR/PPP using bridged-PDUs. An Epipe interworking is used for performing Ethernet interworking with ATM/FR/PPP using routed-PDUs.

An Ipipe is used for performing Ethernet interworking with ATM/FR/PPP using routed-PDUs. An Epipe interworking is used for performing Ethernet interworking with ATM/FR/PPP using bridged-PDUs.

None of the above.

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

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

An Epipe service that has 3 or more SAPs configured.

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

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

1512

1522

1536

1542

vprn-ping

sdp-ping

traceroute

Isp-trace

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.

ADSPEC

CSPF

Service ping

LSP trace

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

RSVP

IPCP

TLDP

PPP

Either RSVP or LDP

M-BGP

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.

An IES has a configurable VC MTU.

An IES interface has an IP address assigned to it.

IES supports QoS.

An IES requires a spoke SDP.

1520

1540

1548

1556

vc-type ether

vc-type vlan

vc-type dot1q

vc-type null

The dot1Q default SAP (port:*) can be used to pass VLAN tags transparently through a network.

The dot1Q null SAP (port:0) accepts all tagged frames and untagged frames.

The dot1Q default SAP (port:*) accepts all untagged frames and any frames with tag values that are not used as a service-delimiting value on another SAP.

A dot1q null SAP (port:0) and a dot1q default SAP (port:*) cannot both be defined on the same port.

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

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

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.

A mirror source with a defined source type.

A mirror source defined with an SDP destination.

A mirror destination with a SAP defined.

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

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.

The frame is dropped.

The frame's outer tag is changed to match the SAP, and it is accepted.

The frames outer tag is dropped, and the frame is accepted.

The frame's tags are removed, and the frame is accepted.

VRF information is advertised between PEs using MP-BGP.

VRF tables are used to forward traffic to CEs.

P routers use VRF tables to maintain customer-specific information.

VRF tables provide isolation between customers.

show service id 5

show service ies

show service service-using ies

show service id 5 base

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

TRUE

FALSE

TRUE

FALSE

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

TRUE

FALSE

TRUE

FALSE

The customer maintains complete control over routing.

The adding of new sites is simplified; no re-configuration is required at existing sites.

The clear demarcation of functionality between service provider and customer makes troubleshooting easier.

All of the above.

TRUE

FALSE

TRUE

FALSE

A VPLS service does not use an FDB.

An FDB is maintained on the PE router to track MAC addresses learned from all traffic through the router.

An FDB is maintained on the PE router to track MAC addresses learned from all VPLS services on the router.

A separate FDB is maintained for each VPLS service to track MAC addresses learned from each service.

For each VPLS service, two FDBs are maintained to track MAC addresses; one for unicast traffic and one for multicast and broadcast traffic.

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

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

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

6VPE requires an IPv6-aware MPLS core.

Both C and D are false.

All of the above statements are true.

By default, a 7750 SR does not advertise all routes in the VRF to a CE router.

The default 7750 SR behavior describes all routes in a VRF that are advertised to other PE routers.

By default, a 7750 SR does not advertise all routes in the VRF to other PE routers.

By default, a 7750 SR advertises all routes in the VRF to a CE router.

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.

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

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

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

6VPE requires an IPv6-aware MPLS core.

Both C and D are false.

All of the above statements are true.

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.

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.

Epipe

Fpipe

Apipe

Ipipe

Cpipe

Gpipe

TRUE

FALSE

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.

TRUE

FALSE

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.

Yes. A routing policy is required to advertise routes between PE routers in a VPRN

No. A routing policy is not required; the default behavior on the 7750 SR is to advertise all VPRN routes between PE routers.

A routing policy is required only when BGP is used as the PE-CE routing protocol, as shown in the exhibit.

A CE1 system interface can not be advertised to PE2 since the CE routers are not aware of the VPRN.

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

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.

Epipe

Apipe

Fpipe

Ipipe

Cpipe

IES does not support QoS.

IES has a configurable IP-MTU

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

An IES interface has an IP address assigned to it.

1

4096

None. This encapsulation is not supported.

The number is limited only by the capacity of the router

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

They reduce the number of SDPs that need to be configured.

They can be used to work around physical topologies that prevent a fully meshed deployment.

They prevent loops that can be introduced by mesh deployments.

They can simplify the implementation of security policy enforcement and packet inspection.

An echo request is sent based on the LSP's label stack.

Echo reply packets may not take the same path as the LSP.

The IP destination address is used to initiate echo requests,

The test fails if the LSP is not operationally up.

The PE routers of the service are responsible for learning MAC addresses.

Flooding ensures that all PEs in a fully-meshed VPLS will learn the source address of all traffic.

MAC learning reduces flooding of frames with previously learned addresses.

Multiple VPLSes on the same PE share the same MAC FDB.

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.

Customer ID and SAP ID.

Customer ID and Service ID.

SAP ID and Service ID.

SDP ID and Service ID.

SDP ID and SAP ID.

SDP ID and VC ID.

The IES's interface must be an IGP peer with the CE.

The IES must use an IP address that is different than the C£.

The IES can only include one SAP for the CE.

The IES must include a network port.

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.

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

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

SAPs can have QoS policies assigned to them.

Multiple SAPs can be defined on the same port.

3

4

6

8

An SDP is not required for a local service.

A single SDP can carry different types of services.

An SDP can simultaneously support GRE and MPLS encapsulation.

An SDP can use the system IP address to indicate the far-end router.

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.

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.

Tunnel Label

VC Label

Operational Control Word

UNI

NNI

Family ipv4

Family ipv6

Family ipv4 ipv6

Family vpn-ipv4

Family vpn-ipv4 vpn-ipv6