Free Practice Questions for Nokia 4A0-107 Exam

WRED monitors the shared buffer space utilization over a period of time.

WRED disables the TCP slow-start congestion control mechanism.

WRED uses two configurable slopes for each buffer pool: a high slope and a low slope.

WRED uses the shared buffer utilization, instead of the individual queue depth, to get a better picture of the average resource utilization of the shared buffer space.

WRED polices the shared buffer pool and marks all packets above a certain rate as "discard eligible."

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.

TRUE

FALSE

64

8

3

16

1

Ensure that traffic flows conform to their traffic profile.

Log violations of metered traffic flows exceeding the CIR value set on the entity across which the traffic is moving.

Provide fairness between traffic flows, so that conforming (in-profile) traffic flows are not starved of bandwidth and/or buffer space by non-conforming (out-of-profile) flows.

Minimize packet loss and reduce end to end latency.

Ensure that variable latencies do not cluster short bursts of originally conforming packets and render them nonconforming.

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.

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.

EXP markings on transit control traffic are not set correctly.

The priority of all self-generated traffic needs to be lowered to allow all other traffic to take precedence.

The priority of various control packets requires special treatment throughout the network.

The BGP process is consuming too many CPU cycles and is impacting OSPF performance.

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.

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.

Packet enters a node will be treated as per the local hop's configured policy.

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