4A0-107 Nokia Quality of Service Free Practice Exam Questions (2025 Updated)

IS-IS

RSVP

ICMP

BGP

A point in the network where EXP bits can be mapped to one of eight predefined FCs, each one with its own queue.

A logical point in a service tunnel where all of customer traffic is aggregated.

A point at which the initial classification of customer traffic occurs.

A point in the network where QoS parameters are discarded in favor of lower-level hardware queuing functions, such as LLI (Link Layer Interleave).

A point in the network where traffic flows from multiple different services are queued together, based on forwarding class.

Queue 6 within-CIR packets, then queue 5 within-CIR packets, then queue 5 and queue 6 above-CIR packets in round-robin.

Queue 6 within-CIR packets, then queue 5 within-CIR packets, then queue 5 and queue 6 above-CIR packets in biased round-robin.

Queue 6 within-CIR packets, then queue 5 within-CIR packets, then queue 6 above-CIR packets, and finally queue 5 above-CIR packets.

Queue 6 and queue 5 within-CIR packets in biased round-robin, then queue 5 and queue 6 above-CIR packets in round-robin.

There are a maximum of 8 levels of priority serviced using a round-robin algorithm.

The default scheduler will spend an equal amount of time in each queue, as long as there is traffic present

The H1 internal forwarding class will receive its CIR before AF traffic.

Orphaned queues will be scheduled out of the BE queue.

A queue servicing EF and AF traffic will require explicit configuration to set the queue to expedited.

SAP-ingress policy

SAP-egress policy

IP-criteria policy

Network-queue policy

Slope policy

Network policy

An egress unicast queue defined in a network queue policy

An ingress unicast queue defined in a SAP-ingress policy

An ingress multipoint queue defined in a SAP-ingress policy

An ingress multipoint queue defined in a network queue policy

Gold

Assured

High Priority

Best Effort

IntServ uses a protocol like RSVP to provide QoS guarantees on a per-flow basis.

DiffServ groups multiple microflows into bigger streams called macro flows.

Intserv requires that network routers allocate resources for thousands of individual flows.

Diffserv classifies packets into forwarding classes only at the first network hop.

Shapeless policing at SAP-ingress only.

Shapeless policing at SAP-ingress and egress.

Biased round robin queuing at ingress only.

Soft shaping at all network interfaces.

Soft shaping at network ingress only.

8

3

4

5

6

All in-profile packets in round-robin, then all out-of-profile packets in biased round-robin.

In-profile EF packets, then in-profile H2 packets, then in-profile AF packets, then out-of-profile EF packets, then out-of-profile H2 and AF packets, and then out-of-profile BE packets.

In-profile EF, H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF packets, then in-profile H2 and AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

In-profile EF and H2 packets, then in-profile AF packets, then out-of-profile H2, AF and BE packets in biased round-robin.

NC, low

NC, high

BE, low

BE, high

Packets that arrive in a burst are immediately dropped; packets that arrive with the proper in between space are immediately.

Packets are buffered on arrival and are forwarded at an average rate conforming with PIR, typically, with a reduced burstiness.

Packets with an average arrival rate higher than PIR are immediately dropped; conforming packets are forwarded at the same rate at which they arrive.

Packets with an average arrival rate higher than PIR are buffered for future processing; conforming packets are immediately forwarded.

A customer is complaining that his VoIP traffic is being dropped even though it is sending the correct DSCP markings. Packets are not being dropped on ingress.

A customer is complaining that his VoIP traffic is being dropped even though it is sending the correct DSCP markings. Packets are being dropped on ingress.

A commercial builder has requested numerous dot1Q epipes, VPRNs, and VPLS services to a business park and is only paying up to a maximum 200Mbps.

An equipment manufacturer has requested a NULL epipe service that will transparently pass dot1Q between the new location and national headquarters.

QoS is not configured on the router.

Packets in forwarding classes "be" and "12" are being queued.

Traffic belonging to forwarding class "ef" is not experiencing queuing delays.

Traffic belonging to forwarding class "11 "will never make use of the shared buffer pool.

Out-of-profile traffic in the shared buffer pool is being dropped.

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

1st

8th

9th

17th

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.