A transit agency wants one enterprise SSID but different network rights per job function. Which RBAC pattern best achieves that?
Select an answer to reveal the explanation.
Short Explanation
One SSID can still mean many fates when RADIUS attributes hand out roles. Badge-number SSIDs and break-room PSKs are the opposite of tidy RBAC. Rebooting APs is not authorization.
Full Explanation
Using a common SSID with RADIUS-delivered authorization attributes is a standard RBAC pattern for enterprise WLAN: authentication succeeds on one network name while VLAN, ACL, or role privileges differ by identity. Per-person SSIDs, shared depot PSKs, or infrastructure reboots do not provide attribute-based authorization.