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…

Question

Options

• AThe administrator did NOT run the apply ACL command.
• BThe simple ACLs remain active for only 600 seconds.
• CThe simple ACLs remain active for only 60 seconds.
• DThe Citrix ADC has been restarted without saving the configurations.

• A
  87% (39)
• B
  9% (4)
• C
  2% (1)
• D
  2% (1)

Explanation

On Citrix ADC, creating an ACL rule with add simpleacl only defines the rule - it does not activate it. The administrator must also run the apply acls command to push the defined ACL rules into the active policy engine. Without this step, the rule was never enforced and would not persist, which is why it was gone a week later.

Why the distractors are wrong:

• B (600 seconds): While 600 seconds is the default TTL for simple ACLs when a timeout is not specified, a 10-minute expiration would not explain a rule disappearing a week later - it would have been gone within minutes of creation.
• C (60 seconds): Simple ACLs have no 60-second lifetime; this figure is fabricated and does not correspond to any Citrix ADC default.
• D (restarted without saving): A restart without saving would wipe all unsaved configurations, not just the ACL - making this an incomplete and less precise explanation for this specific scenario.

Memory tip: Think "Define, then Deploy" - on Citrix ADC, ACL commands follow a two-step pattern: add (define the rule) → apply acls (activate it). If you skip the apply step, the rule never goes live.

No community discussion yet for this question.