An airport authority hub must stop one chatty library spoke from consuming the entire hub uplink on a DMVPN WAN. Which QoS approach directly addresses that risk?
Select an answer to reveal the explanation.
Short Explanation
One chatty spoke can eat the whole hub uplink like one gate hogging the airport road. Per-tunnel QoS shapes each spoke’s tunnel so fairness returns. Turning off shortcuts or stripping IPsec does not fix hub uplink starvation.
Full Explanation
DMVPN hub uplinks are often oversubscribed relative to aggregated spoke access rates. Per-tunnel QoS applies shaping or hierarchical policy per spoke tunnel so one chatty site cannot monopolize the hub’s WAN capacity. Disabling shortcuts, inventing MPLS RTs on a DMVPN, or removing IPsec does not provide that fairness. Design hub per-tunnel QoS alongside overlay routing for airport and civic WAN stability.