An LTM Specialist is troubleshooting an HTTP monitor. The pool member is accessible directly through a browser, but the HTTP monitor is marking the pool member as down.
GET / HTTP/1.1
HTTP/1.1 400 Bad Request
DatE. Tue, 23 Oct 2012 21:39:07 GTM
Server: Apache/2.2.22 (FreeBSD) PHP/5.4.4
mod_ssl/2.2.22 OpenSSL/0.9.8q DAV/2
Content-LengtH. 226
Connection: close
Content-TypE. text/html; charset=iso-8859-1
Which issue is the pool member having?

-- Exhibit - -- Exhibit -Refer to the exhibit.

An LTM device is used to load balance web content over a secure channel.
The developers of the web content have done a trace using an HTTP profiler application. They believe that allowing the LTM device to compress traffic to the client will improve performance. The client can utilize GZIP or deflate compression algorithms.
An LTM Specialist must implement the compression.
The LTM Specialist has completed the following actions:
1.Create the relevant profile.
2.Apply the relevant profile to the virtual server (VS).
After applying the relevant profile, the LTM device is failing to compress the traffic. Instead, the traffic is being served with an error.
What is the problem?

An LTM device has been configured to log the reasons for generating TCP RST packets.
The following log entry occurs:
"01230140:3: RST sent from 192.168.1.100:80 to 192.168.1.124:39272, [0x112d82a:1721] {peer} TCP RST from remote system." Which condition will trigger this log entry?

-- Exhibit-

-- Exhibit --
Refer to the exhibit.
A user is unable to access an HTTP application via a virtual server.
What is the cause of the failure?

An LTM device is monitoring pool members on port 80. The LTM device is using an HTTP monitor with a send string of GET / and a blank receive string.
What would cause the pool members to be marked down?