H12-311_V3.0 · Question #161
When the 802.11 message sent by the STA is to enter the Ethernet through the AP, it is converted into an 802.3 message, which does not belong to the priority mapping method?
The correct answer is C. According to the order in which the packets arrive at the AP. Packet arrival order (option C) is simply a FIFO queue mechanism, not a priority mapping method at all - it assigns no quality-of-service differentiation, so it cannot be considered a way to map 802.11 priorities to 802.3 priorities during frame conversion. Option A (no…
Question
When the 802.11 message sent by the STA is to enter the Ethernet through the AP, it is converted into an 802.3 message, which does not belong to the priority mapping method?
Options
- ANo priority mapping
- BSet different priorities according to different VAPs
- CAccording to the order in which the packets arrive at the AP
- DMapping to priority according to UP
How the community answered
(47 responses)- A2% (1)
- B13% (6)
- C79% (37)
- D6% (3)
Explanation
Packet arrival order (option C) is simply a FIFO queue mechanism, not a priority mapping method at all - it assigns no quality-of-service differentiation, so it cannot be considered a way to map 802.11 priorities to 802.3 priorities during frame conversion.
Option A (no priority mapping) is a legitimate, if basic, approach: the AP strips QoS information and forwards all frames at the same level, which is a defined behavior. Option B (priority by VAP) is a valid method where different Virtual APs are administratively assigned distinct priority levels before forwarding. Option D (mapping by UP) is the standard QoS approach, where the 802.11 User Priority field values are directly translated into 802.3 CoS/PCP priority markings.
Memory tip: Ask yourself whether a method actually makes a decision about priority. Arrival order never inspects the frame's content or service class - it just processes whatever comes first, making it a scheduling policy, not a priority mapping method.
Topics
Community Discussion
No community discussion yet for this question.