4A0-107 Nokia Quality of Service Questions and Answers

It will be discarded because the high-priority-only threshold is exceeded.

It will be stored in the queue’s reserved buffer space and become out-of-profile.

It will be stored in the queue’s reserved buffer space and remain in-profile.

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

TRUE

FALSE

The default forwarding class defined in the SAP-egress policy.

The forwarding class inherited from network ingress classification.

Best Effort.

If there is no match, packets will be dropped.

All out-of-profile traffic will be dropped before any in-profile is dropped.

The time average factor of 0 will discard all packets arriving in the shared buffer pool.

When the shared buffer utilization reaches 51%, in-profile packets might be dropped.

The highest probability with which an out-of-profile packet can be dropped is 20%.

When an in-profile packet arrives and the shared buffer utilization is at 69%, the packet will have approximately a 60% likelihood of being discarded.

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

The process happens only before the packet goes through the switching fabric.

The process happens only before the packet goes onto the egress port.

Marking/remarking the packets is for future classification.

Marking/remarking the packets will occur right after classification of the packet.

A network policy for every network interface configured on the port.

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.

1

2

3

4

5

8

The larger the configured MBS value, the lower the amount of shaping performed.

When policing is enabled on the SAP-ingress, all traffic is considered as in-profile.

Setting the CIR to 1000 and the PIR to max will enable shapeless policing at 1 Mbps within the SAP-egress policy.

Configuring MBS to equal CBS will disable shaping.

Setting the CIR and PIR to equal values disables soft-policing.

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.

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.

0

min

max D. 50000

All forwarded packets will be in-profile

Packets forwarded above CIR will be marked out-of-profile and the rest will be in-profile

Excess packets that arrive within a burst larger than CBS will be forwarded as out-of-profile

All forwarded packets will be out-of-profile

On the network egress port.

On the SDP.

On the access ingress port.

On the egress MDA.

On the SAP.

On the ingress MDA.

Microflow reservations using RSVP

DSCP to EXP translation

Traffic classification

Automatic profiling and policy configuration

Buffer memory management

Traffic scheduling

When applied at the port level for access ingress.

When applied at the FP (Forwarding Pass) level for access ingress.

When applied at the FP (Forwarding Pass) level for network ingress.

When applied at the port level for network egress.

16

8

32

48

56

H2

NC

L2

EF

H1

BE

SAP-ingress

FFPC

SAP-egress

network-egress

Microflow reservations using RSVP

DSCP to EXP translation

Traffic classification

Automatic profiling and policy configuration

Buffer memory management

Traffic scheduling

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.

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.

Policing, expedited

Metering, marked discard eligible

Marking, marked discard eligible

Policing, discarded

Shaping, discarded

TRUE

FALSE

0

3

6

22

A queue will be serviced as expedited if all of the forwarding classes mapped to it are expedited, regardless of its configured type.

A queue will be serviced as best-effort if all of the forwarding classes mapped to it are best-effort, regardless of its configured type.

A queue will be serviced as expedited if at least one of the forwarding classes mapped to it is expedited, regardless of its configured type.

A queue will be serviced as expedited if its type is configured as expedited, regardless of the forwarding classes mapped to it.

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.

BGP

Telnet

ICMP

SNMP

If CIR = PIR, then all packets will be considered as in-profile.

CIR can be set to 0.

CIR can be larger than PIR.

CIR can be set to ‘max’.

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

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.

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.