A site needs a virtual server that will use an iRule to parse HTTPS traffic based on HTTP header values. Which two profile types must be associated with such a virtual server. (Choose two.)

The TCP profile provides the required full-proxy transport-layer connection management that the virtual server depends on, and it is the prerequisite base profile before any higher-layer profile can process traffic.

The HTTP profile instructs BIG-IP to parse traffic as HTTP, which activates HTTP iRule events such as HTTP_REQUEST and makes header values accessible to the iRule - without it, the iRule cannot reference or act on HTTP headers regardless of the underlying traffic.

There is no BIG-IP profile type named HTTPS - SSL offload for inbound client connections is handled by a ClientSSL profile, and this profile alone does not enable HTTP header inspection in iRules.

The ServerSSL profile is used to re-encrypt traffic traveling from BIG-IP to backend pool members, not to decrypt or inspect inbound client-side traffic for iRule processing.