Question 20
At fictional Harbor Media, a network engineer supporting streaming networks is reviewing route-policy and traffic-control behavior during a controlled failover exercise (HCIP-H12-821-POLICY-005). The observed network issue is: A WAN traffic policy drops packets after a bandwidth threshold because committed and excess rates were configured incorrectly. Which next engineering action best addresses the reported problem?
Explanation
Correct Answer
The directly responsive action is: Recalculate token-bucket parameters and choose intended conform, exceed and violate actions. The specific reported fault is: A WAN traffic policy drops packets after a bandwidth threshold because committed and excess rates were configured incorrectly. Confirmation should show: Controlled traffic shows desired throughput and measured color actions without unexpected loss. The supporting technical principle is: Token bucket policers classify traffic using configured rate and burst parameters.
Incorrect Answers
“Review route-policy node sequence and permit or deny outcomes for matching and unmatched routes” responds to another technical or business failure: A Huawei route-policy matches a prefix but the engineer expects every route passing the first node to continue through later nodes. That source case depends on: Ordered route policies evaluate match conditions and actions rather than combining all nodes indiscriminately. The present issue is: A WAN traffic policy drops packets after a bandwidth threshold because committed and excess rates were configured incorrectly. The more direct action is “Recalculate token-bucket parameters and choose intended conform, exceed and violate actions” because Token bucket policers classify traffic using configured rate and burst parameters.
“Assign the appropriate strict or weighted priority queue behavior with controlled capacity limits” responds to another technical or business failure: A campus egress port uses weighted scheduling but latency-sensitive voice sits behind large bulk transfers. That source case depends on: Egress congestion scheduling determines queuing delay among traffic classes. The present issue is: A WAN traffic policy drops packets after a bandwidth threshold because committed and excess rates were configured incorrectly. The more direct action is “Recalculate token-bucket parameters and choose intended conform, exceed and violate actions” because Token bucket policers classify traffic using configured rate and burst parameters.
“Distinguish policing drop or remark actions from shaping that buffers traffic over time” responds to another technical or business failure: A Huawei MQC behavior applies policing at an uplink but the operator expects it to buffer all excess traffic. That source case depends on: Traffic policing and traffic shaping handle excess rates differently. The present issue is: A WAN traffic policy drops packets after a bandwidth threshold because committed and excess rates were configured incorrectly. The more direct action is “Recalculate token-bucket parameters and choose intended conform, exceed and violate actions” because Token bucket policers classify traffic using configured rate and burst parameters.