Free 4A0-107 Exam Dumps Preview

010011

100010

010001

001100

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 egress port schedulers can be children of a single HQoS scheduler.

10000 Kbps

15000 Kbps

20000 Kbps

8th

9th

17th

ToS

DSCP

PREC

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

It will be stored in the reserved buffer space and become in-profile.

It will contend for shared buffer space with packets from other queues.

It will be discarded because the high-priority-only threshold has been reached.

During the allocation of within-CIR bandwidth.

During the allocation of both within-CIR and above-CIR bandwidth.

The port scheduler does not use the level of a child for making bandwidth allocation decisions

Queue 3 within-CIR packets, then queue 4 within-CIR packets, then queue 3 and queue 4 above-CIR packets in round-robin.

Queue 3 within-CIR packets, then queue 4 within-CIR packets, then queue 3 above-CIR packets, and
finally queue 4 above-CIR packets.

Queue 4 within-CIR packets, then queue 3 within-CIR packets, then queue 4 above-CIR packets, and
finally queue 3 above-CIR packets.

Signal degradation, attenuation, line loss

Latency, FIFO, WRED

SNR, queue depth, latency

Attenuation, dispersion, latency

A slope policy for the port on ingress.

A network queue policy for the corresponding MDA on ingress.

A network queue policy for the port on egress.

To have control over the amount of the low priority packets that enter the queue.

To control any traffic flowing through the shared buffer space of the queue.

To limit the number of the TCP sessions that go into slow start during congestion.

An egress unicast queue defined in a network queue policy

An ingress multipoint queue defined in a SAP-ingress policy

An ingress multipoint queue defined in a network queue policy

It will be queued in the reserved portion of the buffer pool if there are no in-profile packets already in the queue.

It will be queued in the reserved portion of the buffer pool and be in-profile.

It will be queued in the shared portion of the buffer pool but contend for shared buffer space with packets from other queues.

It will be queued in the shared portion of the buffer pool but may be dropped if the buffer utilization exceeds the start-average value of the low slope.

af21

af23

af31

The egress port scheduler takes the ratio of requested bandwidth to total bandwidth request from all children. It allocates bandwidth fairly, using these percentages and not exceeding the egress interface speed.

The egress port scheduler allocates bandwidth on a first come, first served distribution method that takes into account the total CIR and PIR requested at each level and the max PIR requested from a single level.

The egress port scheduler will limit the bandwidth offered to the egress port based on the over-subscription factor, provisioned under the router interface, while using a WRR scheduler for the remaining bandwidth.

The egress port scheduler will use the Russian Dolls Method to allocate bandwidth to each level of requested bandwidth. HPO-Only is automatically set to 100%, allowing only high priority traffic to be buffered during congestion.

All self-generated traffic is assigned into forwarding class NC by default.

Ingress self-generated traffic is stored in CPM queues and egress self-generated traffic is stored in
IOM queues.

The self-generated packets will be marked with default EXP bits.

Packets that arrive in a burst are immediately dropped; packets that arrive with the proper in between
space are immediately.

Packets are buffered on arrival and are forwarded at an average rate conforming with PIR, typically, with a reduced burstiness.

Packets with an average arrival rate higher than PIR are immediately dropped; conforming packets are
forwarded at the same rate at which they arrive.

Dot1p

DEI

EXP

Interfaces, ports, SAPs

Ports, ports, MDAs

Interfaces, interfaces. MDAs

MDAs, ports, interfaces

In order to mark Layer 2 traffic, sgt-qos will set various ToS bits.

The DSCP marking stays nc1 for all applications. Only the internal FC is manipulated across different applications.

The internal forwarding class for self-generated traffic is set once and applied to the base router and all VPRN instances.

FALSE

0

3

22

2

3

4

5

8

It is important that all packets are classified in the same way at all SAP-ingress points.

Once a packet is classified to a forwarding class, it cannot change across the network.

Native IP packets entering a network port will be marked at the first network egress by default

Native IP packets entering a network port will be marked at the first network egress, regardless of the re-marking configuration.

The packet's source and destination IP addresses.

The ID of an SDP that is transporting the packet.

When applied at the FP (Forwarding Path) level for access egress

When applied at an access port for ingress or egress

When applied at the port level for network egress

Every forwarding class can be associated with its own queue without sharing with other forwarding classes.

A 3-tier scheduling policy can be applied at SAP-ingress/SAP-egress.

Policing can be deployed instead of queuing at ingress.

Profile-mode and priority-mode queues can only be configured on SAP ingress.

For network egress, egress re-classification can change the profile marked at ingress.

For network ingress, the network policy can classify the packet as either in-profile, or out-of-profile.

It enables CFHP.

It more scalable than using policers.

It allows a separate set of queues/policers for each VLAN on a port.

Set the CBS to 0.

Set the high-priority-only equal to the MBS.

Set the MBS to 0.

Set the high-priority-only to 0.

Access ingress ports

Access egress ports

Network ingress ports