A township wants a junior civic operator to work in NSX without full administrative power. How should the administrator assign least privilege in the NSX GUI?
Select an answer to reveal the explanation.
Short Explanation
Junior clerks do not get the master key to city hall. In System user management, pick a least-privilege built-in role such as Network Operator. Enterprise Admin, Carbon Black, and Horizon pools are the wrong keys.
Full Explanation
A township that wants a junior civic operator to work in NSX without full administrative power should use System user management and assign a built-in operator role such as Network Operator rather than Enterprise Admin—least privilege for day-2 networking tasks. Assigning Enterprise Admin to every junior operator grants System Fabric and security power far beyond the job. Creating the role in Carbon Black Cloud and expecting automatic mapping to NSX Manager confuses endpoint RBAC with NSX Manager privileges. Publishing a Horizon desktop-pool entitlement grants EUC access to a desktop, not an NSX role on the Manager. Exam caveat: built-in roles differ by what menus they can change; verify the chosen role cannot prepare hosts or alter critical Security objects if that is out of scope for juniors. Operational check: in System user management, assign Network Operator (or equivalent least-privilege built-in) to the junior account, have them log in and confirm required Networking views work while Fabric prep remains blocked, and document the role in the township onboarding checklist. In municipal operations, record the chosen control and the rejected alternatives in the change ticket so future on-call staff understand which failure modes would affect city services. Re-validate after the next maintenance window that the same GUI path and realized state still hold under the current NSX build used by the civic platform team.