4A0-C02 Sample Questions Answers

The SoO attribute can be used to uniquely identify the site from which a PE learns routes.

Before a PE redistributes a VPN-IPv4 route, it can assign an SoO attribute to the route.

The SoO attribute can be used to prevent loops from a single site with multiple CE-PE connections.

The SoO attribute can be used as matching criteria when redistributing routes from the CE to the PE.

CSC does not allow a customer carrier to offer Layer 2 services to its end customers.

A CSC VPRN is configured on the network provider's CSC-PE routers.

CSC eliminates the need for customer carriers to build and maintain their own MPLS backbone.

The network provider provides an MPLS VPN backbone to the customer carrier.

No need to build and maintain its own backbone.

The solution scales as the number of serviced customer carriers increases.

The solution scales as the number of VPNs offered by the customer carriers increases.

The ability to manage end-customer services.

There will be increased memory usage on the PE

There will be increased CPU utilization on the PE

The CE will reject the overlapping prefix

The PE will not recognize the prefixes as being different

There is no issue with overlapping address space in a traditional Layer 3 VPN

The EXP field in the bottom MPLS header will be marked.

The EXP field in both the top and bottom MPLS headers will be marked.

For Layer 2 services, the top MPLS header will be marked; for Layer 3 services, the bottom MPLS header will be marked.

The EXP field in the top MPLS header will be marked.

Neither the top nor the bottom EXP field will be marked since EXP remarking can only be done on the network ingress.

All in-profile packets in round-robin, then all out-of-profile packets in biased round-robin.

In-profile EF packets, then in-profile H2 packets, then in-profile AF packets, then out-of-profile EF packets, then out-of-profile H2 and AF packets, and then out-of-profile BE packets.

In-profile EF, H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF packets, then in-profile H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF and H2 packets, then in-profile AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

64

8

3

16

1

Router R2 only.

Routers R2 and R3 only.

Routers R2, R3 and R4 only.

Routers R2, R3, R4and R5.

Access ingress, access egress, network egress

Access ingress, network ingress, network egress

Port ingress, port egress, shared bi-directional

Port ingress, port egress, network egress

Port ingress, network ingress, network egress

Unlike VPLS. VPWS appears as a multi-hop network to the customers.

Unlike VPLS, VPWS allows CEs that are member of the same service instance to communicate with each other as if they are connected via a bridged LAN.

Unlike VPWS, VPLS allows customers to view the network as a routed network.

Unlike VPWS, VPLS is a service where customer MAC addresses are learned.

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

Microflow reservations using RSVP

DSCP to EXP translation

Traffic classification

Automatic profiling and policy configuration

Buffer memory management

Traffic scheduling

Has the ability to distinguish traffic in 32 different ways.

Uses the RSVP protocol to create microflows through a network.

Has the ability to manually configure foiwarding classes through a network.

Uses the RSVP protocol to create macroflows through a network.

Level 8 within CIR.

Level 8 between CIR and PIR.

Level 8, once all PIR is serviced.

Level 1 within CIR.

Level 1 between CIR and PIR.

Level 1, once all PIR is serviced.

An AS is a set of routers under a single technical administration.

An AS efficiently advertises all IGP known routes to other ASs.

An AS presents a consistent routing policy to other autonomous systems.

An AS has a 2-byte or 4-byte AS number assigned.

The DSCP value will be set to af21.

The DSCP value will be set to af23.

The DSCP value will remain as ef.

The EXP value, in the MPLS headers, will be set to 4.

The EXP value, in the MPLS headers, will be set to 3.

Link LDP or MP-BGP

Link LDP or RSVP-TE

T-LDP or MP-BGP

T-LDP or RSVP-TE

The primary contributors to latency are distance, scheduling, and congestion.

The weighted round robin scheduling algorithm will result in more delay for high priority traffic than the regular round robin algorithm.

The round robin scheduling algorithm will result in less jitter for low priority traffic than a strict priority scheduler.

Packet loss can be reduced by decreasing the amount of buffer space available to a queue.

Latency can be reduced by increasing the amount of buffer space available to a queue.

65540

65540 1

65540 65540

65550 65540

Lower local preference is preferred over higher local preference.

Higher MED is preferred over lower MED.

Higher origin code is preferred over lower origin code.

Lower BGP router ID is preferred over higher BGP router ID.

TRUE

FALSE

MP-BGP, LDP, RSVP-TE

LDP, RSVP-TE, GRE

MP-BGP, RSVP-TE, GRE

MP-BGP, LDP

MP-BGP only

There are a maximum of 8 levels of priority serviced using a round-robin algorithm.

The default scheduler will spend an equal amount of time in each queue, as long as there is traffic present

The H1 internal forwarding class will receive its CIR before AF traffic.

Orphaned queues will be scheduled out of the BE queue.

A queue servicing EF and AF traffic will require explicit configuration to set the queue to expedited.

Set the CIR of queue 3 to a non-zero value corresponding to the customer's expected bandwidth requirements.

Set queue 3 to use priority mode.

Set the traffic classification of packets to in-profile.

Set the high-priority-only value to 0.

Map AF traffic to queue 1

The system address of PE2 is present. The system addresses of CSC-PE1 and CSC-PE2 are not present.

The system addresses of PE2, CSC-PE1 and CSC-PE2 are all present.

The system address of CSC-CE1, the route 192.168.10.1, and the route 192.168.20.1 are all present.

The system address of PE2 and the route 192.168.20.1 are present.

Static

RIP

OSPF

IS-IS

MP-BGP

BGP

The default forwarding class for all traffic, including ICMP, is BE, which is placed in queue 1.

The SAP has been shut down.

The IP-match criteria has been misconfigured for ICMP traffic.

Queue 3 has no rate or CIR configured and thus cannot hold any packets.

The SAP-ingress policy has not been applied to the SAP.

A standalone policer has no parent arbiter, while a CFHP pohlicer has a parent arbiter.

A standalone policer has a fixed PIR rate, while a CFHP poker's PIR rate can be dynamically adjusted by its parent arbiter.

Both standalone and CFHP policers use the FIR bucket to gain access to their fair share of the available bandwidth.

Both standalone and CFHP policers use a policer output queue to store packets before they are forwarded.

Signal degradation, attenuation, line loss

Latency, FIFO, WRED

Delay, jitter, packet loss

SNR, queue depth, latency

Attenuation, dispersion, latency

The customer carrier network can be a pure IP network.

The customer carrier provides Layer 2 and Layer 3 services to its end-customers.

A single CSC VPRN is configured on the network provider to support all services offered by the customer carrier.

In the case where the customer carrier offers VPRN services, the model is referred to as hierarchical VPRN.

A single route for 192.168.0.0/16 is advertised.

BGP routes 192.168.1.0/27, 192.168.2.0/27, and 192.168.0.0/16 are advertised.

BGP routes 192.168.1.0/27 and 192.168.2.0/27 are advertised, and 192.168.0.0/16 appears as a "Blackhole" route in the route table only.

The given export policy is invalid.

Each PE must implement a policy to apply a unique SoO attribute to the set of routes received from each customer site.

A different BGP extended community is used on each PE that connects to a single site.

An import policy on the PE rejects a route if the attached SoO matches the configured value.

Import and export policies are applied on the PEs under the global BGP context.

Operates in transparent mode.

Carries RSTP BPDUs only.

Assigns RSTP state to other VPLS services.

Allows load balancing among multiple management VPLS instances.

64496 64512

64512

64496

64512 64496

It specifies the maximum rate at which a queue can be serviced.

It specifies the maximum depth of a queue beyond which packets will be dropped.

It specifies the portion of a queue that is taken from the reserved buffer pool.

It specifies the threshold beyond which only in-profile packets will be queued.

It specifies the peak bandwidth that can be attained by the incoming traffic.

1

5

15

30

45

1

2

3

None

The scheduler will be allocated its "within CIR" bandwidth before all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at the same level have received their "within CIR" bandwidth.

The scheduler will be allocated its "within CIR" bandwidth after all other children at all levels have received their "within CIR" bandwidth.

The scheduler will not be allocated its "within CIR" bandwidth.

VPLS switch identifier.

VPLS service identifier.

VPLS router identifier to all PEs.

A locally unique VPLS service identifier.

PIR = 4Mbps. CIR = 1Mbps

PIR = 1Mbps, CIR = 1 Mbps

PIR = 10Mbps, CIR = 1Mbps

PIR = 5Mbps, CIR = 1.25Mbps

PIR = 1.25Mbps, CIR = 1.25Mbps

TRUE

FALSE

Shapeless policing at SAP-ingress only.

Shapeless policing at SAP-ingress and egress.

Biased round robin queuing at ingress only.

Soft shaping at all network interfaces.

Soft shaping at network ingress only.

802.1p adds 16 bits to the Layer 2 header,

802.1p adds 16 bits to the Layer 3 header.

802.1p specifies 64 different priority levels.

802.1p uses a field in the 802.1Q header.

802.1p uses a field in the Layer 3 IP header

802.1p defines a 3-bit Class of Service field.

1 multipoint and 8 unicast.

8 queues, regardless of traffic type.

8 unicast and 24 multipoint.

8 unicast and 8 multipoint.

16 queues, distributed as desired.

PE2 pushes one label on the IP packet and label-switches it to ASBR2.

ASBR2 forwards an unlabeled IP packet to ASBR1.

ASBR1 pushes one label on the IP packet and label-switches it to PEL

PE1 pops one label and forwards the IP packet to CE1.

PE1 advertises spoke routes to CE1.

The primary VRF on PE1 is used to route data packets from the hub CE to the spoke sites.

The secondary VRF on PE1 contains routes learned from the spoke sites.

Spoke sites do not learn routes from other spoke sites directly.

The As-Path is not present as it was removed with the s-override configuration command

The As-Path is not present as it was removed with the o-as-path configuration command

The As-Path is not present as a policy was configured to set it to the null value

The As-Path is not present as VPN-IPv4 routes do not propagate the IPv4 As-Path BGP attribute

PE1 pushes an LDP transport label.

CSC-CE1 pops the LDP label and pushes a BGP label.

CSC-PE1 pops the BGP label and pushes two labels: a VPN label and an MPLS transport label.

CSC-PE2 pops the MPLS label and pushes a BGP label.

The Alcatel-Lucent 7750 SR supports 1:1 mapping of I-VPLS services to B-VPLS services.

The Alcatel-Lucent 7750 SR supports 1:1 andM:1 mapping of l-VPLS services to B- VPLS services.

The Alcatel-Lucent 7750 SR supports the mapping of multiple, standard VPLS services to B-VPLS services.

The Alcatel-Lucent 7750 SR supports the mapping of multiple, standard VPLS services to l-VPLS services.

Defining the slope of the TCP slow-start mechanism for self generated traffic.

Defining the slope of the scheduling rate per forwarding class when using HQoS.

Defining the high and low slope values when deploying buffer admission control for UDP traffic in the committed buffer pool.

Defining the high and low slope values when deploying buffer admission control for TCP traffic in the shared buffer pool.

Defining the high and low slope values when deploying buffer admission control for TCP traffic in the committed buffer pool.

QoS is not configured on the router.

Packets in forwarding classes "be" and "12" are being queued.

Traffic belonging to forwarding class "ef" is not experiencing queuing delays.

Traffic belonging to forwarding class "11 "will never make use of the shared buffer pool.

Out-of-profile traffic in the shared buffer pool is being dropped.

TRUE

FALSE

network

scheduling

slope

SAP-ingress

network-queue

A device that provides no differentiation between customer traffic flows.

A device that classifies and marks customer traffic.

A device that uses MPLS EXP bits to differentiate between traffic flows.

A device that creates macroflows towards the core from multiple customer sites.

A device that passes macroflows while optionally changing QoS markings.

The default forwarding class defined in the SAP-egress policy.

The forwarding class inherited from network ingress classification.

Best Effort.

If there is no match, packets will be dropped.

It is best used when a single VPN is required to provide Internet access, as well as to maintain VPN connectivity between different customer sites.

If there is no requirement for the VRF to contain the full Internet routing table, a default route to the Internet gateway router is sufficient.

Only one interface on the CE is required for both VPN and Internet connectivity.

The Nokia 7750 SR supports route leaking in full mesh and extranet VPRN topologies only.

DSCP

PREC

Dot1p

ToS

Q-in-Q

packet filtering

prioritization of traffic flows

least cost routing

OAM functionality

separation between the data plane and the control plane

3

64

72

16

56

MPLS tunnels are used to carry transit traffic across the network.

A full mesh of iBGP peering sessions is not required,

Edge and transit routers need to be configured with BGP.

The transit routers need to support LDP or RSVP-TE LSPs.

Marking/Remarking

Classification

Encapsulation

Scheduling

Using dot1p bits of the 802.1q Ethernet frame header

Using DSCP bits within the ToS field of the IP packet header.

Using the IP precedence bits within the ToS field of the IP packet header.

Using the CLP bit of the ATM cell header.

Using the EXP bits of the MPLS transport label header.

It is a parent scheduler.

It is the top-level scheduler.

It can allocate up to 50 Mbps of bandwidth to scheduler "low" since the bandwidth is not used by another Tier 3 scheduler.

It is a child scheduler.

It can only have queues as children.

MAC learning

SA filtering

Routing table population

Frame forwarding

Change the CIR-level value for the best-effort queue to 8.

Do not change anything; it is already guaranteed to receive its CIR

Change the CIR-level value for the best-effort queue to 1.

Change the CIR-weight value of the AF queue to 0.

The EXP bits in the MPLS header.

The packet's source and destination IP addresses.

The packet's DSCP bits.

The dot1p bits in the frame header.

The ID of an SDP that is transporting the packet.

Real-time

Assured

Non-conforming

High priority

In-profile

af11

af12

af31

af33

PIR

CIR

MBS

burst-limit

512 MB ingress, 512 MB egress

256 MB ingress, 256 MB egress

1 GB dynamically allocated between ingress and egress.

768 MB dynamically allocated between ingress and egress.

768 MB, with a minimum of 256 MB ingress and egress, and an additional 256 MB dynamically allocated.

When using profile-mode queues, traffic that is marked as in-profile on ingress and scheduled in the above-CIR loop will still be considered as in-profile at egress.

When an HQoS strategy using an egress port-scheduler has been deployed, Tier 1 receives its scheduling rates based on the amount of egress bandwidth available for each forwarding class.

The greater the difference between PIR and CIR rates in a queue, the less likely a CIR will be provided.

Packets scheduled out of high-priority queues in the default scheduler will have a lower chance of packet loss at the expense of incurring a higher probability of delay.

When using priority-mode queues, traffic that is marked as in-profile on ingress and scheduled in the above-CIR loop will be considered as in-profile at egress.

H-QoS capabilities must be enabled globally on the router

A scheduler-policy must be configured.

The queues in the SAP-ingress and SAP-egress policies do not require additional configuration attributes to make use of the hierarchical schedulers.

The network queue policy must be configured to make use of the scheduler-policy.

The scheduler-policy must be referenced in the SAP-ingress and SAP-egress policies.

The scheduler-policy must be applied on the service SAP.

On the PE facing the CE neighbor

On the CE facing the PE neighbor

On the P facing the PE neighbor

On the PE facing the PE neighbor

Import policies affect ingress data flow.

Export policies affect ingress data flow.

Both import and export policies affect ingress data flow.

Policy direction and data flow are independent.

Router C sends the update to routers E and F only.

Router C sends the update to routers D, E and F.

Router C sends the update to routers A, B, E and F.

Router C sends the update to routers A, B, D, E and F.

The update is sent to router R2 in ISP 1.

The update is sent to routers R2 and R3 in ISP 1.

The update is sent to all routers in ISP 1.

The update is sent to routers R2 and R3 in ISP 1, and to router R3 in ISP 2.

The router ID of router A.

The router ID of router B.

The router ID of router C.

It will not be set.

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

The port that the SAP belongs to must have the correct ether type configured.

The SAP must be configured with the right VLAN tag.

The SDP VC type must be configured as type VLAN and the correct vlan-vc-tag must be specified.

All of the above.

A frame should be sent to the PE that connects to the target site whenever possible.

A frame should be flooded as little as possible.

Customer frames should be switched based on the destination MAC address.

All of the above.

Only (a) and (b) are true.

There will be no impact on the path-mtu.

The path-mtu will decrease by4 bytes.

The path-mtu will increase by 4 bytes.

The path-mtu will decrease by 8 bytes.

The path-mtu will increase by 8 bytes.

The 1-SID must be explicitly configured.

The 1-SID only supports a range from 1 to 255.

The 1-SID will default to 511 .the value of the service-id.

Thel"SIDwilldefaultto131582, the value of the service-id + 131071.

Option A

Option B

Option B

Option C

Option E

Relearning of the MAC address that was purged can only be done once customer traffic resumes.

Relearning of the MAC address that was purged can only be done with the "oam mac-populate" command.

Customer traffic destined to the MAC address that was purged will be dropped until the MAC address is relearned with the "oam mac-populate" command.

Relearning of the MAC address that was purged can only be done with the "oam mac-register" command.

100

1

25

250

The device will try to force the other side up using the evaluating flag in the PDU.

The device will wait for the trasmit-interval of 5 before trying to rediscover the neighbor.

The device will detect the port change and will wait for normal operation mode.

The device will detect the port change and revert to discovery mode.

The PE sends an LDP control message that flushes all FDB entries in the VPLS instance.

The PE sends an LDP control message that flushes all FDB entries in the VPLS instance that are associated with the PE that detected the failure.

The PE flushes it's local FDB only.

The PE sends an oam service message that flushes all FDB entries in the VPLS instance.

MEP

MAP

MIP

MUP

MAC learning

Frame replication

Frame fragmentation

Frame forwarding

Must discard frames with an unknown destination MAC

MSTP

Filter Policies can only be applied on egress.

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

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.

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

The service MTU must be 1514 bytes.

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

The service MTU can be any value.

The route learned from an eBGP peer.

The route with the lowest Origin.

The route with the lowest originator ID or BGP Identifier.

The route with the shortest AS path.

T-LDP and LDP sessions with the other VPRN PE routers and the VPLS PE router

T-LDP sessions with the other VPRN PE routers and the VPLS PE router

LDP sessions with the other VPRN PE routers and the VPLS PE router

LDP sessions with the other VPRN PE routers, and both T-LDP and LDP sessions with the VPLS PE router

T-LDP and LDP sessions with the other VPRN PE routers and LDP sessions with the VPLS PE router

Any CE device

Any PE device

Any P device

Any router in the service provider core

Any customer router

It will label switch the packet based on this label

It will decrement the TTL and label switch the packet based on this label

It will SWAP the label for a new label and then label switch the packet

The P router does not perform any operation on this label

The protocol is configured under the config>service context

The protocol is configured under the global router context

The interface leading to the PE is defined as a protocol neighbor

The routing protocol used must be the same as the routing protocol used at other CE-PE locations in the same VPN.

A routing policy may or may not be required depending on the routing requirements and routing protocol

PE1

RR1

ASBR1

ASBR2

The PE will install a maximum of 40 prefixes into the customer vrf and generate a log message when 40 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, and generate a log message both when 30 and 41 routes are received

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and disable learning of new routes at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 10 routes are received and drop the connection at 41

The PE will install a maximum of 40 prefixes into the customer vrf, generate a log message when 4 routes are received and disable learning of new routes at 41

Show router bgp routes

Show router route-table summary

Show router bgp routes vpn-ipv4 detail

Show router route-table

"show router 10 route-table"

"show router route-table"

"show router 20 route-table"

There is no CLI command that can produce this output on router R4

A single routing protocol for exchanging routes with both the internal customer routers and with the PE

MP-BGP to exchange routes with the PE.

MPLS and a routing protocol for the exchange of labels and routes with the PE

MPLS for exchanging labels with other CE devices

A routing protocol for exchanging routes with the internal customer routers and a routing protocol for exchanging routes with the PE

When sites of different VPRN customers use the same BGP AS number

When sites of the same VPRN customer use the same BGP AS number

When sites of different VPRN customers use different BGP AS numbers

When sites of the same VPRN customer use different BGP AS numbers

When the customer site AS number is the same as the provider AS number

This is the base routing table from CE-1

This is the base routing table from PE-1

This is the customer vrf from CE-1

This is the customer vrf from PE-1D.This is the customer vrf from PE-1

This is the customer vrf from PE-2E.This is the customer vrf from PE-2E.This is the customer vrf from PE-2

This is the base routing table from PE-2F.This is the base routing table from PE-2F.This is the base routing table from PE-2

This is the base routing table from CE-2G.This is the base routing table from CE-2G.This is the base routing table from CE-2

The route with the lowest MED.

The route with the shortest AS Path.

The route received from the lowest peer IP address.

The route with the lowest Origin.

On the CE under the RIP context

On the PE under the BGP context

On the PE under the RIP context

On the CE under the BGP context

This policy is not required

Show router bgp routes

Show router bgp routes address-family vpn-ipv4

Show router bgp routes

Show router bgp routes

The AS-Path is not present because a policy is configured on PE2 to set it to null.

The AS-Path is not present because a policy is configured on CE1 to set it to null.

The AS-Path is not present because a policy is configured on PE1 to set it to null.

The AS-Path is not present because VPN-IPv4 routes do not propagate the IPv4 AS-Path BGP attribute.

Router R1

Router R2

Routers R1 and R2

Router R3

Router R4

Allow routes to be exchanged between all or selected sites of one VPRN and all or selected sites of a second VPRN

Allow the service provider to provide multiple VPRNs with Internet access

Reduce the number of VPRN tunnels required

Simplify the administration of multiple VPRNs

Force all traffic in multiple VPRNs to pass through a single device

MP-iBGP sessions must be configured between the PE routers in each AS.

LDP must be configured in each AS.

MP-eBGP sessions must be configured between the ASBRs.

The ASBRs must be configured with "enable-inter-as-vpn".

Each customer site has a logically direct route to every other customer site.

It provides optimal routing between all sites.

It allows access between all CE devices and all sites participating in the same VRF.

It requires a full BGP mesh in the provider core.

When the route is first received at the P from the PE

When the route from the CE is populated into the VRF at the PE

When the route from the PE is populated into the VRF at the CE

When the route is propagated from the PE to the CE

When the route is exported into the MP-BGP table from the VRF

Distributing the customer generated labels between sites

Distributing the customer routing information between

Forwarding the customer originated data packets to the appropriate destination

Forwarding the provider originated data packets to the appropriate customer site

Providing secure layer 3 routing exchange between sites

Identify the egress PE in the MPLS domain

Signal the egress VPRN ID

Identify the ingress PE in the MPLS domain

Transport route updates between PEs

OSPF

ISIS

MP-BGP

BGP

Targeted LDP

Show service 3

Show service id 3

Show service 3 base

Show service id 3 base

Show service 3 detail

Show service id 3 detail

ASBR1 includes label 131069 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to ASBR2.

ASBR1 includes label 131068 in the route update sent to PEL

ASBR1 includes labels 131068 and 131069 in the route update sent to ASBR2.

A data packet destined to a remote AS is encapsulated with three labels within the originating AS.

The ASBR redistributes VPN-IPv4 updates to its ASBR eBGP peers.

PE routers in different ASes exchange IPv4 routes directly between each other using eBGP.

The advertising ASBR assigns a new label to the route before sending it via an MP-eBGP update to its ASBR peer.

64496 64497

64496

64497

64497 64497

This command is required on all PE routers to distribute labeled IPv4 routes directly to PEs in remote AS.

This command is required on the ASBRs to exchange labeled IPv4 routes between the ASs.

This command is required on the route reflectors to exchange customer routes between ASs as labeled IPv4 routes.

This command is required on all PE routers to distribute labeled IPv4 routes to connected CEs.

CE2 forwards an unlabeled IP packet to PE2 via the VPRN interface.

PE2 pushes two labels on the IP packet and label-switches the packet to ASBR2.

ASBR2 pops one label from the IP packet and label-switches it to ASBR1.

ASBR1 pushes two labels on the IP packet and label-switches the packet to PEL.

Memory exhaustion in the provider core

Route leaking between the customer networks

CPU utilization for route processing

Unwanted packet forwarding between customer networks

VPLS 1 will be displayed as mVPLS and VPLS 100 will be displayed as VPLS.

VPLS 1 will be displayed as mVPLS and VPLS 100 will be displayed as uVPLS

VPLS 1 will be displayed as VPLS and VPLS 100 will be displayed as VPLS.

VPLS 1 will displayed VPLS and VPLS 100 will be displayed as uVPLS.

An LSP must be configured between PE-A and PE-D for this traffic to be forwarded.

A VPLS FDB lookup is done at PE-A of Metro A only

An SDP must be configured between PE-A of Metro A and PE-D of Metro D for this traffic to be forwarded

A VPLS FDB lookup is done at PE-A and PE-C of Metro A and PE-B of Metro B

1500

1514

1518

It depends on the access port MTU.

It depends on the network port MTU.

MAC learning

SA filtering

Routing table population

Frame forwarding

Spanning-tree BPDUs are returned to the sender.

The MEP sees its own CFM frames returned to itself.

This is not a function of IEEE 802.lag but of 802.1D

The record field of the CFM frame keeps track of chassis-mac addresses.

An error will be generated and the configuration will not be allowed.

The filter entry will be ignored and traffic matching the criteria will be forwarded

All traffic matching entry 20 will be dropped.

Traffic matching entry 20 will be forwarded to sdp 100:1.

Event notification.

Loopback control.

Information.

Variable request.

Variable response.

9100

9104

9108

9122

9126

Yes

No

The PE devices participating in the VPLS mesh run a separate Spanning Tree instance in the Core. The Primary Bridge is the Root Bridge for the VPLS mesh.

The PE devices participating in the VPLS mesh determine which bridge is closest to Root Bridge. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge has the lowest bridge-id. This bridge becomes the Primary Bridge.

The PE devices participating in the VPLS mesh determine which bridge is the Root Bridge. This becomes the Primary Bridge.

This is not a best practice. Any switch can be used as the root bridge.

So that you know which links will be active in your network.

To prevent a new switch from becoming root when added to the network.

To allow all ports on the root switch to become alternate ports.

Designated

Discarding

Listening

Root

Forwarding

TRUE

FALSE

Set the bridge priority to 131071.

Set the bridge priority to 0.

Set the bridge priority to 32768.

Leave the bridge priority as the default.

The MEP sees the CFM frame from a different MEG.

The MEP sees a different service-id in the frame sent by a MEP.

The MIP transmits the service-id for each service. The MIP should only see it's own service-id.

This is a function of 802,3ah EFM,

I-VPLS is configured in the core of the network with an l-MAC address. This l-MAC address is the only MAC learned in the core

The B-VPLS and l-VPLS are configured in the edge. The B-VPLS is configured with a Backbone MAC and is the only MAC learned in the core

Each SDP is configured with a Backbone MAC to hide customer MAC addresses in the core

Each SAP is associated with a common l-MAC to hide customer MAC addresses in the core

sap 1/1/1

sap 1/1/1:0*

sap 1/1/1:0

sap 1/1/1:*

The switch with the lowest priority becomes the root.

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.

Option A

Option B

Option C

Option D

The frame is dropped.

The frame is always flooded

The frame is forwarded and MAC learning is automatically disabled.

The frame is discarded if the destination is unknown.

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

sap 1/1/1:200.100

sap 1/1/1:200*

sap 1/1/1:*

sap 1/1/1:0*

MSTP

MCLAG

LACP

DHCP

A proprietary protocol

The frame will be forwarded out the port associated with the DA.

The frame will be discarded.

The frame will be flooded to all ports.

The frame will be fragmented and forwarded out the port associated with the DA.

H-VPLS

M-VPLS

PBB

MC-EP

A Spanning Tree BPDU will be sent across the mesh flushing the FDB table in all devices participating in the VPLS instance.

Stale information will be used within the VPLS instance to forward traffic until the FDB ages out.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. Only MAC addresses associated with the PE that the failure occurred on will be flushed.

An LDP control message will be sent to all devices in the mesh participating in the VPLS instance. The entire FDB in the VPLS instance will be flushed.

0

1

2

3

Bridge B

Bridge C

Bridge D

Bridge E

VPLS1500 is a user VPLS.

VPLS 1500 is management VPLS.

Spanning tree BPDUs for the management VPLS are tagged.

Spanning tree BPDUs for the management VPLS are untagged.

TRUE

FALSE

It flushes the local FDB speeding recovery

It discards all packets in the queue and sends icmp-discad messages to the sender. The packets are re-transmitted resulting in no loss of data.

On failure, the PE sends an LDP flush-all-from-me message to all PE devices in the VPLS. This speeds convergence to the new topology.

It is not important to use send-flush-on-failure as Active/Standby signalling automatically converges the FDB in all VPLS instances

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

The l-TAG in the l-SID is inspected to determine where the frame should be delivered.

When the B-MAC header is stripped the customer MAC address is then looked up in the FDB

The l-SID in the l-TAG is inspected to determine where the frame should be delivered.

The PE inspects the service label in the MPLS header before stripping the B-MAC header.

The entire confederation is viewed as a single AS by an eBGP peer.

Within a confederation, each member AS is considered as a stand-alone AS.

Member ASs within a confederation can use route reflection.

Member ASs must be fully meshed within a confederation.

All routers with which it has a BGP session.

All routers with which it has a BGP session, except the router it received the update from, which is router B.

All routers with which it has a BGP session, except the router it received the update from, which is router C.

All routers with which it has a BGP session, except the router it received the update from, which is router D.

Only eBGP neighbors.

Routers R1, R2, R3, R4 and R5.

Routers R1and R4 only.

Routers R1, R2, R3 and R4 only.

Routers R1, R4 and R5 only.

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

An update message is used. Only a single prefix can be withdrawn at a time.

An update message is used. Multiple prefixes can be withdrawn at a time.

A withdraw message is used. Only a single prefix can be withdrawn at a time.

A withdraw message is used. Multiple prefixes can be withdrawn at a time.

Policy changes are delayed until the peer router with the affected routes reboots.

Policy changes are delayed until route updates for affected BGP routes are received from peers.

Policy changes are delayed until BGP sessions are cleared or BGP is reset.

Policy changes are delayed until the router reboots.

100

The IGP cost

500

None

All BGP routes are accepted.

All routes matching prefix lists "List-1" and "List-2" are rejected.

BGP routes matching prefix lists "List-1" or "List-2" are rejected.

BGP routes matching prefix lists "List-1" and "List-2" are rejected.

Option A

Option B

Option C

Option D

Option A

Option B

Option C

Option D

Execute a command to re-evaluate all routes in the Local-RIB against the configured export policies.

Execute a command to re-evaluate all routes in the RIB-In against the configured import policies.

Execute a command to reset the BGP session with the affected peer or peers.

No further action is required.

Next Hop is modified when crossing member AS boundaries within a confederation.

Origin Code is modified when crossing member AS boundaries within a confederation.

AS Path is modified when crossing member AS boundaries within a confederation.

None of the well known mandatory attributes is modified within a confederation.

Authentication is performed before establishing the BGP session.

Authentication can only be configuredon the group or neighbor level.

By default, MD5 authentication is disabled.

Peer authentication may be optionally requested in an open message.

AS Path of 65200, local-preference of 100.

AS Path of 65200, local-preference of None.

Null AS Path, local-preference of 100.

Null AS Path, local-preference of None.

100

The IGP cost

500

None

Core and edge node failure recovery depends on IGP convergence.

Edge neighbor failure is detected by the eBGP session timeout.

BGP control plane convergence is independent of number of affected prefixes.

Upon BGP control plane convergence, an optimal path is installed in the FIB.

Two routes from router R4.

Two routes from router R5.

Two routes; one from router R4 and one from router R5.

Four routes; two from router R4 and two from router R5.

A single-homed AS is also known as a stub AS.

A single-homed AS is also known as a leaf AS.

A single-homed AS uses either the ISP AS number or a private AS number.

A single-homed AS can be either transit or non-transit

Option A

Option B

Option C

Option D

None

2

3

4

BGP version number.

The local AS number.

The Hold Time.

Authentication.

65206 65202 65100

(65206 65202)65100

(65204 65206 65202) 65100

(65200) 65100

The aggregator attribute will not be present, and the atomic aggregate flag will not be set.

The aggregator attribute will not be present, and the atomic aggregate flag will be set.

The aggregator attribute will be present, and the atomic aggregate flag will not be set.

The aggregator attribute will be present, and the atomic aggregate flag will be set.

70 seconds

25 seconds

20 seconds

30 seconds

The routes are in the RIB-In.

The routes are in the Loc-RIB.

The routes are in the RIB-Out.

The routes are not in any of the BGP databases.

The routes from routers R1, R2 and R5.

The routes from routers R1and R2.

The routes from routers R2 and R5.

Two routes are chosen at random and advertised to router R4.

7

13

21

42

12

13

14

15

The route is ignored.

The route is flagged as invalid and placed in the LOC-RIB.

The route is flagged as invalid and placed in the RIB-In.

The route is flagged as invalid and placed in the RIB-Out.

"client2" routes will be tagged with communities "West" and "North".

"client2" routes will be tagged with communities "West", "North" and "South".

"client2" routes will be tagged with community "West".

"client2" routes will be tagged with community "South".

TTL is a well-known mandatory BGP attribute.

The default TTL value of an eBGP message is 1, and 64 for an iBGP message.

The default TTL value of an iBGP message can be modified using the multihop command.

The default TTL value of an eBGP message can be modified using the "ttl-security" command.

eBGP peers typically use system addresses for session establishment.

eBGP peers are managed under a single administration.

eBGP peers do not propagate updates learned via iBGP.

eBGP peers are usually directly connected to each other.

The router will accept the update and send a notification.

The router will not accept the update and send a notification.

The router will accept the update and ignore the attribute.

The router will accept the update and propagate the attribute.