-- 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.
ltm monitor http http_mon { defaults-from http destination *:* interval 5 recv "200 OK" send "GET /\\r\\n" time-until-up 0 timeout 16
}
What is the issue?

• A.The request is NOT being received by the pool member.
• B.The pool member is responding with a 404.
• C.The HTTP headers are compressed.
• D.The pool member is responding without HTTP headers.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit-

-- Exhibit --
Refer to the exhibit.
Which step should an LTM Specialist take next to finish upgrading to HD1.3?

• A.Activate HD1.3
• B.Relicense HD1.3
• C.Install hotfix to HD1.3
• D.Install image to HD1.3

Comment: *

Name: *

Email: *

Verification: *

A failover event is recorded in the log messages:
Jan 01 00:00:50 BIG-IP notice sod[5855]: 01140029:5: HA proc_running tmm fails action is go offline and down links.
Jan 01 00:00:50 BIG-IP notice sod[5855]: 010c0050:5: Sod requests links down.
Jan 01 00:00:50 BIG-IP notice sod[5855]: 010c0054:5: Offline for traffic group /Common/traffic-group-1.
Jan 01 00:00:50 BIG-IP notice sod[5855]: 010c003e:5: Offline
Jan 01 00:00:50 BIG-IP notice logger: /usr/bin/tmipsecd --tmmcount 4 ==> /usr/bin/bigstart stop racoon Jan 01 00:00:50 BIG-IP info lacpd[5502]: 01160016:6: Failover event detected. (Switchboard failsafe disabled while offline)
Jan 01 00:00:51 BIG-IP err bcm56xxd[5296]: 012c0010:3: Failover event detected. Marking external interfaces down. bsx.c(3633)
Jan 01 00:00:51 BIG-IP info bcm56xxd[5296]: 012c0015:6: Link: 1.1 is DOWN Jan 01 00:00:56 BIG-IP notice mcpd[5318]: 0107143c:5: Connection to CMI peer 10.0.0.3 has been removed
Jan 01 00:00:56 BIG-IP notice mcpd[5318]: 0107143a:5: CMI reconnect timer: enabled Jan 01 00:00:56 BIG-IP notice mcpd[5318]: 01071431:5: Attempting to connect to CMI peer 10.0.0.3 port
6699
What is the cause of the failover?

• A.A switchboard failure caused system fail-safe to initiate the failover.
• B.Loss of connection to CMI peer 10.0.0.3 initiated the failover.
• C.TMM failed, and system fail-safe initiated the failover.
• D.TMM failed, and VLAN fail-safe initiated the failover.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -

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

• A.The client authentication failed.
• B.The virtual server does NOT have a pool configured.
• C.The client and server CANNOT agree on a common cipher.
• D.The virtual server does NOT have a client SSL profile configured.

Comment: *

Name: *

Email: *

Verification: *

-- Exhibit -

-- Exhibit --
Refer to the exhibit.
An LTM Specialist is troubleshooting an issue with a new virtual server. When connecting through the virtual server, clients receive the message "The connection was reset" in the browser. Connections directly to the pool member show the application is functioning correctly.
What is the issue?

• A.The pool member is failing the monitor check.
• B.The virtual server is configured with the incorrect SNAT address.
• C.The virtual server is processing encrypted traffic as plain-text HTTP.
• D.The pool member default gateway is set incorrectly.

Comment: *

Name: *

Email: *

Verification: *