4A0-107 Exam Dumps - Nokia Quality of Service

Negative jitter results in a smaller than expected interval between transmitted packets.

Jitter does not have any effect on the quality of video applications.

Serialization delay is not affected by congestion.

Queuing delay is a fixed form of delay in networks.

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.

A device that provides no differentiation between customer traffic flows.

A device that classifies and marks customer traffic.

A device that uses MPLS EXP bits to differentiate between traffic flows.

A device that creates macroflows towards the core from multiple customer sites.

A device that passes macroflows while optionally changing QoS markings.

The CIR has no influence on the forwarding rate of the policer traffic.

The CIR influences whether a packet is considered high-profile or low-profile.

The policer discards all incoming packets when PIR bucket reaches the MBS level.

PIR bucket forwards packets that arrive with rates above PIR as out-of-profile.

The default forwarding class for ICMP traffic is BE and cannot be changed.

The SAP has been shut down.

Queue 3 has no PIR or CIR configured, and thus cannot hold any packets.

The SAP-ingress policy has not been applied to the SAP.

Scheduler policies cannot be children of an egress port-scheduler.

HQoS provides a static method of allocating scheduling resources to each queue and/or child.

Scheduler policies can be applied to the MDA to schedule network ingress traffic.

Every time a scheduler-policy is assigned to a SAP, a new hardware scheduler is created to service the SAP.

A scheduler applied to multiple SAPs within the same service will result in a single hardware scheduler operating across all SAPs within the service.

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.

2

3

5

6

None of the above.

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

It will be marked as DSCP BE and classified into forwarding class BE.

It will be marked as DSCP NC1 and classified into forwarding class BE.

It will be marked as DSCP NC1 and classified into forwarding class NC.

It will be marked as DSCP NC1 and classified into forwarding class AF.

IOM3

FP3 based IMM

IOM1

IOM2

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

3

4

6

8

Several Tier 1, Tier 2, and Tier 3 schedulers can be defined within a policy.

A queue’s parent scheduler must be a Tier-3 scheduler.

The parent must have a higher level in the hierarchy.

If no parent is configured, the queue/scheduler is considered orphaned.

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 FP (Forwarding Pass) level for access ingress

When applied at the port level for network egress

Microflow reservations using RSVP

DSCP to EXP translation

Traffic classification

Automatic profiling and policy configuration

Buffer memory management

Traffic scheduling

Real-time

Assured

Non-conforming

High priority

In-profile

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.

The EXP field in the bottom MPLS header will be marked.

The EXP field in both the top and bottom MPLS headers will be marked.

For Layer 2 services, the top MPLS header will be marked; for Layer 3 services, the bottom MPLS header will be marked.

The EXP field in the top MPLS header will be marked.

Neither the top nor the bottom EXP field will be marked since EXP remarking can only be done on the network 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 SAP egress, the profile marked at ingress may change based on the scheduling loop.

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

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

3

4

5

6

8

16

32

48

PIR = 5 Mbps, CIR = 0 Mbps

PIR= 4 Mbps, CIR = 1 Mbps

PIR= 6 Mbps, CIR = 4 Mbps

PIR= 6 Mbps, CIR = 1 Mbps

It sets both the forwarding class and the packet’s dot1p, lsp-exp, precedence, or dscp field to the same value.

It groups all packets together into a single aggregate stream, and gives all packets the same treatment.

It copies the three most significant bits in the packet’s dscp field into the forwarding class.

It assigns a forwarding class based on the packet’s dot1p, lsp-exp, precedence, or dscp value.

The EXP bits in the MPLS header.

The packet's source and destination IP addresses.

The packet's DSCP bits.

The dot1p bits in the frame header.

The ID of an SDP that is transporting the packet.

Signal degradation, attenuation, line loss

Latency, FIFO, WRED

Delay, jitter, packet loss

SNR, queue depth, latency

Attenuation, dispersion, latency

L2

H1

AF

BE

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 based on a WRR distribution method that takes into account the CIR and PIR requested at each level and the max speed, either default or configured, on egress.

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.

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.

DiffServ reserves resources dynamically using the RSVP protocol.

DiffServ only requires packets to be classified into forwarding classes at the first network hop.

DiffServ provides granular differentiation and superior fairness because it processes traffic streams individually.

DiffServ is more scalable it treats traffic streams as aggregates.