Which configuration method can be used to restrict access to the NSIP?

Which configuration method can be used to restrict access to the NSIP?

• A. Command policy
• B. Access Control List (ACL)
• C. Authentication policy
• D. Authorization policy

Answer: (B)

Using an Access Control List to restrict management access to the NSIP. An ACL filters traffic by source IP, so you can permit management traffic only from trusted networks and block everything else from reaching the NetScaler’s NSIP. This is the standard way to control who can access the management interface over protocols like SSH or HTTPS, directly at the network edge. Other options don’t fit this specific need as cleanly: a command policy limits what commands can be run on the device but doesn’t control who can reach the NSIP; authentication and authorization policies govern user identity and what they can do after logging in, not the IP-based access to the management IP. So the correct approach is applying an ACL to the NSIP.

Using an Access Control List to restrict management access to the NSIP.

An ACL filters traffic by source IP, so you can permit management traffic only from trusted networks and block everything else from reaching the NetScaler’s NSIP. This is the standard way to control who can access the management interface over protocols like SSH or HTTPS, directly at the network edge.

Other options don’t fit this specific need as cleanly: a command policy limits what commands can be run on the device but doesn’t control who can reach the NSIP; authentication and authorization policies govern user identity and what they can do after logging in, not the IP-based access to the management IP. So the correct approach is applying an ACL to the NSIP.