Which address should be used to perform management changes to ensure they affect the primary in an HA NetScaler pair?

Which address should be used to perform management changes to ensure they affect the primary in an HA NetScaler pair?

• A. Cluster IP address
• B. NetScaler IP address
• C. Subnet IP address
• D. Virtual IP address

Answer: (A)

In an HA NetScaler pair, management changes that you want to affect the primary should be made through the cluster IP. The cluster IP is a floating management address that is owned by the active primary unit and moves to the primary during failover. When you connect to this address, you’re managing the whole pair via the active controller, so configuration updates are applied to the primary and synchronized to the secondary. Connecting to a per-node management IP would target a specific node and could lead to inconsistencies if that node isn’t the primary or if failover occurs. The other addresses serve different roles—Subnet IP for server traffic, Virtual IP for client traffic, and NetScaler IP for individual node management—so they don’t guarantee that changes affect the current primary.

In an HA NetScaler pair, management changes that you want to affect the primary should be made through the cluster IP. The cluster IP is a floating management address that is owned by the active primary unit and moves to the primary during failover. When you connect to this address, you’re managing the whole pair via the active controller, so configuration updates are applied to the primary and synchronized to the secondary. Connecting to a per-node management IP would target a specific node and could lead to inconsistencies if that node isn’t the primary or if failover occurs. The other addresses serve different roles—Subnet IP for server traffic, Virtual IP for client traffic, and NetScaler IP for individual node management—so they don’t guarantee that changes affect the current primary.