Question 660
A post-incident design review discusses the following: During a predeployment review for a high-volume retail campus, the team discovers this design gap: an application marks traffic correctly at the LAN edge but a WAN provider rewrites all DSCP values. An approval gate requires both a measurable acceptance check and a durable prevention control. Which preventive design control MOST DIRECTLY addresses this specific risk?
Explanation
Correct Answer
Use provider class mapping tables and test end-to-end during new circuit acceptance. Apply the same control to the high-volume retail campus rollout checklist. This control targets the underlying design risk. End-to-end QoS behavior depends on consistent class mapping across each administrative transport domain. The follow-up acceptance check remains: The intended markings or provider classes are visible on both sides of the WAN demarcation. The high-volume retail campus acceptance record also captures this result.
Incorrect Answers
An untrusted endpoint can mark arbitrary DSCP values unless network policy validates and normalizes them. The repeat risk here is different: End-to-end QoS behavior depends on consistent class mapping across each administrative transport domain. A directly relevant preventive control is: Use provider class mapping tables and test end-to-end during new circuit acceptance. Apply the same control to the high-volume retail campus rollout checklist.
CBWFQ reserves proportional service opportunity for classes under congestion without assigning every flow an absolute priority queue. The repeat risk here is different: End-to-end QoS behavior depends on consistent class mapping across each administrative transport domain. A directly relevant preventive control is: Use provider class mapping tables and test end-to-end during new circuit acceptance. Apply the same control to the high-volume retail campus rollout checklist.
Average bandwidth below circuit capacity does not prevent short congestion intervals from filling queues. The repeat risk here is different: End-to-end QoS behavior depends on consistent class mapping across each administrative transport domain. A directly relevant preventive control is: Use provider class mapping tables and test end-to-end during new circuit acceptance. Apply the same control to the high-volume retail campus rollout checklist.