Which scenario could explain why an ACL disappears after a restart if changes were not saved?

Which scenario could explain why an ACL disappears after a restart if changes were not saved?

• A. The administrator did NOT run the apply ACL command.
• B. The simple ACLs remain active for 600 seconds.
• C. The simple ACLs remain active for 60 seconds.
• D. The Citrix ADC has been restarted without saving the configurations.

Answer: (D)

ACLs on Citrix ADC are kept in the running configuration while the device is up. A restart loads the startup configuration from storage. If changes were made to an ACL but were not saved, those edits exist only in memory and are not written to the startup config. When the device reboots, it restores the startup config, so the unsaved ACL changes are lost and the ACL appears to disappear. To keep the ACL after a reboot, you must save the running configuration to startup configuration before restarting (for example, save ns config). The other scenarios don’t explain persistence across a reboot: not applying the ACL means it never takes effect, and time-limited activations would expire while the system is running rather than be preserved or lost across restarts.

ACLs on Citrix ADC are kept in the running configuration while the device is up. A restart loads the startup configuration from storage. If changes were made to an ACL but were not saved, those edits exist only in memory and are not written to the startup config. When the device reboots, it restores the startup config, so the unsaved ACL changes are lost and the ACL appears to disappear. To keep the ACL after a reboot, you must save the running configuration to startup configuration before restarting (for example, save ns config). The other scenarios don’t explain persistence across a reboot: not applying the ACL means it never takes effect, and time-limited activations would expire while the system is running rather than be preserved or lost across restarts.