An LTM Specialist has set up a custom SNMP alert.
Which command line tool should the LTM Specialist use to test the alert?

• A.logger
• B.logtest
• C.testlog
• D.snmptest

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -

-- Exhibit --
Refer to the exhibit.
Users report that a web application works incorrectly. Sometimes contextual data displayed on the web pages is accurate; other times it is inaccurate.
The LTM administrator looks at the connection table with a filter on one of the client IP addresses currently connected using the command "tmsh show sys connection cs-client-addr 10.0.20.1" with the following results:
10.0.20.1:60048 10.0.20.88:80 10.0.20.1:60048 172.16.20.1:80 tcp 3 (tmm: 0)
10.0.20.1:60050 10.0.20.88:80 10.0.20.1:60050 172.16.20.3:80 tcp 3 (tmm: 0)
10.0.20.1:60047 10.0.20.88:80 10.0.20.1:60047 172.16.20.2:80 tcp 3 (tmm: 0)
10.0.20.1:60049 10.0.20.88:80 10.0.20.1:60049 172.16.20.1:80 tcp 3 (tmm: 0) What is the solution to the problem?

• A.Synchronize the clock of the LTM device with NTP.
• B.Modify the load balancing method attached to the pool.
• C.Set up an HTTP cookie insert profile in the virtual server.
• D.Modify the setup of the monitor bound to the pool used by the application.

Comment: *

Name: *

Email: *

Verification: *

The LTM Specialist is writing a custom HTTP monitor for a web application and has viewed the content by accessing the site directly via their browser. The monitor continually fails. The monitor configuration is:
ltm monitor http /Common/exampleComMonitor {
defaults-from /Common/http
destination *:*
interval 5
recv "Recent Searches"
send "GET /app/feed/current\?uid=20145 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 }
A trace shows the following request and response:
Request: GET /app/feed/current?uid=20145 HTTP/1.1 Host www.example.com Accept-Encoding gzip, deflate Connection: close
Response: HTTP/1.1 302 Moved Temporarily Date Wed, 17 Oct 2012 18:45:52 GMT Server Apache Location https://example.com/login.jsp Content-Encoding gzip Content-Type text/html;charset=UTF-8 Set-CookiE. JSESSIONID=261EFFBDA8EC3036FBCC22D991AC6835;
Path=/app/feed/current?uid=20145
What is the problem?

• A.The HTTP monitor does NOT support monitoring jsp pages.
• B.The request includes an Accept-Encoding so the server is responding with a gzipped result and LTM monitors CANNOT handle gzipped responses.
• C.The request does NOT include any cookies and the application is expecting a session cookie.
• D.The request does NOT include a User-Agent header.

Comment: *

Name: *

Email: *

Verification: *

A failover event is recorded in the following log messages:
Jan 01 00:56:56 BIG-IP notice mcpd[5318]: 01070727:5: Pool /Common/my-pool member / Common/10.0.0.10:80 monitor status down.
Jan 01 00:56:56 BIG-IP notice sod[5855]: 010c0045:5: Leaving active, group score 10 peer group score 20.
Jan 01 00:56:56 BIG-IP notice sod[5855]: 010c0052:5: Standby for traffic group /Common/traffic-group-1.
Jan 01 00:56:56 BIG-IP notice sod[5855]: 010c0018:5: Standby
Jan 01 00:57:06 BIG-IP notice logger: /usr/bin/tmipsecd --tmmcount 4 ==> /usr/bin/bigstart stop racoon What is the cause of the failover?

• A.The racoon service stopped responding.
• B.The HA group score changed.
• C.The peer device left the traffic group.
• D.No traffic is seen on traffic-group-1.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -

-- Exhibit --
Refer to the exhibit.
A client attempts to connect from a Google Chrome browser to a virtual server on a BIG-IP LTM. The virtual server is SSL Offloaded. When the client connects, the client receives an SSL error. The client receives the same errors when trying Mozilla Firefox and Internet Explorer browsers.
The LTM Specialist does an ssldump on the virtual server and receives the results as per the exhibit.
How should this be resolved?

• A.Set the virtual server to listen on port 443 (HTTPS).
• B.Adjust the SSL key length in the SSL profile to match the minimum required by the client.
• C.Upgrade the client to support the appropriate SSL cipher suite.
• D.Select the appropriate "SSL Profile (Client)" in the virtual server settings.

Comment: *

Name: *

Email: *

Verification: *