Nokia Nokia SRA Composite Exam 4A0-C02 Exam Dumps: Updated Questions & Answers (October 2025)

The EXP bits in the MPLS header.

The packet's source and destination IP addresses.

The service ID of the service to which the SAP belongs.

The dot1p bits in the frame header.

The packet's Ethertype.

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.

CIR

CIR level

CIR weight

Rate

Level

Weight

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.

8, 6, 3

8, 8, 6

16, 8, 4

8, 6, 4

24, 16, 8

The DSCP value will be set to af21.

The DSCP value will be set to af23.

The DSCP value will remain as ef.

The EXP value, in the MPLS headers, will be set to 4.

The EXP value, in the MPLS headers, will be set to 3.

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.

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

The discard probability slope of an in-profile traffic is steeper than that of an out-of-profile traffic.

When the shared buffer utilization reaches 55%, both in-profile and out-of-profile packets may be dropped.

The maximum probability with which an out-of-profile packet can be dropped is higher than that of an in-profile packet.

When the shared buffer utilization is at 61%, only in-profile packets are currently in the shared buffer pool.

SAPs

SDPs

Services

Queues

Schedulers

Forwarding classes

1536

1514

14%

1492

1488

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.

DSCP value

802.1p value

IP DF bit

TCP/UDP port numbers

HTML version number

Signal degradation, attenuation, line loss

Latency, FIFO, WRED

Delay, jitter, packet loss

SNR, queue depth, latency

Attenuation, dispersion, latency

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.

Simplifies signaling.

Reduces core's forwarding database size.

Simplifies MDU configuration.

Enables a scalable inter-domain solution.