Pass the Nokia SRC Certification 4A0-107 Questions and answers with ExamsMirror

PIR

CIR

MBS

burst-limit

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.

To force the TCP algorithm to increase its transmission window upon detecting a congestion.

The available bandwidth of the port is divided in a strict priority over its children.

Expedited queues must be serviced before best-effort queues.

Orphaned queues are serviced on the 8th scheduling priority.

The configured CIR dictates the maximum port bandwidth that can be allocated during the within-CIR pass for that level.

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.

A port scheduler can only be implemented on a network egress port when queue-groups are configured for that port.

A port scheduler can be implemented on an access ingress port.

A port scheduler can be implemented without HQoS on an access egress port.

A port scheduler can be implemented on a network ingress port.

Limiting the maximum forwarding rate of each individual policer and, at the same time, marking, packets as in-profile or out-of-profile.

Putting packets in a buffer as they are received, and marking packets as in-profile or out-of-profile as they are removed from the buffer.

Rate-limiting the collective output of several policers, and to reallocate bandwidth that is not utilized by some policers to other policers that need to use it.

Rate-limiting the collective output of several policers towards each egress FFPC, while maintaining control of the maximum overall forwarding rate.

SAP-ingress only

SAP-egress only

SAP-ingress and SAP-egress

Network ingress

Network egress

The policy should be placed in a "shutdown" state before changes are made.

A new network policy should be created and applied to the interface, overwriting the previous policy.

The policy must first be removed from the interface, then modified and re-applied to the interface.

Before the policy can be changed, it must be deleted with the no network qos command.

Before any changes are made to the policy, all network interfaces where the policy is applied have to be shut down.

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.

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 a default DSCP value.

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