There are three servers in the pool: 172.16.20.1, 172.16.20.2, and 172.16.20.3, with the virtual IP address
10.0.20.88.
A user CANNOT connect to an HTTP application. To understand the problem and find a solution, the LTM Specialist runs two concurrent traces on the LTM device, with the following results:
Trace on client side:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on 0.0, link-type EN10MB (Ethernet), capture size 96 bytes
22:22:07.423759 IP 172.16.20.100.53875 > 10.0.20.88.80: S 998346084:998346084(0) win 5840 <mss
1460,sackOK,timestamp 67942058 0,nop,wscale 4>
22:22:07.424056 IP 10.0.20.88.80 > 172.16.20.100.53875: S 4671780:4671780(0) ack 998346085 win 4380
<mss 1460,nop,wscale 0,nop,nop,timestamp 2392362490 67942058,sackOK,eol>
22:22:07.424776 IP 172.16.20.100.53875 > 10.0.20.88.80: . ack 1 win 365 <nop,nop,timestamp 67942058
2392362490>
22:22:07.424790 IP 172.16.20.100.53875 > 10.0.20.88.80: P 1:149(148) ack 1 win 365 <nop,nop,timestamp
67942058 2392362490>
22:22:07.424891 IP 10.0.20.88.80 > 172.16.20.100.53875: . ack 149 win 4528 <nop,nop,timestamp
2392362491 67942058>
22:22:12.024850 IP 10.0.20.88.80 > 172.16.20.100.53875: R 1:1(0) ack 149 win 4528
6 packets captured
6 packets received by filter
0 packets dropped by kernel
Trace on server side:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on internal, link-type EN10MB (Ethernet), capture size 96 bytes
22:22:07.424881 IP 172.16.20.100.53875 > 172.16.20.2.80: S 51116678:51116678(0) win 4380 <mss
1460,nop,wscale 0,nop,nop,timestamp 2392362491 0,sackOK,eol>
22:22:08.424893 IP 172.16.20.100.53875 > 172.16.20.2.80: S 51116678:51116678(0) win 4380 <mss
1460,nop,wscale 0,nop,nop,timestamp 2392363491 0,sackOK,eol>
22:22:09.625082 IP 172.16.20.100.53875 > 172.16.20.2.80: S 51116678:51116678(0) win 4380 <mss
1460,nop,wscale 0,nop,nop,timestamp 2392364691 0,sackOK,eol>
22:22:10.825194 IP 172.16.20.100.53875 > 172.16.20.2.80: S 51116678:51116678(0) win 4380 <mss
1460,sackOK,eol>
4 packets captured
4 packets received by filter
0 packets dropped by kernel
What should the LTM Specialist do to solve the problem?

• A.Modify the monitor of the pool.
• B.Configure the virtual server to use SNAT.
• C.Enable the virtual server.
• D.Edit the packet filter rules.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -

-- Exhibit -Refer to the exhibit.
An HTTP monitor always marks the nodes in the pool as down. The monitor's definition and the HTTP headers from the monitor request and response are provided.
What is the issue?

• A.The monitor is NOT configured to follow the redirect.
• B.The send string is incorrect.
• C.The response is compressed.
• D.The monitor timeout is too short.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit-

-- Exhibit -Refer to the exhibit. An LTM Specialist is working on an LTM 11.0.0 installation and has identified a security
vulnerability as shown in the exhibit. The LTM Specialist is tasked with applying the latest
available hotfix to resolve the problem.
Which procedure resolves the problem?

• A.Browse to System > Software Management > Image List.
  Import 11.1.0.HF3 to the available hotfix images.
  Select the imported hotfix image and installation location and click Install.
• B.Browse to System > Software Management > Image List.
  Import TMOS 11.2.0 to the available hotfix images.
  Select the imported hotfix image and installation location and click Install.
• C.Browse to System > Software Management > Hotfix List.
  Import TMOS 11.2.0 to the available hotfix images.
  Select the imported hotfix image and installation location and click Install.
• D.Browse to System > Software Management > Hotfix List.
  Import 11.1.0.HF3 to the available hotfix images.
  Select the imported hotfix image and installation location and click Install.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -

-- Exhibit --
Refer to the exhibit.
An LTM Specialist is troubleshooting an HTTP monitor that is marking a pool member as down.
Connecting to the pool member directly through a browser shows the application is up and functioning correctly.
How should the send string be modified to correct this issue?

• A.GET /\r\n\r\n
• B.GET /\r\nHTTP/1.0\r\n\r\n
• C.GET /\r\nHost: \r\n\r\n
• D.GET / HTTP/1.0\r\n\r\n

Comment: *

Name: *

Email: *

Verification: *

An IT administrator wants to log which server is being load balanced to by a user with IP address 10.10.10.25.
Which iRule should the LTM Specialist use to fulfill the request?

• A.when SERVER_CONNECTED {
  if { [IP::addr [IP::remote_addr]] equals 10.10.10.25]} {
  log local0. "client 10.10.10.25 connected to pool member [IP::addr [LB::server addr]]" }
  }
• B.when SERVER_CONNECTED {
  if { [IP::addr [clientside [IP::remote_addr]] equals 10.10.10.25]} {
  log local0. "client 10.10.10.25 connected to pool member [IP::addr [LB::server addr]]" }
  }
• C.when CLIENT_ACCEPTED {
  if { [IP::addr [IP::remote_addr] equals 10.10.10.25]} {
  log local0. "client 10.10.10.25 connected to pool member [IP::addr [LB::server addr]]" }
  }
• D.when CLIENT_ACCEPTED {
  if { [IP::addr [clientside [IP::remote_addr]] equals 10.10.10.25]} {
  log local0. "client 10.10.10.25 connected to pool member [IP::addr [LB::server addr]]" }
  }

Comment: *

Name: *

Email: *

Verification: *