Scenario: A Citrix Administrator has configured the following Access Control List (ACL) to block traffic from the IP address 10.102.29.5. add simpleacl rule1 DENY srcIP 10.102.29.5
A week later, the administrator found that the ACL is no longer present on the NetScaler.
What could be the reason for this?
The NetScaler will lose configurations that are not saved before a restart. If the ACL was configured but the changes were not saved, a restart of the NetScaler would cause the configured ACL to be lost. This matches the scenario described, where the administrator found that the ACL was no longer present on the NetScaler. Therefore, the most reasonable explanation is that the NetScaler was restarted without saving the configurations.
B. the only reasonable answer. ACLs do not need to be applied and are not time-based
Its A You need to always apply acl after applying acl cmd ..tested successfully
You are wrong. It's from doc.citrix.com "Applying Extended ACLs and Extended ACL6s: Unlike simple ACLs and ACL6s, extended ACLs and ACL6s created on the Citrix ADC do not work until they are applied."
B is correct
A is correct; https://support.citrix.com/article/CTX110453
No Apply for simple ACLs (only extended ACLs.) no default TTL for simple ACLs, if you don't mention it it stay there in config. if you don't save it, and Ns gets rebooted, you won't be able to see it.