Scenario: A Citrix Administrator configures an 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 discovers that the ACL is no longer present on the Citrix ADC.
What could be the reason for this?
The most plausible reason for the ACL no longer being present on the Citrix ADC is that the Citrix ADC has been restarted without saving the configurations. In Citrix ADC, configurations that are not explicitly saved do not persist across reboots. Hence, if the administrator did not save the configuration after adding the ACL rule, it would be lost upon a restart of the Citrix ADC.
D is the only valid answer here.
C. 600sec=10min simple acl cannot deny based on IP destination. https://docs.citrix.com/en-us/citrix-adc/current-release/networking/access-control-lists-acls/simple-acls-and-simple-acl6s.html Extended ACL can filter based on the destination IP. https://docs.citrix.com/en-us/citrix-adc/current-release/networking/access-control-lists-acls/extended-acls-and-extended-acl6s.html
Admin please delete my answer. This is the wrong answer for the wrong question. My mistake.
voting D
D indeed, apply ACL does not apply to simpleacl. simpleacl TTL is not being used, there is no default expiry. D is indeed the answer.
This has to be: D. The Citrix ADC has been restarted without saving the configurations.
Important is "the ACL is no longer present". Only if the config is saved, the ACL is in the ns.config but if the ACL is not present anymore, it was not saved and got lost during reboot.