If your customer has a policy requirement that cannot be handled in the Visual Policy Editor, what would you use to supplement the Visual Policy Editor?

iApps are deployment templates that automate configuration of application services - they do not extend or supplement the logic of individual access policies.

TMOS is the underlying operating system for all BIG-IP modules and is not a tool an administrator uses to supplement policy logic.

iControl is F5's REST and SOAP API framework for remote management and automation, not a mechanism for customizing per-session access policy decisions.

iRules use a full TCL scripting language integrated into the BIG-IP TMOS data plane, giving administrators the ability to inspect, modify, and control traffic at a granular level beyond what the Visual Policy Editor's predefined graphical elements support. When an access policy requirement is too complex or specific to be represented visually, iRules can be attached to the policy to handle those conditions programmatically.