Free 4A0-105 Exam Dumps Preview

Filter Policies can only be applied on egress.

Filter Policies can be based on IP, MAC, and VPI/VCI addresses.

Any number of ingress and egress filter policies can be associated with a SAP.

An IP filter and a MAC filter can be applied on the ingress SAP at the same time.

None of the above.

Bridge B

Bridge C

Bridge D

TRUE

There is no effect. The MAC addresses for the l-VPLS age out independently of the aging of B-VPLS addresses.

By default, the remote-age timer of the B-VPLS is configured to 0 and addresses do not age out. The l- VPLS uses its own timer.

The same timer is used for B-VPLS and l-VPLS addresses on the node.

A VPLS is a multipoint Layer 2 service.

A VPLS allows multiple customer sites to be connected in a single bridged domain.

With an IP/MPLS infrastructure, service providers can provide multiple VPLS services over a common
IP/MPLS infrastructure.

The VPLS switches traffic based on MAC address associated to the appropriate SAP.

The service MTU must be equal to or smaller than 1514 bytes.

The service MTU must be equal to or greater than 1514 bytes.

The service MTU can be any value.

If the FDB reaches the limit, the router will discard frames.

Discarding frames when the FDB limit is reached could deny SLA guarantees.

The CE must be configured with an MC-LAG to both PE devices.

There is no configuration required on the CE.

The CE must be an Alcatel-Lucent 7750 SR.

All untagged frames will be dropped.

The source MAC address of a frame with a top tag of 200 and bottom tag of 300 will be populated in VPLS 3.

All frames with more than one tag will be dropped.

The source MAC address of a frame with a single tag of 500 will be populated in VPLS 1.

The switch with the highest priority becomes the root.

The switch with the lowest MAC address always becomes the root.

The switch with the highest MAC address always becomes the root.

Event notification.

Loopback control.

Variable request.

Variable response.

The frame is dropped.

The frame is always flooded

The frame is discarded if the destination is unknown.

More information is required to determine the fate of this new frame.

VPLS 10 and VPLS 20 are not actually configured as a user VPLS.

VPLS 10 and VPLS 20 are not using the same spoke-sdps that the management VPLS is using.

Based on the output there is now way of telling if there is a problem with the configuration.

On the PE the endpoint has been configured with "supress-standby-signalling"

On the PE the endpoint has been configured with "no supress-standby-signalling"

On the MDU the endpoint has been configured with "supress-standby-signalling"

The sdp id is different on the far-end.

LDP is disabled on the far-end.

The mesh-sdp is administratively shutdown on PEL

There is an MTU mismatch.

A management VPLS carries customer traffic over the non-blocking spoke-SDP

The management VPLS must be created before the user VPLS.

The vc-id is signaled in the control plane.

There is a vc-id to vc-label mapping.

The vc-id has point to point significance.

100

200

1

On initialization and then every hello-interval.

Every 1 second.

Never.

The same timer is used in all VPLS types.

Higher than the default timer of an I-VPLS.

The same timer as an l-VPLS.

The same as the number of alternate ports in the topology

The same as the number of root ports

1 per switch

In a dynamic environment where MAC addresses are changing rapidly, the lower the age-time, the larger the fdb-table-size should be.

In a dynamic environment where MAC addresses are changing rapidly, the higher the age-time, the smaller the fdb-table-size should be.

There is no relationship between the age-time and the fdb-table-size.

H-VPLS

M-VPLS

MC-EP

Designated

Listening

Root

Forwarding