A Citrix Administrator deletes parts of the configuration and saves, with no backup available. How should the administrator recover the configuration quickly?

A Citrix Administrator deletes parts of the configuration and saves, with no backup available. How should the administrator recover the configuration quickly?

• A. Restore from revision history.
• B. Run HA file synchronization.
• C. Run Save v/s Running configuration.
• D. Restart the Citrix ADC

Answer: (A)

Restoring from a previous configuration revision is the quickest and most reliable way to recover when parts of the configuration have been deleted and saved. Citrix ADC keeps snapshots of the configuration each time you save, so you can roll back to a known-good state without needing external backups. This lets you revert the running configuration to a version that existed before the accidental deletion, restoring only what was there at that time. To do this, open the management interface and navigate to the configuration revisions area, select a revision created before the deletion, and restore or apply it as the active running configuration. The device will load that snapshot, bringing back the missing parts with minimal downtime. If the platform supports it, you may choose to restore and then save the configuration to startup so the change persists across reboots. Other options don’t provide the same immediate, built-in safety net. Relying on HA file synchronization depends on the other node containing the desired older config and can overwrite the current state unpredictably. Saving the running configuration versus the startup config won’t undo the deletion, and restarting won’t revert to a previous state unless you’ve already loaded a prior revision.

Restoring from a previous configuration revision is the quickest and most reliable way to recover when parts of the configuration have been deleted and saved. Citrix ADC keeps snapshots of the configuration each time you save, so you can roll back to a known-good state without needing external backups. This lets you revert the running configuration to a version that existed before the accidental deletion, restoring only what was there at that time.

To do this, open the management interface and navigate to the configuration revisions area, select a revision created before the deletion, and restore or apply it as the active running configuration. The device will load that snapshot, bringing back the missing parts with minimal downtime. If the platform supports it, you may choose to restore and then save the configuration to startup so the change persists across reboots.

Other options don’t provide the same immediate, built-in safety net. Relying on HA file synchronization depends on the other node containing the desired older config and can overwrite the current state unpredictably. Saving the running configuration versus the startup config won’t undo the deletion, and restarting won’t revert to a previous state unless you’ve already loaded a prior revision.