What is the likely reason the newly added content switching vServer configurations were not visible the next day?

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

Answer: (A)

In a Citrix ADC HA pair, the management access you use and whether you persist changes are what decide if new configurations survive to the next day. The NSIP you log into determines which unit you’re configuring—the primary (active) unit is the one that holds the live configuration and is responsible for syncing to the standby. If you connect to the NSIP of the primary and make changes like adding content switching vServers, those changes will exist in memory on that active unit, but they will only persist if you explicitly save them to the startup configuration. If they’re not saved, a reboot or failover can cause those changes to be lost, explaining why they’re not visible the next day. The primary reason described here is that the administrator was interacting with the primary unit, and the changes were not saved to startup, so they didn’t survive to the next day.