Question 590
Original unofficial Cisco 350-501 SPCOR v1.1 service-provider network operations scenario: An operator makes a rigid guaranteed-bandwidth statement based only on DSCP marks without checking that the service queue has reserved capacity. Which observable result most directly verifies that this network issue was resolved?
Explanation
Correct Answer
For this scenario, the observed situation is: An operator makes a rigid guaranteed-bandwidth statement based only on DSCP marks without checking that the service queue has reserved capacity. The most directly supported response is: Combine marking with validated scheduling, capacity planning, and traffic admission controls. Technical basis: Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. Evidence of success: Under full load, traffic receives the planned queue share and premium latency stays within SLA. Ongoing protection: Test QoS performance under congestion, not only when links are idle.
Incorrect Answers
EVPN MAC mobility signaling tracks changes in a host's attachment location. Evidence of that behavior would not establish the required outcome here. The case-specific failure is: Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. A passing check should show: Under full load, traffic receives the planned queue share and premium latency stays within SLA.
The proposed test would be relevant to: MPLS L3VPN forwarding depends on both service-label import and transport next-hop resolution. The reported problem follows from: Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. Instead, verify: Under full load, traffic receives the planned queue share and premium latency stays within SLA.
The proposed test would be relevant to: Multicast reverse-path forwarding prevents looping traffic by checking upstream source reachability. The reported problem follows from: Marking identifies classes; enforcement comes from queueing, shaping, and policer configuration. Instead, verify: Under full load, traffic receives the planned queue share and premium latency stays within SLA.