A customer would like to allow their IT Helpdesk to configure IoT devices to connect to a single SSID using a unique PSK that other devices cannot use. Which solution would you recommend?

Question

Options

• AMPSK AES with HPE Aruba Networking ClearPass
• BMPSK AES with HPE Aruba Networking Central Cloud Authentication
• CMPSK Local
• DMPSK AES with MAC Auth

• A
  88% (35)
• B
  3% (1)
• C
  3% (1)
• D
  8% (3)

Explanation

MPSK AES with ClearPass is correct because ClearPass Policy Manager provides a dedicated operator portal where helpdesk staff can be granted limited administrative access to provision unique per-device PSKs - each cryptographically isolated so other devices cannot reuse them - all on a single SSID.

Option B (Central Cloud Auth) is wrong because while Central supports MPSK, it lacks ClearPass's purpose-built helpdesk delegation model and granular per-device PSK lifecycle management. Option C (MPSK Local) is wrong because locally-stored PSKs live on the AP/controller with a limited count, no delegation interface, and no centralized helpdesk workflow. Option D (MAC Auth) is wrong because MAC addresses are trivially spoofable, so tying a PSK to a MAC address doesn't actually prevent other devices from using that credential.

Memory tip: "ClearPass = Clear Path for the helpdesk to hand out PSKs" - whenever the exam mentions helpdesk provisioning of unique credentials per device, ClearPass is the answer, not Central (which is cloud management) or local/MAC-based shortcuts.

No community discussion yet for this question.