A customer has interfering devices that are seen over the air. They contact you and ask you to configure RAPIDS to help identify interfering and rogue APs. HPE Aruba Networking Central identifies a…

Question

Options

• ADevice profiling on the switch
• BFrom the switch MAC address table
• CFrom the switch LLDP neighbors table
• DFrom the AP MAC address table

• B
  96% (24)
• C
  4% (1)

Explanation

Option B is correct because switches dynamically build a MAC address table (CAM table) that maps each learned MAC address to the physical port it was seen on - when a rogue AP connects to a switch port, the switch records that AP's MAC address against that port, and HPE Aruba Networking Central can query this table via the switch to pinpoint the exact port.

Option A (device profiling) identifies what type of device is connected (e.g., OS, category), not where it is physically connected, so it cannot determine a switch port. Option C (LLDP neighbors table) only reflects devices actively advertising LLDP - a rogue AP is unauthorized and unlikely to be running LLDP, so it wouldn't appear there. Option D is a distractor conflating "AP MAC address table" with the switch MAC address table; APs do not maintain port-based MAC forwarding tables the way switches do.

Memory tip: Think of the switch's MAC address table as a "guest registry" - every device that connects gets logged at the "door" (port) it entered. Central checks this registry to catch the rogue at its exact entry point.

No community discussion yet for this question.