Which built-in command policy permission level should be used to create local, limited-privilege user accounts that have read-only access and the ability to enable and disable services and servers?

Which built-in command policy permission level should be used to create local, limited-privilege user accounts that have read-only access and the ability to enable and disable services and servers?

• A. Operator
• B. Network
• C. Sysadmin
• D. Read-only

Answer: (A)

Built-in command policy permission levels define what commands a user can execute on the appliance. The Operator level is designed for users who need to monitor and perform essential operational tasks, providing read-only visibility while still allowing them to enable or disable services and servers as needed. This strikes the right balance for local, limited-privilege accounts that must observe the system but also manage core services without full configuration rights. A Read-only level would not permit enabling/disabling, Sysadmin would grant full configuration access, and Network focuses on network-related controls beyond the scope of service management.

Built-in command policy permission levels define what commands a user can execute on the appliance. The Operator level is designed for users who need to monitor and perform essential operational tasks, providing read-only visibility while still allowing them to enable or disable services and servers as needed. This strikes the right balance for local, limited-privilege accounts that must observe the system but also manage core services without full configuration rights. A Read-only level would not permit enabling/disabling, Sysadmin would grant full configuration access, and Network focuses on network-related controls beyond the scope of service management.