HPE7-A08 · Question #118
A manufacturing company depends on FTP, email, and RDP services, which are accessed locally. On Monday morning, RDP sessions are not responsive when users on the employee WLAN download their email…
The correct answer is A. Update the employee user role with an ACL on position 3 that puts RDP traffic to a high-priority. Option A is correct because the root cause is uplink congestion at the mobility gateway, and the fix must apply prioritization at that exact bottleneck. An ACL-based QoS policy on the employee user role marks RDP traffic as high-priority, ensuring the gateway's scheduler…
Question
A manufacturing company depends on FTP, email, and RDP services, which are accessed locally. On Monday morning, RDP sessions are not responsive when users on the employee WLAN download their email and large files from the FTP server simultaneously. The network administrator concludes that the mobility gateway's uplinks are congested when that happens. Which would be the best option the network engineer can propose in the implementation plan to improve RDP responsiveness?
Options
- AUpdate the employee user role with an ACL on position 3 that puts RDP traffic to a high-priority
- BChange the employee WLAN from tunneled to bridged so that the bottleneck in the mobility
- CSet the WMM voice DSCP value on the employee WLAN to 56 and enable the RDP application
- DUpdate the spanning-tree configuration from enabled to disabled on the gateway's link
How the community answered
(34 responses)- A53% (18)
- B12% (4)
- C29% (10)
- D6% (2)
Explanation
Option A is correct because the root cause is uplink congestion at the mobility gateway, and the fix must apply prioritization at that exact bottleneck. An ACL-based QoS policy on the employee user role marks RDP traffic as high-priority, ensuring the gateway's scheduler forwards interactive RDP packets before bulk FTP and email traffic during congestion - restoring responsiveness without changing infrastructure.
Why the distractors fail:
- B is wrong because switching from tunneled to bridged mode changes where traffic is processed, not how it's prioritized - it doesn't relieve uplink congestion or give RDP preferential queuing.
- C is wrong because WMM DSCP settings govern the wireless air interface QoS between clients and APs, not the wired uplinks where the congestion actually occurs; fixing the wrong segment doesn't solve the problem.
- D is wrong because disabling spanning tree is a dangerous red herring - it prevents loops but has zero effect on traffic prioritization, and removing it risks broadcast storms that would make performance worse.
Memory tip: Match the fix to the failure point - "uplink congested" → QoS at the uplink. Think ACL = traffic cop at the gateway door, waving RDP through the priority lane while FTP and email wait. WMM is only for the air, STP is only for loops.
Topics
Community Discussion
No community discussion yet for this question.