To grant a Junior Citrix Administrator full access except Shell, User configuration, and Partition configuration, which preexisting command policy should you apply?

To grant a Junior Citrix Administrator full access except Shell, User configuration, and Partition configuration, which preexisting command policy should you apply?

• A. Sysadmin
• B. Operator
• C. Network
• D. Superuser

Answer: (A)

In Citrix ADC, command policies determine which CLI commands a user can run, and built-in policies set different privilege levels. The Sysadmin policy is the broadest, designed for administrators who need extensive control over configuration, diagnostics, and management tasks. Starting with Sysadmin gives you the widest range of legitimate commands, which you can then restrict by denying specific actions you don’t want the junior admin to perform—such as Shell access, User configuration, and Partition configuration. The other options are more limited in scope and wouldn’t provide the necessary breadth of capability for “full access” with only a few exclusions. So applying the Sysadmin policy as the base and then blocking the sensitive commands achieves the described access level.

In Citrix ADC, command policies determine which CLI commands a user can run, and built-in policies set different privilege levels. The Sysadmin policy is the broadest, designed for administrators who need extensive control over configuration, diagnostics, and management tasks. Starting with Sysadmin gives you the widest range of legitimate commands, which you can then restrict by denying specific actions you don’t want the junior admin to perform—such as Shell access, User configuration, and Partition configuration. The other options are more limited in scope and wouldn’t provide the necessary breadth of capability for “full access” with only a few exclusions. So applying the Sysadmin policy as the base and then blocking the sensitive commands achieves the described access level.