Packets can be classified into 16 different FCs when using priority mode queuing.

This feature is available on egress SAPs within any service.

MPLS EXP bits can be changed based on multi-field classification.

If a Behavior Aggregate (BA) and Multi-field (MF) match occurs, only the MF override parameters will take effect.

If a Behavior Aggregate (BA) and Multi-field (MF) match occurs, the BA classification can override the forwarding class while the MF classification can override the profile.

The NRLI

The AFI

The SAFI

The extended community

The egress port scheduler can have up to 17 children spread across 8 levels.

Multiple egress port schedulers can be assigned to a single port with many HQoS children.

Multiple HQoS policies can be children of a single port scheduler.

Multiple egress port schedulers can be children of a single HQoS scheduler.

H2

NC

L2

EF

H1

BE

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

The IOM3 adds more memory to both forwarding complexes which increases the total number of queues available.

The IOM3 only contains a single forwarding complex which reduces the number of queues used.

The IOM3 allows multiple forwarding classes to be assigned to a single queue.

The IOM3 allows queues to be dynamically allocated between ingress and egress.

The IOM3 has a larger CPU capable of tracking active hardware queue utilization and adjusting memory allocation accordingly.

MAC learning

SA filtering

Routing table population

Frame forwarding

8

16

6

4

3

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.

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.

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.

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

WRED

shapers

schedulers

markers

weighted fair queues (WFQ)

The three most significant (first) bits define 8 forwarding classes.

The three least significant (last) bits of the DSCP specify the drop probability.

The full 8 bits of the TOS field are used for DSCP.

To convert DSCP to IP precedence, the three most significant (first) bits are matched.

DSCP provides for eight drop probabilities.

TRUE

FALSE

64

8

3

16

1

SAPs

SDPs

Services

Queues

Schedulers

Forwarding classes

The DSCP value will be set to af21.

The DSCP value will be set to be.

TheDSCPvaluewillbesettoaf23.

The DSCP value will be set to af 12.

Thedot1pvaluewillbesetto5.

Thedot1pvaluewillbesetto2.

The dot1p value will be set to 3.

TRUE

FALSE

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.

Option A

Option B

Option C

Option D

It requires the configuration of back-to-back VRFs between ASBR routers in different autonomous systems

It is the most scalable of the Inter-AS models.

Most routers that support VPRN functionality support model A by default.

It uses conventional eBGP to distribute unlabeled IPv4 routes between ASBR routers in different autonomous systems.

The Alcatel-Lucent 7750 SR allows the setting of the maximum number of routes that can be accepted in a VRF for a VPRN service.

The "maximum-routes" command is used to specify the maximum number of remote routes that can be held within a VRF for a VPRN service.

When the "maximum-routes" command is used with the "log-only" parameter, new routes are still learned.

Once the "threshold" value is reached, no new routes are added to the VRF.

Show router bgp routes

Show router route-table summary

Show router bgp routes vpn-ipv4 detail

Show router route-table

One label per route

One label per next-hop

One label per VRF

One label per prefix

One label per tunnel

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

Configuring labeled eBGP sessions between CSC-CE and CSC-PE routers.

Configuring a policy on each CSC-CE to advertise local PE addresses to the network provider.

Configuring labeled iBGP sessions between PEs residing in different customer carrier sites.

Advertising the received system addresses of remote PEs using either iBGP or IGP/LDP within each customer carrier site.

BGP sessions established between RR2 and the PEs support IPv4 and VPN-IPv4 address families.

BGP sessions established between RR1 and the PEs support the IPv4 address family only.

BGP sessions established between RR1 and the PEs support IPv4 and VPN-IPv4 address families.

BGP sessions established between RR2 and the PEs support the IPv4 address family only.

The ASBRs use MP-eBGP to peer with each other and exchange IPv4 routes between autonomous systems.

The ASBRs use MP-iBGP to peer with PE routers in their autonomous system and exchange VPN-IPv4 routes.

The ASBRs maintain a mapping of labels for IPv4 routes exchanged between autonomous systems.

The ASBRs require per-VPRN configuration.

oam vprn-ping source destination

oam vprn-ping source destination

vprn-ping router

Ping source

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

CSC is also known as carrier's carrier or carrier serving carrier.

The customer carrier provides VPN or Internet services to its end-customers.

A CSC VPRN is configured on the customer carrier's CSC-CE routers.

These routes will not appear on CE-B

Type 1 LSAs

Type 3 LSAs

Type 5 LSAs

Type 7 LSAs

Reduced number of VPN tunnels that need to be managed.

Optimal routing between all sites.

Limited configuration required on the hub PE device.

Site to site redundancy support.

CE1

PE2

PE1

CE2

Any CE device

Any PE device

Any P device

Any router in the service provider core

Any customer router

It is the customer responsibility to ensure their address space is unique

The Route Distinguisher ensures that addresses are unique between customers.

The Route Target ensures that addresses are unique between customers

The provider will advise the customers to change their addresses

The provider will use NAT to ensure that addresses are unique between customers

CE1 forwards the data packet to PE1 via the VPRN 20 interface.

PE1 pushes two labels on the IP packet: a BGP label and an LDP transport label.

CSC-CE1 pops the LDP label and swaps the BGP label.

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

This configuration is correct and complete

This configuration is correct except that the system interface must be added

This configuration is correct except that the interfaces facing the CE routers must be added.

MPLS configuration is not required

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.

ecmp and multipath must be configured within the VPRN instance.

The RD of the VPRN on the local PE must be different from the RD of the remote PEs.

Is enabled in the config>router>bgp context

Allows a PE router to load share traffic across routes learned from both direct CE-PE peerings and MP-BGP peerings.

All traffic exchanged between end-customers is carried over a single CSC VRF.

Customer carrier PE routers residing in different sites must run eBGP between them to exchange customers' routes.

The customer carrier network can be a pure IP network.

MPLS can be used in the customer carrier network to improve scalability.

VPN-IPv4 routes for all PE system addresses in AS 1000

BGP labeled IPv4 routes for all PE system addresses in AS 1000

VPN-IPv4 routes for all PE system addresses in AS 5000

BGP labeled IPv4 routes for all PE system addresses in AS 5000

Three route targets and three route distinguishers

Five route targets and three route distinguishers

Three route targets and two route distinguishers

Five route targets and two route distinguishers

PE1

RR1

ASBR1

ASBR2

192.168.10.1

192.168.20.1

10.10.10.1

10.10.10.6

TRUE

FALSE

802.1D2004

802.1D 1998

comp-dot1w

PVST

Bandwidth and replication inefficiency can occur on inter-metro links if there is a lot of multicast traffic

The number of control sessions grows exponentially in a fully meshed network.

Spanning-tree is required to prevent loops when using mesh SDPs on the inter-metro links.

Network touches increase with each node added to the mesh.

If a spoke-SDP is configured between the new site and PE-D no further SDPs will be required.

If a mesh- SDP is configured between the new site and PE-D no further SDPs will be required.

A mesh- SDP must be configured between the new site and all other PEs within Metro B.

A spoke- SDP must be configured between the new site and all other PEs within Metro B.

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

Loss of connectivity.

Unidirectional Loss.

Loop detection.

Merged Services.

End-to-end bit error rates.

Spoke SDP

Mesh SDP

Either (a) or (b) will make this sentence true.

Neither (a) nor (b) will make this sentence true.

H-VPLS

M-VPLS

PBB

MC-EP

4094

8190

32768

131071

If the MAC address of this new client device does not reach the upper limit of the configured total number of MAC addresses allowed in the VPLS forwarding database, then the new MAC address will be stored.

The new source MAC addresses will not be entered in the VPLS service forwarding database.

New local source MAC addresses will not be entered in the VPLS service forwarding database, but new remote MAC addresses would continue to be entered.

New remote source MAC addresses will not be entered in the VPLS services forwarding database, but new local MAC addresses would continue to be entered.

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.

Only R4 will be reachable through the VPLS.

B All devices will be reachable through the VPLS.

R4 and R3 will remain reachable.

No devices will be reachable.

TRUE

FALSE

Yes

No

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.

100

1

25

250

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 source MAC address of a frame with a top tag of 100 will be populated in VPLS 2.

As frames leave the switch, the DA is populated into the FDB.

As frames enter the switch, the DA is populated into the FDB.

As frames leave the switch, the SA is populated into the FDB.

As frames enter the switch, the SA is populated into the FDB.

Configure the local age timer to be larger.

Configure the local age timer to be lower.

Configure the remote age timer to be larger.

Configure the remote age to be lower.

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.

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 CE must be configured with an MC-LAG to both PE devices.

The CE must be configured with LACP in active mode.

There is no configuration required on the CE.

The CE must be an Alcatel-Lucent 7750 SR.

Processing the TTL takes extra time.

MAC learning rate is doubled.

FDB size is doubled.

Requires a protocol to remove loops.

PE-A will require a SAP id of "sap 1/1/1:200" and PE-B will require a SAP id of "sap 1/1/1:300.

PE-A will require a SAP id of "sap 1/1/1" and PE-B will require a SAP id of "sap 1/1/1".

PE-A will require a SAP id of "sap 1/1/1:0" and PE-B will require a SAP id of "sap 1/1/1:0".

PE-A will require a SAP id of "sap 1/1/1:*" and PE-B will require a SAP id of "sap 1/1/1:*".

A confederation is a collection of Autonomous Systems advertised as a single AS number to BGP speakers outside the confederation.

Each member AS must either maintain a full mesh of iBGP sessions, or use route reflection.

Confederations can be used to subdivide ASs that have a large number of BGP speakers into smaller domains.

A full mesh of intra-confederation eBGP sessions is required between the member ASs.

"client2" routes will be only tagged with communities 'East'' and "South".

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

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

"client2" routes will be rejected.

ISP 1 and ISP 2 have a public transit relationship, while ISP 3 and ISP 4 have a private transit relationship.

ISP 1 and ISP 2 have a private transit relationship, while ISP 3 and ISP 4 have a public transit relationship.

ISP 1 and ISP 2 have a private peering relationship, while ISP 3 and ISP 4 have a public peering relationship.

ISP 1 and ISP 2 have a public peering relationship, while ISP 3 and ISP 4 have a private peering relationship.

Client-1 routes only.

Client-2 routes only.

Client-1 and Client-2 routes.

Neither Client-1 nor Client-2 routes.

140000 200 135000

137000 140000 200 135000

140000 23456 135000

135000 200 140000

Only the BGP route is in the route table.

Both routes are in the route table.

None of the routes is in the route table.

Only the OSPF route is in the route table.

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.

An import policy that rejects updates with an AS Path matching the regular expression ".+ 65540 .+".

An import policy that rejects updates with an AS Path matching the regular expression ".+ 65540".

An import policy that rejects updates with an AS Path matching the regular expression "65540 .+".

An import policy that rejects updates with an AS Path matching the regular expression "65540".

Add-Paths allows non-best paths to be advertised to a peer.

Add-Paths capabilities are exchanged between peers after the BGP session is established.

A BGP speaker must advertise the capability to receive multiple paths from its peer.

A BGP speaker must advertise the capability to send multiple paths to its peer.

There can only be one community associated with a route.

Community is an optional non-transitive attribute.

Community is an optional transitive attribute.

Community is a well-known discretionary attribute.

Only the first route will appear in the RIB-Out.

Only the second route will appear in the RIB-Out.

Only the third route will appear in the RIB-Out.

All routes will appear in the RIB-Out.

It is an optional transitive attribute.

It is an optional non-transitive attribute.

The atomic aggregate flag is always set if the aggregator attribute is set.

The atomic aggregate flag is always set if the AS Path information is lost due to aggregation.

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.

"65100"

"65100 65200''

"65200 65100"

"65100 65250 65200"

1

32

64

255

Optional transitive attribute.

Optional non-transitive attribute.

Well-known mandatory attribute.

Well-known discretionary attribute.

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.

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.

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

BGP version number.

The local AS number.

The Hold Time.

Authentication.

100

250

The IGP cost

None

The router ID of router A.

The router ID of router B.

The router ID of router C.

It will not be set.

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.