Quick Answer

The correct order for LLQ configuration for voice traffic begins with classifying voice traffic using a class-map that matches DSCP EF, then creating a policy-map and assigning that class to the priority queue, followed by optionally configuring a bandwidth guarantee for other classes, applying the service-policy on the WAN interface, and finally verifying LLQ using show policy-map interface. This sequence is correct because Low Latency Queuing (LLQ) requires traffic to be identified first through classification, then placed into a strict priority queue to ensure minimal delay and jitter for real-time voice packets, with verification confirming that the policy is actively shaping traffic as intended. On the ENCOR 350-401 exam, this drag-and-drop task tests your understanding of QoS implementation order, and a common trap is placing the verification step too early or forgetting that the class-map must be created before the policy-map references it. A useful memory tip is to think “Classify, Prioritize, Guarantee, Apply, Verify” — or simply “CP-GAV” — to lock in the correct sequence from first to last.