An ACME company employee complained about a recent poor-quality VoIP call while moving around their office environment. HPE Aruba Networking Central reported a fair UCC score for this call while…

Question

Options

• ARecent renovations have changed the floor plan
• BThe Call Admission Control level is set too low
• CBSS color mode has not been enabled
• DThe client does not support U-NII-2 or U-NII-2-Extended channels

• A
  60% (12)
• B
  15% (3)
• C
  25% (5)

Explanation

A is correct because recent office renovations physically alter RF propagation - new walls, rooms, or partitions create dead zones and coverage gaps that Aruba Central's AI-based UCC scoring doesn't know about until the floor plan is updated. As the user roams through these newly obstructed areas, signal drops and MOS degrades below 3.0 (2.3 is well into "poor" territory on the 1–5 scale). D is correct because 5GHz is divided into U-NII bands, and U-NII-2/2E are DFS channels; if the client only supports U-NII-1 and U-NII-3, it cannot associate with APs deployed on DFS channels - severely limiting roaming candidates and leaving the client stuck on a distant AP as it moves. B is wrong because Call Admission Control set too low would block the call from being admitted, not let a low-quality call through - a rejected call produces no MOS score at all. C is wrong because BSS coloring is a Wi-Fi 6 co-channel interference mitigation feature that improves spatial reuse in dense environments; its absence degrades aggregate capacity but does not specifically cause mobility-related quality drops.

Memory tip: When you see "poor quality while moving" on 5GHz, think "Map and Channels" - is the coverage map stale (floor plan change), and can the client actually reach all the APs it needs to roam to (channel support)?

No community discussion yet for this question.