When an 802.11 packet sent by a STA enters the Ethernet through the AP, it is converted into an 802.3 packet, which is not a priority mapping method.

Question

Options

• ANo priority mapping
• BDifferent priorities according to different VAP settings
• CAccording to the order in which the packets arrive at the AP
• DMap the priorities according to UP.

• A
  11% (2)
• B
  6% (1)
• C
  83% (15)

Explanation

When converting 802.11 wireless frames to 802.3 Ethernet frames at an AP, the question asks which option is not a valid priority mapping method. Processing packets purely by arrival order (FIFO) is simply queuing - it applies no priority logic whatsoever, meaning all packets are treated equally regardless of their 802.11 User Priority (UP) value, making C the correct "not a mapping method" answer.

Why the distractors are wrong:

• A (No priority mapping) is technically a valid method - you can deliberately choose to strip and ignore all priority markings during translation.
• B (VAP-based priority settings) is a real method - Virtual Access Points can be configured with a fixed priority, applying it to all traffic on that VAP during frame conversion.
• D (Map according to UP) is the most common method - the 802.11 UP field (0–7) is directly translated to the corresponding 802.1p/DSCP priority in the 802.3 frame.

Memory tip: Think of the three real methods as discard it, hardcode it, or translate it - arrival order does none of these, it just blindly processes whatever shows up first, which is a scheduling policy, not a priority mapping policy.

No community discussion yet for this question.