H12-323_V2.0 · Question #15
To prevent non-critical services from occupying too much network resources, QoS policies can be configured in application protocols, namely smart application control SAC. Which of the following…
The correct answer is C. In roaming scenarios, the SAC policy of the user after roaming is based on the policy issued by. Option C describes SAC roaming policy behavior incorrectly. In roaming scenarios, the SAC policy applied to a user after roaming is not based on the policy issued by the roamed-to (target) controller or location - it is based on the policy from the home/original WAC (Wireless…
Question
To prevent non-critical services from occupying too much network resources, QoS policies can be configured in application protocols, namely smart application control SAC. Which of the following descriptions of SAC functions is wrong?
Options
- ASAC mainly detects and identifies the 4th to 7th layer content and some dynamic protocols (such
- BFor the identified application protocol packets, their priority can be modified or directly discarded
- CIn roaming scenarios, the SAC policy of the user after roaming is based on the policy issued by
- DWhen a CAPWAP tunnel is established between WAC and AP to centrally forward user
How the community answered
(15 responses)- A13% (2)
- B7% (1)
- C73% (11)
- D7% (1)
Explanation
Option C describes SAC roaming policy behavior incorrectly. In roaming scenarios, the SAC policy applied to a user after roaming is not based on the policy issued by the roamed-to (target) controller or location - it is based on the policy from the home/original WAC (Wireless Access Controller) that initially served the user. The policy follows the user's session context, not the destination network element's configuration.
Options A, B, and D describe accurate SAC behaviors: A is correct because SAC operates at OSI layers 4–7 and handles dynamic protocol identification; B is correct because SAC can both remark packet priority and drop packets for identified application flows; D is correct in that SAC functions apply within CAPWAP tunnel-based centralized forwarding scenarios between WAC and APs.
Memory tip: Think of SAC roaming policy like a hotel guest's VIP status - the privileges (policy) are set by the home account (original WAC), not by whichever branch (AP/new controller) the guest walks into. When option C implies the destination sets the rules, that's the red flag.
Topics
Community Discussion
No community discussion yet for this question.