Comprehensive and Detailed Explanation
HPE Press guide context | PDF page 842 | HPE Press, Aruba Certified Associate – Campus Access Official Certification Study Guide
Technical Deep Dive — Original Chat Wording
Role-Based Access Control (RBAC) is an authorization framework that determines which operations users are permitted to perform according to their assigned roles.
In HPE Aruba Networking Central, RBAC helps organizations separate administrative responsibilities and restrict access to sensitive network configuration functions.
Instead of independently defining every permission for every administrator, an organization assigns permissions to roles.
Users are then associated with the appropriate roles according to their operational responsibilities.
For example, an Administrator role can provide broad configuration and management permissions.
An Operator role can permit selected operational and troubleshooting activities without necessarily granting full administrative access.
A View Only role restricts users to permitted read-only operations.
This approach simplifies access management, particularly when organizations have large IT teams with different responsibilities.
RBAC also supports the principle of least privilege, whereby users receive only the permissions necessary to perform their assigned duties.
Modern Central deployments can additionally use scope and resource restrictions to control where those permissions apply.
However, location or device-group membership alone does not define RBAC permissions.
The essential relationship is that permissions belong to roles, and roles are assigned to users .
This distinction improves consistency, reduces administrative errors, and simplifies security auditing.
Therefore, Option B (Permissions are assigned based on user roles) is correct.