Which factor is cited as a cause for newly added configurations on a Content Switching virtual server to disappear when tested later on the HA pair?

• A. The units had different firmware versions
• B. The junior administrator connected to the NSIP of the secondary NetScaler in the HA pair
• C. The changes were not saved to the config repository
• D. A failover occurred automatically without manual intervention

Answer: (B)

In an HA pair, what actually governs the traffic and saved configuration is the unit that is currently active. If you connect to the NSIP of the secondary NetScaler and make changes there, those changes exist only on that secondary unit unless they are explicitly synchronized to the partner and saved to the config repository. When the pair is tested later, the active unit’s configuration (or the primary’s baseline) takes precedence, and without proper synchronization, the edits made on the secondary can be overwritten or not applied, causing them to disappear. To keep changes, you should perform edits on the active unit or ensure proper config synchronization and saving so both units share the same configuration.