F5 301B dumps - 100% Pass Guarantee!

The pool members are serving up simple static web content.

The current virtual server configuration is given as follows:

tmsh list ltm virtual simple

ltm virtual simple { destination 10.10.10.10:80 ip-protocol tcp mask 255.255.255.255 profiles {

http { }

httpcompression { }

oneconnect { }

tcp { }

}

snat automap

vlans-disabled

}

tmsh list ltm pool simple_pool ltm pool simple_pool { members {

10.10.10.11:80 {

address 10.10.10.11 }

10.10.10.12:80

{

address 10.10.10.12 }

10.10.10.12:80

{

address 10.10.10.13 }

} }

Which three objects in the virtual server configuration can be removed without disrupting functionality of the virtual server? (Choose three.)

A. tcp

B. http

C. oneconnect

D. snat automap

E. httpcompression

An LTM Specialist has a OneConnect profile and HTTP profile configured on a virtual server to load balance an HTTP application.

The following HTTP headers are seen in a network trace when a client connects to the virtual server:

Clientside: GET / HTTP/1.1 Host: 192.168.136.100 User-Agent: Mozilla/5.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-EncodinG. gzip, deflate Connection: keep-alive

Serverside: HTTP/1.1 200 OK DatE. 5 Jun 1989 17:06:55 GMT Server: Apache/2.2.14 (Ubuntu) Vary: Accept-Encoding Content-EncodinG. gzip Content-LengtH. 3729 X-Cnection: close Content-TypE. text/html

The LTM Specialist notices the OneConnect feature is working incorrectly.

Why is OneConnect functioning incorrectly?

A. Client must support HTTP/1.0.

B. Client must support HTTP keep-alive.

C. Server must support HTTP/0.9.

D. Server must support HTTP keep-alive.

A virtual server for a set of web services is constructed on an LTM device. The LTM Specialist has created an iRule and applied this iRule to the virtual server:

when HTTP_REQUEST { switch [HTTP::uri] {

"/ws1/ws.jsp" {

log local0. "[HTTP::uri]-Redirected to JSP Pool"

pool JSP

}

default { log local0. "[HTTP::uri]-Redirected to Non-JSP Pool" pool NonJSP

} } } However, the iRule is NOT behaving as expected. Below is a snapshot of the log: /WS1/ws.jsp-Redirected to JSP Pool /WS1/ws.jsp-Redirected to JSP Pool /WS1/ws.jsp-Redirected to JSP Pool /WS1/WS.jsp-Redirected to Non-JSP Pool /ws1/WS.jsp-Redirected to Non-JSP Pool /WS1/ws.jsp-Redirected to JSP Pool /ws1/ws.jsp-Redirected to Non-JSP Pool

What should the LTM Specialist do to resolve this?

A. Use the followinG. switch -lc [HTTP::uri]

B. Use the followinG. switch [string tolower [HTTP::uri]]

C. Set the "Case Sensitivity" option of each member to "None".

D. Select the "Process Case-Insensitivity" option for the virtual server.

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?

A. A virtual server connection limit has been reached.

B. The host at the other end terminated the TCP connection.

C. The LTM device reset the connection because no pool members are available.

D. The LTM device has reached the maximum number of allowed attempts to send the data segment to the affected TCP connection.

-- Exhibit

-- Exhibit -

Refer to the exhibit.

An LTM Specialist is troubleshooting a new HTTP monitor on a pool. The pool member is functioning correctly when accessed directly through a browser. However, the monitor is marking the member as down. The LTM Specialist captures

the monitor traffic via tcpdump.

What is the issue?

A. The server is marking the connection as closed.

B. The pool member is rejecting the monitor request.

C. The monitor request is NOT returning the page body.

D. The 'time-until-up' setting on the monitor is incorrect.