Scenario: A Citrix Administrator made changes to a Citrix ADC, deleting parts of the configuration and saving some new ones. The changes caused an outage that needs to be resolved as quickly as…

Question

Options

• ARestore from the revision history.
• BRun high availability (HA) file synchronization.
• CRestart the Citrix ADC.
• DRun saved versus running configuration.

• A
  85% (17)
• B
  10% (2)
• D
  5% (1)

Explanation

Citrix ADC maintains a revision history of configuration changes, allowing administrators to roll back to a previous known-good state without needing an external backup - making it the fastest recovery path when a bad change causes an outage.

Why the distractors are wrong:

• B (HA file sync): HA sync propagates the current (broken) config from the primary to the secondary - it doesn't restore a previous state and would only spread the problem.
• C (Restart): Restarting the ADC loads the saved config, but if the bad changes were saved (as the scenario states), the broken config persists after reboot.
• D (Saved vs. running config): This comparison tool shows differences between the saved and running configs - useful for auditing, but it doesn't restore anything.

Memory tip: Think of revision history as Citrix ADC's built-in "undo" button - when there's no backup and the saved config is already corrupted, revision history is your only native rollback option.

No community discussion yet for this question.