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 point in the network where EXP bits can be mapped to one of eight predefined FCs, each one with its own queue.

A logical point in a service tunnel where all of customer traffic is aggregated.

A point at which the initial classification of customer traffic occurs.

A point in the network where QoS parameters are discarded in favor of lower-level hardware queuing functions, such as LLI (Link Layer Interleave).

A point in the network where traffic flows from multiple different services are queued together, based on forwarding class.

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.

Signal degradation, attenuation, line loss

Latency, FIFO, WRED

Delay, jitter, packet loss

SNR, queue depth, latency

Attenuation, dispersion, latency

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.

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.

3

64

72

16

56

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.

MAC learning

SA filtering

Routing table population

Frame forwarding

Router interfaces

Ingress MDA

Ingress Ethernet network ports

Egress Ethernet network ports

Service SAPs

Classification

Marking

Queuing

Congestion management

Scheduling

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.

packet filtering

prioritization of traffic flows

least cost routing

OAM functionality

separation between the data plane and the control plane

TRUE

FALSE

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.