An LTM Specialist configures an HTTP monitor as follows:
ltm monitor http stats_http_monitor {
defaults-from http
destination *:*
interval 5
recv "Health check: OK"
send "GET /stats/stats.html HTTP/1.1\\r\\nHost: www.example.com\\r\\nAccept-EncodinG. gzip, deflate\
\r\\nConnection: close\\r\\n\\r\\n"
time-until-up 0
timeout 16
}
The monitor is marking all nodes as down. A trace of the HTTP conversation shows the following:
GET /stats/stats.html HTTP/1.1
Host: www.example.com
Accept-EncodinG. gzip, deflate
Connection: close
HTTP/1.1 401 Authorization Required
DatE. Tue, 23 Oct 2012 19:38:56 GMT
Server: Apache/2.2.15 (Unix)
WWW-AuthenticatE. Basic realm="Please enter your credentials"
Content-LengtH. 480
Connection: close
Content-TypE. text/html; charset=iso-8859-1
Which action will resolve the problem?

• A.Add a valid username and password to the monitor.
• B.Add a backslash before the colon in the receive string.
• C.Use an HTTPS monitor with a valid certificate instead.
• D.Add an NTLM profile to the virtual server.

Comment: *

Name: *

Email: *

Verification: *

Given the log entry:
011f0005:3: HTTP header (32800) exceeded maximum allowed size of 32768 (Client sidE. vip=/Common/ VS_web profile=http pool=/Common/POOL_web client_ip=10.0.0.1) Which HTTP profile setting can be modified temporarily to resolve the issue?

• A.Increase Maximum Header size
• B.Decrease Maximum Header size
• C.Decrease Maximum Header Count
• D.Increase Maximum Requests
• E.Increase Maximum Header Count
• F.Decrease Maximum Requests

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -

-- Exhibit --
Refer to the exhibit.
The decoded TCPDump capture is a trace of a failing health monitor. The health monitor is sending the string shown in the capture; however, the server response is NOT as expected. The receive string is set to
'SERVER IS UP'.
What is the solution?

• A.The /test_page.html does NOT exist on the web server and should be added.
• B.Incorrect syntax in send string. 'Connection: Close' should be 'Connection: Open'.
• C.The GET request Host header field requires a host name.
• D.Incorrect syntax in send string. 'HTTP/1.1' should be 'HTTP1.1'.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -


-- Exhibit --
Refer to the exhibits.
After upgrading LTM from v10 to v11, users are unable to connect to an application. The virtual server is using a client SSL profile for re-terminating SSL for payload inspection, but a server SSL profile is being used to re-encrypt the request.
A client side ssldump did NOT show any differences between the traffic going directly to the server and the traffic being processed by the LTM device. However, packet capture was done on the server, and differences were noted.
Which modification will allow the LTM device to process the traffic correctly?

• A.Change to different ciphers on the server SSL profile.
• B.Enable ProxySSL option in the server SSL profile.
• C.Enable Strict Resume.
• D.Change Secure Renegotiation to "Request."

Comment: *

Name: *

Email: *

Verification: *

An LTM Specialist must perform a packet capture on a virtual server with an applied standard FastL4 profile. The virtual server 10.0.0.1:443 resides on vlan301.
Which steps should the LTM Specialist take to capture the data payload successfully while ensuring no other virtual servers are affected?

• A.A new FastL4 profile should be created and applied to the virtual server with PVA acceleration disabled. Then the packet capture tcpdump -ni vlan301 should be executed on the command line interface.
• B.The packet capture tcpdump -ni vlan301 should be executed on the command line interface. There is no need to change profiles or PVA acceleration.
• C.The LTM device is under light load. The traffic should be mirrored to a dedicated sniffing device. On the sniffing device, the packet capture tcpdump -ni vlan301 should be executed.
• D.The standard FastL4 profile should have PVA acceleration disabled. Then the packet capture tcpdump -ni vlan301 should be executed on the command line interface.

Comment: *

Name: *

Email: *

Verification: *