Which events are valid iRule events triggered by BIG-IP ASM processing? (Choose 2)

ASM_REQUEST_BLOCKING is a valid iRule event that fires when ASM determines a request should be blocked due to a policy violation, allowing the iRule to inspect or influence the blocking decision.

ASM_REQUEST_ACCEPTED is not a defined BIG-IP ASM iRule event; no standard iRule event exists that fires specifically when a request passes policy without violation.

ASM_REQUEST_VIOLATION is a valid iRule event that fires when ASM detects one or more violations in a request, giving iRule logic access to violation details before the final enforcement action.

ASM_RESPONSE_BLOCKING is not a valid ASM iRule event name; the correct response-side violation event is ASM_RESPONSE_VIOLATION, not a BLOCKING variant.