Nokia QoS study plan

Define the end-to-end QoS pipeline (classification, marking, queuing, scheduling, shaping/policing, drop) and place each Nokia implementation point on that pipeline

Explain the difference between DiffServ per-hop behaviors (EF, AF classes, default) and map them to Nokia forwarding-class and profile concepts without confusing the two naming schemes

Sketch the internal packet path through an Nokia IP router (ingress classification, fabric, egress queues) from memory and label where each QoS action occurs

Build a personal glossary of 25 QoS terms with a one-line definition and where each appears in Nokia CLI context

Configure ingress classification using IP criteria (DSCP, IP precedence, ACL-based match) on a Nokia router in a lab or simulator and verify the assigned forwarding class

Configure egress queuing with at least three queues, assign scheduler weights, and demonstrate that a high-priority queue drains before a best-effort queue under congestion

Write a marking policy that re-marks DSCP at ingress and at an edge boundary, then verify the marked value in packet captures

Compare policer versus shaper behavior in a lab test and record the resulting drop and delay characteristics

Construct a service-level QoS policy that binds classification, marking, policing, and queuing into a single deployable template for one service type

Explain how QoS policies attach to service constructs (SAP, SDP, network interface) and predict which attachment point wins when policies overlap

Design a multi-service scenario (voice, business data, best-effort internet) with explicit bandwidth guarantees and calculate whether the sum of guarantees fits the link

Draft a rollback plan for a QoS policy change on a production router, listing the verification steps before and after commit

Trace how a mobile transport QoS marking survives from the radio access side through backhaul to the core, noting where remarking or trust boundaries occur

Explain the role of QoS in mobile transport for latency-sensitive traffic (voice, signaling) versus bulk traffic, and identify the transport bottleneck points

Configure and verify a hierarchical scheduling structure (parent shaper with child queues) and describe the resulting behavior under oversubscription

Compare fixed transport QoS requirements (business Ethernet, wholesale) with mobile backhaul requirements and list three concrete differences

Build an end-to-end QoS design for a transport ring carrying mobile backhaul and fixed business services, allocating bandwidth per class and justifying each allocation

Identify the counters and statistics available per queue, per policer, and per forwarding class on Nokia routers and state what each counter proves

Write five troubleshooting scenarios (voice quality degradation, policer over-drop, queue starvation, misclassification, shaper misconfiguration) with a first-check and root-cause path for each

Practice reading queue statistics to distinguish congestion drops from policer drops in a lab capture

Design a monitoring approach that measures per-class latency, jitter, loss, and throughput, and explain which tool or counter answers which question

Set up a lab test that injects congestion and record per-class behavior over time to prove the QoS design meets its intent

Revisit QoS fundamentals and correct any misconceptions found during weeks 1-5, rewriting your glossary entries that proved wrong

Explain how assurance and telemetry data feed back into policy tuning, with one concrete example of a policy change driven by monitoring data

Consolidate all five domains into a single reference sheet of 40 facts you must know cold, covering architecture, classification, policy, transport, and monitoring

Complete at least 60 practice questions across all domains and log every wrong answer with the underlying concept it exposed

Re-derive the bandwidth math for a four-class design from scratch without notes and check it against your week 3 document

Reconfigure a full QoS policy from a blank lab device in under 30 minutes without reference material

Review the error log from week 7 and close every gap by re-reading notes and re-running the relevant lab step

Take two full-length timed practice exams and score above your target threshold on both

Explain aloud, without notes, the complete QoS lifecycle from classification to assurance for both a mobile backhaul and a fixed business service

Finalize a one-page exam-day reference containing only the facts you repeatedly missed