F5 LTM Specialist 301b New Questions

LTM Specialist: Maintain & Troubleshoot Questions and Answers

Question 13

Given this as the first packet displayed of an ssldump:

2 2 1296947622.6313 (0.0001) S>CV3.1(74) Handshake

ServerHello

Version 3.1

random[32]=

19 21 d7 55 c1 14 65 63 54 23 62 b7 c4 30 a2 f0

b8 c4 20 06 86 ed 9c 1f 9e 46 0f 42 79 45 8a 29

session_id[32]=

c4 44 ea 86 e2 ba f5 40 4b 44 b4 c2 3a d8 b4 ad

4c dc 13 0d 6c 48 f2 70 19 c3 05 f4 06 e5 ab a9

cipherSuite TLS_RSA_WITH_RC4_128_SHA

compressionMethod NULL

In reviewing the rest of the ssldump, the application data is NOT being decrypted.

Why is ssldump failing to decrypt the application data?

Options:

The application data is encrypted with SSLv3.

The application data is encrypted with TLSv1.

The data is contained within a resumed TLS session.

The BigDB Key Log.Tcpdump.Level needs to be adjusted.

Question 14

-- 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?

Options:

The client authentication failed.

The virtual server does NOT have a pool configured.

The client and server CANNOT agree on a common cipher.

The virtual server does NOT have a client SSL profile configured.

Question 15

-- Exhibit –

-- Exhibit --

Refer to the exhibits.

An LTM Specialist is reconfiguring a virtual server to redirect all clients to HTTPS. Testing reveals that the redirect is functioning incorrectly. As part of the troubleshooting process, the LTM Specialist performs a packet capture.

What is the issue?

Options:

The redirect is causing an infinite loop.

The virtual server is missing a clientssl profile.

The redirect is sending the client to the incorrect location.

The virtual server is incorrectly processing the HTTP request.

Question 16

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?

Options:

TMM failed, and VLAN fail-safe initiated the failover.

TMM failed, and system fail-safe initiated the failover.

Loss of connection to CMI peer 10.0.0.3 initiated the failover.

A switchboard failure caused system fail-safe to initiate the failover.

Labour Day Special - Limited Time 65% Discount Offer - Ends in 0d 00h 00m 00s - Coupon code: top65certs

LTM Specialist: Maintain & Troubleshoot Questions and Answers

Options:

Answer:

Options:

Answer:

Options:

Answer:

Options:

Answer: