In a scenario with a junior administrator configuring a Content Switching virtual server on an HA pair, the next day a senior administrator finds the configuration missing. What is the most likely cause?

• A. Both NetScalers were restarted overnight
• B. The junior administrator connected to the NSIP of the secondary NetScaler in the HA pair
• C. The NetScaler appliances are not on the same firmware version
• D. The junior administrator did not force a failover to save the configuration

Answer: (B)

In an HA pair, the two NetScalers share a single configuration state so both units stay in sync. The unit that currently handles traffic is the primary, and changes made on the standby (secondary) unit are not automatically guaranteed to propagate to the active unit unless you explicitly synchronize the configuration.

If the junior administrator connected to the NSIP of the secondary NetScaler and created the content switching virtual server there, those changes would stay on the standby. Without performing a config sync to push those changes to the primary (and thus to the active configuration used for traffic), the next day the active unit could still reflect the previous state, making the new vserver appear missing when the senior administrator checks.

To prevent this, always make changes on the active unit or immediately synchronize the configuration after changes, and verify that both units have the same configuration.