If a team member has full admin partition permissions but cannot use aaad.debug in the CLI, what is the most likely reason?

• A. The team member does NOT have permission to use the CLI.
• B. The team member does NOT have Shell access by design.
• C. The team member needs to troubleshoot the issue from the GUI.
• D. The team member is NOT using the CLI correctly.

Answer: (B)

Shell access and partition-level admin rights operate at different layers. The aaad.debug command is a debugging tool that runs in the underlying operating system shell, not in the NetScaler management CLI. Even with full admin partition permissions, you don’t automatically gain access to the OS shell. If shell access is disabled by design for that user, the command won’t be available in the CLI. To troubleshoot, you’d need to enable shell access for that account (if allowed) or use diagnostics available within the NetScaler CLI or GUI that don’t require OS-shell access.