Which statement describes a typical purpose of iRules.

iRules allow for sophisticated, event-driven manipulation of network traffic, including the ability to parse, modify, or insert specific data, such as individual control characters, directly into the HTTP payload or headers based on custom logic.

Updating health monitor timers based on server load is typically handled by adaptive monitoring or external orchestration, not a direct function implemented by iRules, which primarily focus on traffic processing and content manipulation.

Examining server responses to remove a pool member is the primary function of an active health monitor, which is a distinct BIG-IP feature designed for continuous server health checks, not a typical purpose of iRules.

While iRules can influence pool member selection based on request or response data, the fundamental choice of a pool member is managed by configured load balancing methods and persistence profiles; iRules typically provide exceptions or overrides to these, rather than defining the primary selection logic itself.