A.iRules can be used to look at client requests and server responses to choose a pool member to select for load balancing

B.iRules can be used to add individual control characters to an HTTP data stream.

C.iRules can examine
a server response and
remove
it from a pool if the response is unexpectediRules can examine a server. response and remove it from a pool if the response is unexpected

D.iRules can be used to update the timers
on monitors
as a server load changes.iRules can be used to update the timers on monitors as a server. load changes.

A.Licenses only have to be reactivated for RMAs El no other situations.

B.Licenses generally have to be reactivated during system software upgrades.

C.Never. Licenses are permanent
for the
platform regardless
the version of software installed.

D.Licenses only have to be
reactivated
when new features are added (IPv6, Routing Modules, etc)El no other situations.

A.CLIENT_ACCEPTED

B.HTTP_REQUEST

C.CLIENT_DATA

D.HTTP_DATA

A.Qkview, part numbers for failed components

B.Qkview, EUD output

C.Qkview, UCS archive, core files

D.Qkview, packet capture, UCS archive

A.When the loadElbalancing choice references "node", priority group activation is unavailable.

B.When the loadElb alancing choice references "node", the addresses' parameters are used to make the loadElbalancing choice rather than the member's parameters.

C.LoadElbalancing options referencing "nodes" are available only when the pool members are defined for the "any" port.

D.There is no difference; the two terms are referenced for backward compatibility purposes.