In an HA pair, why might a newly configured content-switching vServer not show on the active pair after the junior admin saved it on NSIP 192.168.20.10?

In an HA pair, why might a newly configured content-switching vServer not show on the active pair after the junior admin saved it on NSIP 192.168.20.10?

• A. The junior administrator made the changes and did NOT force a failover to save the configuration.
• B. The junior administrator connected to the NSIP of the secondary Citrix ADC in the HA pair.
• C. Both Citrix ADCs in the HA pair restarted overnight.
• D. The Citrix ADC appliances have different firmware versions.

Answer: (B)

In an HA pair, only one unit is active and serving traffic at a time, while the other stays in sync but not actively serving. If you connect to the NSIP of the secondary appliance and save a new content-switching vServer there, that change is stored on the secondary’s copy of the configuration. It won’t automatically appear on the active (primary) unit until you push the configuration across or perform a failover. In short, saving on the secondary’s NSIP means the modification is not yet reflected on the active pair, which is why the new vServer doesn’t show up there. To see it on the active pair, you’d either trigger a failover or perform a config synchronization between the HA nodes.

In an HA pair, only one unit is active and serving traffic at a time, while the other stays in sync but not actively serving. If you connect to the NSIP of the secondary appliance and save a new content-switching vServer there, that change is stored on the secondary’s copy of the configuration. It won’t automatically appear on the active (primary) unit until you push the configuration across or perform a failover. In short, saving on the secondary’s NSIP means the modification is not yet reflected on the active pair, which is why the new vServer doesn’t show up there. To see it on the active pair, you’d either trigger a failover or perform a config synchronization between the HA nodes.