Nokia 4A0-107 Nokia Quality of Service Exam Practice Test

8

3

4

5

6

It enables CFHP.

It more scalable than using policers.

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

It allows a set of queues to be shared among multiple SAPs.

16

8

32

48

56

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.

It specifies the maximum rate at which a queue can be serviced.

It specifies the maximum depth of a queue beyond which packets will be dropped.

It specifies the portion of a queue that is taken from the reserved buffer pool.

It specifies the threshold beyond which only in-profile packets will be queued.

It specifies the peak bandwidth that can be attained by the incoming traffic.

802.1p bits

Precedence

DSCP

EXP

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

It will be classified into forwarding class BE and stored in queue 1.

It will be classified into forwarding class BE and stored in queue 8.

It will be classified into forwarding class NC and stored in queue 1.

It will be classified into forwarding class NC and stored in queue 8.

It maps customer traffic to forwarding classes on ingress.

It can use customer QoS markings to do the mapping.

The default SAP-ingress policy classifies all traffic into FC “be” with low priority.

It serves the classification, queuing, and marking functions of QoS but does not serve scheduling

Using dot1p bits of the 802.1q Ethernet frame header

Using DSCP bits within the ToS field of the IP packet header.

Using the IP precedence bits within the ToS field of the IP packet header.

Using the CLP bit of the ATM cell header.

Using the EXP bits of the MPLS transport label header.

1st

8th

9th

17th

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.

TRUE

FALSE

SAPs

SDPs

Services

Queues

Schedulers

Forwarding classes

H2

NC

L2

EF

H1

BE

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.

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.

Router interfaces

Ingress MDA

Ingress Ethernet network ports

Egress Ethernet network ports

Service SAPs

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.

Classification

Marking

Buffer admission control

Scheduling

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.

It defines a premium service that effectively creates a dedicated link between peers.

It defines four different AF traffic classes.

Every AF class in each differentiated services node is allocated a certain amount of forwarding resources.

Within each AF class, IP packets are marked with one of three possible drop precedence values.

The administrative PIR values are ignored and both operational rates are set to the minimum residual rate allowed by the hardware.

The administrative PIR value is ignored and both operational rates are set to the administrative CIR value.

They are chosen as the largest multiple of the hardware rate step that is less than or equal to the corresponding CIR/PIR administrative value.

They are chosen as the smallest multiple of the hardware rate step that is greater than or equal to the corresponding CIR/PIR administrative value.

Spoke-SDPs bound to an IES

Spoke-SDPs bound to a VPRN interface

SAPs

Network interfaces

PIR

CIR

Level

Weight

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.

The IOM3 adds more memory to both forwarding complexes which increases the total number of queues available.

The IOM3 only contains a single forwarding complex which reduces the number of queues used.

The IOM3 allows multiple forwarding classes to be assigned to a single queue.

The IOM3 allows queues to be dynamically allocated between ingress and egress.

The IOM3 has a larger CPU capable of tracking active hardware queue utilization and adjusting memory allocation accordingly.

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.

Each network egress port receives its own buffer pool.

Each SAP-egress port receives its own buffer pool.

All SAP-ingress ports on the same MDA share a buffer pool.

All the network ingress ports on the same MDA share a buffer pool.

Each network ingress port on the same MDA receives its own buffer pool.

The first 3 bits of the DSCP value are copied directly into the EXP field on the first network egress.

The EXP bits are set on the first network egress, based on a combination of the SAP-ingress classification and the network policy applied.

The 3 priority bits are copied directly from the dot1p header into the EXP field of the first MPLS header.

The EXP bits are set based on a default map that translates DSCP codes into internal forwarding classes on SAP-ingress.

CIR

CIR level

CIR weight

Rate

Level

Weight

TRUE

FALSE

2

3

5

6