What does the administrator need to do to recover quickly when changes cause outage and there is no Citrix ADC backup?

What does the administrator need to do to recover quickly when changes cause outage and there is no Citrix ADC backup?

• A. Restart the Citrix ADC.
• B. Restore from the revision history.
• C. Run saved versus running configuration.
• D. Run highly availability (HA) file synchronization.

Answer: (B)

In Citrix ADC, you have a built-in revision history that automatically saves previous configurations as you make changes. When an outage is caused by a bad change and there is no external backup, restoring from the revision history lets you roll back to a known-good configuration quickly. This restores the device to a working state without needing another backup copy, and you can then reapply changes carefully. Restarting the appliance won't revert the configuration and just pauses services. Running saved versus running configuration is about comparing or saving configurations, not performing a rollback. HA file synchronization helps keep two devices in sync, but it doesn't provide a quick rollback to a prior working state when the current change has caused the outage.

In Citrix ADC, you have a built-in revision history that automatically saves previous configurations as you make changes. When an outage is caused by a bad change and there is no external backup, restoring from the revision history lets you roll back to a known-good configuration quickly. This restores the device to a working state without needing another backup copy, and you can then reapply changes carefully.

Restarting the appliance won't revert the configuration and just pauses services. Running saved versus running configuration is about comparing or saving configurations, not performing a rollback. HA file synchronization helps keep two devices in sync, but it doesn't provide a quick rollback to a prior working state when the current change has caused the outage.