Which of the following commands is not required when configuring the Mesh whitelist?

Question

Options

• Aradio radio-id
• Bap-system-profile
• Cmesh-whitelist-profile
• Dpeer-ap mac

• A
  5% (1)
• B
  82% (18)
• C
  9% (2)
• D
  5% (1)

Explanation

ap-system-profile is not part of the Mesh whitelist configuration workflow - it is a general AP system profile used for settings like login credentials and management parameters, completely separate from mesh peer control.

Why the distractors are wrong (i.e., why A, C, and D are required):

• A. radio radio-id - Required to specify which radio interface the mesh link operates on; mesh operates over a specific radio, so you must identify it.
• C. mesh-whitelist-profile - This is the core command that creates/enters the whitelist profile itself; without it, there is no whitelist to configure.
• D. peer-ap mac - Required to explicitly add the peer AP's MAC address to the whitelist, which is the entire purpose of the whitelist - controlling which APs are trusted mesh peers.

Memory tip: Think of the three required commands as who, where, and what - mesh-whitelist-profile (what profile), radio radio-id (where/which radio), and peer-ap mac (who is allowed). The ap-system-profile handles unrelated AP-level settings and has no role in peer trust/mesh whitelisting.

No community discussion yet for this question.